SCM:DonGould: Reach problem? Is this being caused by the Telstra free weekend congesting the Reach ports?
I'd be interested to see a traceroute to 7206-gi-0-2.w-link.net to compare the path.
Is there a common Reach router in there that isn't dealing with the flood of traffic Telstra is throwing at it?
From Snap connection in Dunedin..
Tracing route to 7206-gi-0-2.w-link.net [207.244.149.46]
over a maximum of 30 hops:
1 2 23 ms 99 ms 100 ms 192.168.1.253
3 21 ms 24 ms 25 ms 20.17.69.111.static.snap.net.nz [111.69.17.20]
4 14 ms 13 ms 14 ms 24.17.69.111.static.snap.net.nz [111.69.17.24]
5 * * * Request timed out.
6 40 ms 32 ms 31 ms 111-69-27-66.core.snap.net.nz [111.69.27.66]
7 95 ms 94 ms 95 ms 203.167.233.10
8 222 ms 223 ms 222 ms i-0-6-4-1.tlot-core01.bx.reach.com [202.84.142.1
14]
9 229 ms 220 ms 220 ms i-2-5.tlot03.bi.reach.com [202.84.251.242]
10 223 ms 223 ms 223 ms xe-11-2-0.edge1.losangeles6.level3.net [4.68.62.
9]
11 220 ms 220 ms 220 ms vlan80.csw3.LosAngeles1.Level3.net [4.69.144.190
]
12 220 ms 220 ms 220 ms ae-82-82.ebr2.LosAngeles1.Level3.net [4.69.137.2
5]
13 234 ms 244 ms 234 ms ae-6-6.ebr2.SanJose5.Level3.net [4.69.148.202]
14 245 ms 234 ms 234 ms ae-5-5.ebr4.SanJose1.Level3.net [4.69.148.142]
15 232 ms 255 ms 234 ms ae-34-34.ebr2.SanJose1.Level3.net [4.69.153.33]
16 265 ms 252 ms 251 ms ae-7-7.ebr1.Seattle1.Level3.net [4.69.132.50]
17 250 ms 250 ms 250 ms ae-13-51.car3.Seattle1.Level3.net [4.69.147.133]
18 249 ms 249 ms 249 ms metapeer.car3.Seattle1.Level3.net [4.71.152.18]
19 253 ms 253 ms 253 ms 208.99.192.65
20 252 ms 252 ms 252 ms 208.99.192.94
21 250 ms 250 ms 250 ms renbd1-gi-2-1.w-link.net [207.244.149.54]
22 251 ms 250 ms 250 ms botbd1-gi-4-2.w-link.net [207.244.149.33]
23 250 ms 250 ms 250 ms 7206-gi-0-2.w-link.net [207.244.149.46]
While my internet has been slow most of the weekend it seems others have had it much worse..
Ya, same IP in there... seems like the peering fabric is a round robin of some kind. Different vlans to Level3.
If we really wanted to get to the bottom of this we'd ping NANog and ask for help, but I think it's fairly obvious.