High pings 40ms+ to 1.1.1.1 in Melbourne AUS/Internode

performance
routing

#1

Similar to Degraded latency performance in DFW I’ve noticed latency to 1.1.1.1 in Melbourne Australia have increased from ~9ms to ~40ms recently.

I have two different connections from two ISPs. It only seems to affect one (Internode) while the other (TPG) is unaffected. The two connections take almost the identical route but the latency is very different. I believe this is an issue with the upstream provider.

Ping & traceroute from Internode (poor latency)

C:\Users\longz>ping 1.1.1.1

Pinging 1.1.1.1 with 32 bytes of data:
Reply from 1.1.1.1: bytes=32 time=48ms TTL=53
Reply from 1.1.1.1: bytes=32 time=53ms TTL=53
Reply from 1.1.1.1: bytes=32 time=61ms TTL=53
Reply from 1.1.1.1: bytes=32 time=60ms TTL=53

Ping statistics for 1.1.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 48ms, Maximum = 61ms, Average = 55ms

C:\Users\longz>tracert 1.1.1.1

Tracing route to one.one.one.one [1.1.1.1]
over a maximum of 30 hops:

1 1 ms 1 ms 2 ms dsldevice.lan [10.1.1.1]
2 9 ms 8 ms 8 ms 10.20.21.16
3 5 ms 7 ms 7 ms nme-apt-bur-wgw1-be-10.tpgi.com.au [203.219.155.138]
4 6 ms 4 ms 3 ms 203-219-107-206.static.tpgi.com.au [203.219.107.206]
5 18 ms 15 ms 11 ms bundle-ether-13.win-edge901.melbourne.telstra.net [165.228.52.1]
6 19 ms 16 ms 18 ms bundle-ether2.lon-edge901.melbourne.telstra.net [203.50.11.115]
7 57 ms 60 ms 53 ms clo2241358.lnk.telstra.net [139.130.67.10]
8 59 ms 56 ms 59 ms one.one.one.one [1.1.1.1]

Trace complete.

Ping & traceroute from TPG (good latency)

C:\Users\Long>ping 1.1.1.1

Pinging 1.1.1.1 with 32 bytes of data:
Reply from 1.1.1.1: bytes=32 time=9ms TTL=57
Reply from 1.1.1.1: bytes=32 time=11ms TTL=57
Reply from 1.1.1.1: bytes=32 time=9ms TTL=57
Reply from 1.1.1.1: bytes=32 time=9ms TTL=57

Ping statistics for 1.1.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 11ms, Average = 9ms

C:\Users\Long>tracert 1.1.1.1

Tracing route to one.one.one.one [1.1.1.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms router.asus.com [192.168.2.1]
2 <1 ms <1 ms <1 ms 192.168.1.1
3 10 ms 9 ms 8 ms 10.20.22.137
4 9 ms 8 ms 10 ms nme-sot-dry-wgw1-be-20.tpgi.com.au [203.219.155.72]
5 9 ms 9 ms 9 ms 203-219-107-202.static.tpgi.com.au [203.219.107.202]
6 9 ms 11 ms 10 ms bundle-ether19.lon-edge901.melbourne.telstra.net [139.130.41.105]
7 9 ms 12 ms 21 ms clo2241358.lnk.telstra.net [139.130.67.10]
8 9 ms 9 ms 8 ms one.one.one.one [1.1.1.1]

#2

Experienced similar this morning, but issue seem to be gone now.