Explore & discover

Helpful Links

Constant Ping Spikes (Can't reach a CSR who knows what latency even is)

Highlighted
Contributor

Constant Ping Spikes (Can't reach a CSR who knows what latency even is)

Hi All,

I have had several days of constant ping spikes on a hardwired connection. The spikes make all "real time" activities impossible (Google Hangouts, Skype, Gaming, etc.) 

 

I have tried disconnecting all wireless devices and rebooting everything that can be rebooted. I have shutdown all unneeded processes. There are no uploads on the network. A typical run is something like this:

 

ping 8.8.8.8 -t

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=745ms TTL=45
Reply from 8.8.8.8: bytes=32 time=81ms TTL=45
Reply from 8.8.8.8: bytes=32 time=31ms TTL=45
Reply from 8.8.8.8: bytes=32 time=24ms TTL=45
Reply from 8.8.8.8: bytes=32 time=59ms TTL=45
Reply from 8.8.8.8: bytes=32 time=36ms TTL=45
Reply from 8.8.8.8: bytes=32 time=33ms TTL=45
Reply from 8.8.8.8: bytes=32 time=39ms TTL=45
Reply from 8.8.8.8: bytes=32 time=33ms TTL=45
Reply from 8.8.8.8: bytes=32 time=26ms TTL=45
Reply from 8.8.8.8: bytes=32 time=27ms TTL=45
Reply from 8.8.8.8: bytes=32 time=88ms TTL=45
Reply from 8.8.8.8: bytes=32 time=38ms TTL=45
Reply from 8.8.8.8: bytes=32 time=23ms TTL=45
Reply from 8.8.8.8: bytes=32 time=24ms TTL=45
Reply from 8.8.8.8: bytes=32 time=32ms TTL=45
Reply from 8.8.8.8: bytes=32 time=23ms TTL=45
Reply from 8.8.8.8: bytes=32 time=23ms TTL=45
Reply from 8.8.8.8: bytes=32 time=23ms TTL=45
Reply from 8.8.8.8: bytes=32 time=23ms TTL=45
Reply from 8.8.8.8: bytes=32 time=23ms TTL=45
Reply from 8.8.8.8: bytes=32 time=24ms TTL=45
Reply from 8.8.8.8: bytes=32 time=23ms TTL=45
Reply from 8.8.8.8: bytes=32 time=23ms TTL=45
Reply from 8.8.8.8: bytes=32 time=23ms TTL=45
Reply from 8.8.8.8: bytes=32 time=23ms TTL=45
Reply from 8.8.8.8: bytes=32 time=23ms TTL=45
Reply from 8.8.8.8: bytes=32 time=24ms TTL=45
Reply from 8.8.8.8: bytes=32 time=24ms TTL=45
Reply from 8.8.8.8: bytes=32 time=24ms TTL=45
Reply from 8.8.8.8: bytes=32 time=24ms TTL=45
Reply from 8.8.8.8: bytes=32 time=24ms TTL=45
Reply from 8.8.8.8: bytes=32 time=23ms TTL=45
Reply from 8.8.8.8: bytes=32 time=25ms TTL=45
Reply from 8.8.8.8: bytes=32 time=23ms TTL=45
Reply from 8.8.8.8: bytes=32 time=526ms TTL=45
Reply from 8.8.8.8: bytes=32 time=23ms TTL=45
Reply from 8.8.8.8: bytes=32 time=23ms TTL=45
Reply from 8.8.8.8: bytes=32 time=23ms TTL=45
Reply from 8.8.8.8: bytes=32 time=23ms TTL=45

Ping statistics for 8.8.8.8:
Packets: Sent = 40, Received = 40, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 745ms, Average = 60ms

When I run a tracert to Google's DNS, I sometimes catch the problem:


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 homeportal [192.168.1.254]
2 10 ms 10 ms 11 ms adsl-74-243-130-1.int.bellsouth.net [74.243.130.1]
3 10 ms 10 ms 11 ms 70.159.228.15
4 11 ms 11 ms 10 ms 70.159.228.17
5 1295 ms 15 ms 15 ms 12.123.14.41
6 23 ms 23 ms 22 ms 12.122.141.221

 

Running Tracert or MRT, the lag always takes place on AT&T Worldnet Services Equipment. When I get a CSR, they tell me that everything is fine...  

Thanks for any help out there!!

~Matt

 

Tags (3)
5,249 Views
Message 1 of 3
Professor
Solution
Accepted by topic author
Accepted by greenmrt
‎06-20-2017 4:27 AM

Re: Constant Ping Spikes (Can't reach a CSR who knows what latency even is)

@greenmrt

For me, pinging Google DNS gives me an average of 41.855 but a max of 61.777. The spike you are receiving could be associated with traffic on your home network or neighborhood. From my experience, that kind of spike could be due to video streaming. However, there are other causes. Let's eliminate some common causes. Here are two recommendations:

  1. Disable IPv6 on your AT&T provided router/gateway - IPv6 is enabled by default and can cause a slow network and other communication issues
  2. Change the Ethernet port configuration for each port on your AT&T provided router/gateway from Auto-detect to 100BaseT/Full Duplex - This will eliminate auto-negotiation incompatibilities

Physically power off all devices in your network other than the one you used for pinging. Now try the ping test.

 

Look at the event and system logs of your AT&T provided router/gateway and see if there is an entry that repeats every minute or less.

_____________________________________________________
Tags (1)
Message 2 of 3
Contributor

Re: Constant Ping Spikes (Can't reach a CSR who knows what latency even is)

@ApexRon,

 

Wow! That is amazing. Things were largely better last night without any changes, but still there were occasional spikes to ~200-300. The firmware on my router does not allow me to set the ports to to 100BaseT/Full Duplex, but all I have attached are a printer and desktop. After disabling IPv6, though, I got these results:

 

Ping statistics for 8.8.8.8:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 23ms, Average = 21ms

Thankful and sanity restored,
~Matt

P.S. Can you train some CSR's? The one I talked to told me the lag I had was caused by AT&T's DNS servers (even when I told him the lag happened when I pinged an IP address). He then said that what we needed to do was reset the modem and reinput the user setup. Last bit of advise was to find another provider... Thank goodness for you!

Message 3 of 3
Share this topic
Share this topic
Announcements

Are you having trouble logging in? Is your email password not working? Let us show you how to Reset your Email Password using myAT&T!

Additional Support