I'm in the Chicago area, and I often do a quick check on connectivity by pinging Google.com. Most of the time, it's in the 11-13ms area. Starting Friday (7/31), it was suddenly 48 or so, another time, in the 20's, then in the 50's, with a slightly different IP address. Each ping set is consistent. This is using IPv6. If I force IPv4, it's normal. For some reason, it looks like the IPv6 is being routed through Comcast in Pennsylvania???
Microsoft Windows [Version 10.0.18363.959](c) 2019 Microsoft Corporation. All rights reserved. c:\downloads>ping -4 google.com Pinging google.com [172.217.6.110] with 32 bytes of data:Reply from 172.217.6.110: bytes=32 time=11ms TTL=117Reply from 172.217.6.110: bytes=32 time=11ms TTL=117Reply from 172.217.6.110: bytes=32 time=21ms TTL=117Reply from 172.217.6.110: bytes=32 time=11ms TTL=117 Ping statistics for 172.217.6.110: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 11ms, Maximum = 21ms, Average = 13ms c:\downloads>tracert -4 google.com Tracing route to google.com [172.217.6.110]over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms RT-AC68U-F288 [192.168.1.1] 2 8 ms 8 ms 8 ms 96.120.25.213 3 9 ms 9 ms 8 ms 68.86.185.21 4 12 ms 13 ms 11 ms be-124-ar01.area4.il.chicago.comcast.net [162.151.45.109] 5 13 ms 12 ms 13 ms be-32221-cs02.350ecermak.il.ibone.comcast.net [96.110.40.53] 6 11 ms 12 ms 12 ms be-2201-pe01.350ecermak.il.ibone.comcast.net [96.110.37.6] 7 12 ms 12 ms 12 ms 66.208.233.86 8 14 ms 12 ms 13 ms 209.85.250.189 9 11 ms 12 ms 12 ms 108.170.238.91 10 12 ms 11 ms 11 ms ord37s03-in-f110.1e100.net [172.217.6.110] Trace complete.
c:\downloads>ping google.com Pinging google.com [2607:f8b0:4009:802::200e] with 32 bytes of data:Reply from 2607:f8b0:4009:802::200e: time=44msReply from 2607:f8b0:4009:802::200e: time=43msReply from 2607:f8b0:4009:802::200e: time=44msReply from 2607:f8b0:4009:802::200e: time=43ms Ping statistics for 2607:f8b0:4009:802::200e: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 43ms, Maximum = 44ms, Average = 43ms c:\downloads>tracert google.com Tracing route to google.com [2607:f8b0:4009:802::200e]over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 2601:249:500:73a4::1 2 8 ms 9 ms 8 ms 2001:558:4040:13::1 3 8 ms 9 ms 8 ms te0-0-0-7-sur01.peru.in.indiana.comcast.net [2001:558:322:9801::1] 4 8 ms 8 ms 8 ms 2001:558:300:1a1::2 5 12 ms * 13 ms be-124-ar01.area4.il.chicago.comcast.net [2001:558:300:1bc::1] 6 * * * Request timed out. 7 * * * Request timed out. 8 * 24 ms * be-301-cr12.pittsburgh.pa.ibone.comcast.net [2001:558:3:1e7::2] 9 23 ms * 23 ms be-1412-cs04.pittsburgh.pa.ibone.comcast.net [2001:558:3:1a7::1] 10 * * * Request timed out. 11 * * * Request timed out. 12 27 ms 27 ms 27 ms ord37s07-in-x0e.1e100.net [2607:f8b0:4009:802::200e] Trace complete.
↧