This isn't resolved, but the issue has been identified and worked around. There seems to be a TPG router on a Pipe IX in Melbourne that isn't passing traffic for routes that it's advertising.
On Tue, 16 Jun 2020 at 10:26, Tim Sandy <[email protected]> wrote: > Seeing some issues with Internet routing, particular subnets are > unreachable from at least TPG NBN/ADSL. > > Traceroutes get as far as the Optus network and then drop. Both TPG and > Optus looking glasses are seeing my routes and can successfully ping my > network. > > > Interestingly too, tracing from network back to the hop where my traffic > disappears - Traverses the same previous hop and gets a response. > > > Trace INTO my network; > 4 24 ms 25 ms 24 ms 203.219.107.202 > 5 25 ms 27 ms 24 ms 203.8.177.106 > 6 26 ms 25 ms 23 ms 59.154.142.56 <<<Same > 7 38 ms 25 ms 28 ms 161.43.103.98 > 8 * * * Request timed out. > 9 * * * Request timed out. > 10 * * * Request timed out. > > Trace FROM my network; > Tracing route to 161.43.103.98 over a maximum of 30 hops > 4 <1 ms <1 ms 1 ms 220.101.41.13 > 5 * * * Request timed out. > 6 3 ms 2 ms 2 ms 59.154.142.62 <<<Same > > 7 2 ms 8 ms 2 ms 161.43.103.98 > > > Anyone else having problems? >
_______________________________________________ AusNOG mailing list [email protected] http://lists.ausnog.net/mailman/listinfo/ausnog
