SimplePandaBSD Premium Member join:2003-09-22 Montreal, QC |
Google Public DNS route changeJust noticed this today; seems like it's changed in the last 12-24 hours.
1. 172.16.254.1 0.0% 4 1.4 1.0 0.7 1.4 0.0 2. ??? 3. 209.148.245.173 0.0% 4 81.4 34.6 12.0 81.4 31.8 4. 69.63.248.181 0.0% 4 13.6 13.7 12.0 17.0 2.2 5. 209.148.224.246 0.0% 4 41.7 25.6 12.8 41.7 14.2 6. 72.14.222.87 0.0% 3 28.6 28.6 19.9 37.4 8.7 7. 72.14.239.75 0.0% 3 11.6 14.4 11.6 17.1 2.6 8. google-public-dns-a.google.com 0.0% 3 13.9 12.6 11.8 13.9 1.0
8.8.8.8 (google-public-dns-a) is now about 10-15ms away from Rogers DOCSIS. Seems a routing change happened and/or Google spun up another node closer to Rogers. Ping times were 40ms+ as recently as a day or two ago.
8.8.8.8 namebench's as the fastest DNS server visible to me at this point. |
|
damir join:2013-12-12 CANADA |
damir
Member
2014-Dec-5 10:07 pm
I don't see it like that.
C:\Windows\System32>tracert 8.8.8.8
Tracing route to google-public-dns-a.google.com [8.8.8.8] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms CACTUS [10.10.1.1] 2 * * * Request timed out. 3 21 ms 11 ms 12 ms 67.231.222.181 4 16 ms 35 ms 16 ms 64.71.241.97 5 * 33 ms 33 ms 69.63.253.149 6 28 ms 27 ms 27 ms 74.125.49.229 7 31 ms 51 ms 88 ms 209.85.244.131 8 28 ms 26 ms 28 ms google-public-dns-a.google.com [8.8.8.8]
Trace complete. |
|
|
to SimplePanda
said by SimplePanda:Just noticed this today; seems like it's changed in the last 12-24 hours.
8.8.8.8 (google-public-dns-a) is now about 10-15ms away from Rogers DOCSIS. Seems a routing change happened and/or Google spun up another node closer to Rogers. Ping times were 40ms+ as recently as a day or two ago.
8.8.8.8 namebench's as the fastest DNS server visible to me at this point. This is not specific to Rogers. |
|
SimplePandaBSD Premium Member join:2003-09-22 Montreal, QC |
said by v6movement :said by SimplePanda:Just noticed this today; seems like it's changed in the last 12-24 hours.
8.8.8.8 (google-public-dns-a) is now about 10-15ms away from Rogers DOCSIS. Seems a routing change happened and/or Google spun up another node closer to Rogers. Ping times were 40ms+ as recently as a day or two ago.
8.8.8.8 namebench's as the fastest DNS server visible to me at this point. This is not specific to Rogers. Didn't say it was... still gets me to 8.8.8.8 in less than half the time it did yesterday. |
|
SimplePanda |
to damir
We have completely different routing tough; I'm guessing you're not in Toronto. |
|
GNONT42 join:2014-12-01 North York, ON |
These are our results. Tracing route to 8.8.8.8 over a maximum of 20 hops
1 * * * Request timed out. 2 16ms 1ms 16ms 209.148.244.5 3 1ms 1ms 1ms 69.63.249.77 4 16ms 16ms 16ms 24.156.144.182 5 32ms 16ms 16ms 72.14.216.189 6 16ms 16ms 16ms 66.249.94.173 7 16ms 16ms 16ms 8.8.8.8
Trace complete.
Pinging 8.8.8.8 with 64 bytes of data:
Reply from 8.8.8.8: bytes=64 time=32ms TTL=58 seq=1 Reply from 8.8.8.8: bytes=64 time=16ms TTL=58 seq=2 Reply from 8.8.8.8: bytes=64 time=16ms TTL=58 seq=3 Reply from 8.8.8.8: bytes=64 time=16ms TTL=58 seq=4
Ping statistics for 8.8.8.8 Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 16ms, Maximum = 32ms, Average = 20ms |
|
|
Isn't your connection still crapping the bed GNONT42? |
|
GNONT42 join:2014-12-01 North York, ON |
said by oceros37:Isn't your connection still crapping the bed GNONT42? Shhhh, it's behaving at the moment... I don't want it to hear you or it'll crap out again |
|