Didn't find what you were looking for?
We have advanced search options to make it easier to locate posts, questions and answers on this community.
More information can be found at Advanced Search Options
If you are looking for something specific, please check if someone else has already asked or answered the same question.
This content may be outdated or inaccurate
All posts are closed and commenting has been disabled
If you have a question or comment, please start a new post (registration is required)
Leave the Archive
Why am I getting super high ping bursts?
Hello,
I have had awesome service for years up until several weeks ago when I started getting huge lag from a bottleneck somewhere down the line. Its sporadic in duration and time of day, but I would say average once or twice an hour and lasts several mins (sometimes worse in frequency). I have restarted my router many times to no effect. I do work in IT and tried to see if I could see the source of the lag via 'tracert' to google's DNS. I found about 4 hops out was the issue and seen huge spikes on 96.34.95.68 (600ms to 1000 ms) and also seen a relatively large lag on 96.34.0.133. No lag was detected on my local network or 2 hopes out from running pings for several mins to each hop closer to me. Maybe this can help someone find some faulty equipment. It's a very recent development, just weeks and I hope it can be resolved so I can game again. If this is not the appropriate forum for this info could someone please give me a contact I could email with issue.
Thanks
Answers
-
Hi @Mmobley77, welcome to our community!
Have you restarted the modem in addition to the router? Will you run a continuous ping test through your command prompt ("ping -t 8.8.8.8" or other IP) and check if you can see any spikes there as well? If possible please test while connected directly to the modem, bypassing your router. If you know the IP of the game server you play on, you could ping it simultaneously in a second command prompt window to compare results.
0 -
Yes, I have bypassed, using ethernet direct into the modem provided by spectrum and have ran multiple extended pings on nodes along my trace while monitoring for spikes to see which node correlated with the spikes.
0 -
See this happen often at the IXP's (hand off to third party peer).
Are the next hops after the trouble spots non-Charter/Spectrum network nodes?
0 -
Are you seeing the spikes on every IP you ping? Do they happen at the same time when pinging different IP's simultaneously? Just how high are they spiking?
Are you able to attach a screenshot showing your ping test and tracert results?
0 -
The routers are within Spectrums network. They still have Charters DNS name. When I was testing the connections, I didn't save the individual ping tests as I would assume an admin could monitor that ip for a few hours and see what was happening because it is very consistent. The spikes sometimes get 1000ms + for around 30 seconds. Sometimes it effects streaming video, so we get a pause when watching for buffer but that is only a few times.
Example of a spike on a ping to google DNS. I tracert the hops and isolated to the IP mentioned above. The 30-40ms is normal range for my location in the past.
Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=456ms TTL=114
Reply from 8.8.8.8: bytes=32 time=416ms TTL=114
Reply from 8.8.8.8: bytes=32 time=1365ms TTL=114
Reply from 8.8.8.8: bytes=32 time=27ms TTL=114
Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 1365ms, Average = 566ms
C:\Users\bmobl>PING 8.8.8.8
Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=597ms TTL=114
Reply from 8.8.8.8: bytes=32 time=574ms TTL=114
Reply from 8.8.8.8: bytes=32 time=550ms TTL=114
Reply from 8.8.8.8: bytes=32 time=1483ms TTL=114
Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 550ms, Maximum = 1483ms, Average = 801ms
C:\Users\bmobl>PING 8.8.8.8
Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=1614ms TTL=114
Reply from 8.8.8.8: bytes=32 time=27ms TTL=114
Reply from 8.8.8.8: bytes=32 time=33ms TTL=114
Reply from 8.8.8.8: bytes=32 time=903ms TTL=114
Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 1614ms, Average = 644ms
C:\Users\bmobl>PING 8.8.8.8
Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=562ms TTL=114
Reply from 8.8.8.8: bytes=32 time=1505ms TTL=114
Reply from 8.8.8.8: bytes=32 time=27ms TTL=114
Reply from 8.8.8.8: bytes=32 time=37ms TTL=114
Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 1505ms, Average = 532ms
C:\Users\bmobl>PING 8.8.8.8
Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=1144ms TTL=114
Reply from 8.8.8.8: bytes=32 time=978ms TTL=114
Reply from 8.8.8.8: bytes=32 time=935ms TTL=114
Reply from 8.8.8.8: bytes=32 time=904ms TTL=114
Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 904ms, Maximum = 1144ms, Average = 990ms
0 -
May want to drop a tracert to it as well. May simply be a high utilization issue that needs to be addressed. Especially if you capture a different general route appears cleaner than another. If you can capture it with a specific game server or streaming server, it may be very useful for them.
Ran into this back when FFXIV 2.0 launched out of Montreal. Pathing to/through Level3 was getting overloaded at certain times of day while it was demonstrably much more stable via TATA or Cogentco peering. Might spot a similar scenario here. If it doesn't clear up with the next round of BGP route announcements, they may need to escalate things.
1 -
Grabbed this one on a noticeable drop.
1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.1.1]
2 13 ms 9 ms 707 ms 047-133-032-001.res.spectrum.com [47.133.32.1]
3 9 ms 10 ms 9 ms lag-156.dtr01hlrgnc.netops.charter.com [96.34.94.244]
4 608 ms 17 ms 5 ms lag-20.crr01hlrgnc.netops.charter.com [96.34.93.240]
5 43 ms 19 ms 32 ms lag-404.crr02spbgsc.netops.charter.com [96.34.95.68]
6 27 ms 789 ms 963 ms lag-808.bbr01spbgsc.netops.charter.com [96.34.2.50]
7 930 ms 45 ms 29 ms lag-805.bbr02atlnga.netops.charter.com [96.34.0.133]
8 21 ms 23 ms 22 ms lag-802.prr01atlnga.netops.charter.com [96.34.3.111]
9 805 ms 35 ms 26 ms 096-034-150-059.biz.spectrum.com [96.34.150.59]
10 28 ms 21 ms 24 ms 108.170.225.251
11 242 ms 38 ms 25 ms 209.85.241.155
12 207 ms 34 ms 33 ms dns.google [8.8.8.8]
And
1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.1.1]
2 14 ms 9 ms 10 ms 047-133-032-001.res.spectrum.com [47.133.32.1]
3 640 ms 10 ms 17 ms lag-156.dtr01hlrgnc.netops.charter.com [96.34.94.244]
4 34 ms 19 ms 9 ms lag-20.crr01hlrgnc.netops.charter.com [96.34.93.240]
5 23 ms 745 ms 22 ms lag-404.crr02spbgsc.netops.charter.com [96.34.95.68]
6 22 ms 37 ms 22 ms lag-808.bbr01spbgsc.netops.charter.com [96.34.2.50]
7 794 ms 28 ms 37 ms lag-805.bbr02atlnga.netops.charter.com [96.34.0.133]
8 20 ms 22 ms 22 ms lag-802.prr01atlnga.netops.charter.com [96.34.3.111]
9 23 ms 23 ms 22 ms 096-034-150-059.biz.spectrum.com [96.34.150.59]
10 24 ms 25 ms 609 ms 108.170.225.251
11 791 ms 36 ms 30 ms 209.85.241.155
12 320 ms 951 ms 33 ms dns.google [8.8.8.8]
0 -
Update,
Little later 8pm it looks like it may be closer to my immediate service.
1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.1.1]
2 861 ms 977 ms 988 ms 047-133-032-001.res.spectrum.com [47.133.32.1]
3 952 ms * 116 ms lag-156.dtr01hlrgnc.netops.charter.com [96.34.94.244]
4 1048 ms 974 ms 1961 ms lag-20.crr01hlrgnc.netops.charter.com [96.34.93.240]
5 991 ms 38 ms 32 ms lag-404.crr02spbgsc.netops.charter.com [96.34.95.68]
6 2947 ms 967 ms 31 ms lag-808.bbr01spbgsc.netops.charter.com [96.34.2.50]
7 2951 ms 975 ms 2943 ms lag-805.bbr02atlnga.netops.charter.com [96.34.0.133]
8 993 ms 24 ms 29 ms lag-802.prr01atlnga.netops.charter.com [96.34.3.111]
9 896 ms 1958 ms 973 ms 096-034-150-059.biz.spectrum.com [96.34.150.59]
10 959 ms 34 ms 32 ms 108.170.225.251
11 334 ms 985 ms 2933 ms 209.85.241.155
12 82 ms 31 ms 31 ms dns.google [8.8.8.8]
0 -
Those are quite the spikes at hops 2 and 3, which as you stated are very close to your immediate service. I recommend scheduling an appointment with a technician, there could be an issue with the modem, tap, or other nearby infrastructure which they may be able to trace the issue back to. I will send you a private message from our Community_Help handle to see if you would like to schedule that.
1
