Visitor

 • 

2 Messages

Sunday, May 31st, 2026 2:57 AM

im having occasional 300 ms pings. is there anything i can do?

im having the occasional 300 ms ping, after doing a traceroute i've determine it has to do with chicago hub being congested. is there anyway to fix this? like route me to a different hub?

Oldest First
Selected Oldest First

Official Employee

 • 

2.3K Messages

20 hours ago

Hello @Theosco, Thanks so much for taking a moment out of your day to leave a post on our community forum and we would be happy to help. Check out Internet Troubleshooting Tips and let us know if that helps. 

Visitor

 • 

2 Messages

20 hours ago

C:\Users\Theos>ping -t www.comcast.net

Pinging e7010.dscg.akamaiedge.net [2600:1418:1000:697::1b62] with 32 bytes of data:
Reply from 2600:1418:1000:697::1b62: time=19ms
Reply from 2600:1418:1000:697::1b62: time=21ms
Reply from 2600:1418:1000:697::1b62: time=19ms
Reply from 2600:1418:1000:697::1b62: time=19ms
Reply from 2600:1418:1000:697::1b62: time=16ms
Reply from 2600:1418:1000:697::1b62: time=18ms
Reply from 2600:1418:1000:697::1b62: time=25ms
Reply from 2600:1418:1000:697::1b62: time=20ms
Reply from 2600:1418:1000:697::1b62: time=17ms
Reply from 2600:1418:1000:697::1b62: time=18ms
Reply from 2600:1418:1000:697::1b62: time=15ms
Reply from 2600:1418:1000:697::1b62: time=19ms
Reply from 2600:1418:1000:697::1b62: time=14ms
Reply from 2600:1418:1000:697::1b62: time=13ms
Reply from 2600:1418:1000:697::1b62: time=12ms
Reply from 2600:1418:1000:697::1b62: time=19ms
Reply from 2600:1418:1000:697::1b62: time=19ms
Reply from 2600:1418:1000:697::1b62: time=20ms
Reply from 2600:1418:1000:697::1b62: time=14ms
Reply from 2600:1418:1000:697::1b62: time=20ms
Reply from 2600:1418:1000:697::1b62: time=20ms
Reply from 2600:1418:1000:697::1b62: time=15ms
Reply from 2600:1418:1000:697::1b62: time=14ms
Reply from 2600:1418:1000:697::1b62: time=243ms
Reply from 2600:1418:1000:697::1b62: time=197ms
Request timed out.
Reply from 2600:1418:1000:697::1b62: time=13ms
Reply from 2600:1418:1000:697::1b62: time=18ms
Reply from 2600:1418:1000:697::1b62: time=17ms
Reply from 2600:1418:1000:697::1b62: time=17ms
Reply from 2600:1418:1000:697::1b62: time=467ms
Reply from 2600:1418:1000:697::1b62: time=14ms
Reply from 2600:1418:1000:697::1b62: time=17ms
Reply from 2600:1418:1000:697::1b62: time=19ms
Reply from 2600:1418:1000:697::1b62: time=17ms
Reply from 2600:1418:1000:697::1b62: time=19ms
Reply from 2600:1418:1000:697::1b62: time=17ms
Reply from 2600:1418:1000:697::1b62: time=18ms
Reply from 2600:1418:1000:697::1b62: time=24ms
Reply from 2600:1418:1000:697::1b62: time=24ms
Reply from 2600:1418:1000:697::1b62: time=20ms
Reply from 2600:1418:1000:697::1b62: time=14ms

Ping statistics for 2600:1418:1000:697::1b62:
    Packets: Sent = 42, Received = 41, Lost = 1 (2% loss),
Approximate round trip times in milli-seconds:
    Minimum = 12ms, Maximum = 467ms, Average = 38ms
Control-C
^C
C:\Users\Theos>\

Expert

 • 

118.2K Messages

5 hours ago

The concern is not "accessibility / disability" help related............ Topic moved here to the proper help section. 

Expert

 • 

118.2K Messages

4 hours ago

@Theosco 

Try long pinging google.com using IPv4: ping /4 t50 google.com

Then, try a tracroute using the same numerical IP address that you got for the Google ping;

tracert /4 xxx.xxx.xxx.x 

x = Google's IP address.

forum icon

New to the Community?

Start Here