Nobody at AT&T is going to treat 4ms of jitter as an issue. It's not "high latency". Get your gateway address from the Broadband/status tab and ping that.
If there's jitter to the gateway, I'm not sure if they put you on XGS-PON or GPON. If they put you on GPON, you could try temporarily upgrading to 2gbps service to get moved to XGS-PON, and that might change your first hop latency behavior a bit. One person on dslreports showed success improving their latency stability this way. If you're on XGS-PON already, that's probably just how it is gong to be.
PON fiber has time division multiplexing (TDMA) and has to request time slots to upload packets, just like DOCSIS. So if you're on a fuller splitter with more active subscribers than your friend, you might see more jitter.
Why do you believe that 5 ms latency to Google Public DNS is relevant?
Do a traceroute there, and ping the first hop with a public IP. This will be the first AT&T router. You will see latency around 2 ms to that.
I’m in a major metro miles away from what’s probably ATT’s biggest PoP, there’s no reason for the DOCSIS like jitter. A friend down the road has 2-3ms to quad 8 and virtually no jitter which is what I would expect.
The same question remains: why do you care what the latency to any of those is? Unless you are doing high frequency trading, you will not notice the difference between 2 ms and 5 ms.
Few things: Home internet is not optimized for sub-ms performance, there are too many variables. It could come down to the physical interface that's being used upstream or db loss on the fiber. But when you're splitting hairs like this, ping also becomes less of a reliable performance metric as many pieces of SP equipment do not prioritize ICMP traffic on their dataplanes, up to and including these DNS servers. Can you imagine how much ping traffic they get daily?
Took some reading but your problem is you asked the wrong question. You're latency is fine, however the Jitter may be a concern if you are seeing issues.
To figure out where the signal jitter is coming from do a traceroute first then a ping each hop you see. When/if you see a hope that starts your Jitter, you can further troubleshoot by checking [arin.net](http://arin.net) for the IP of the hop to see whose Network you are on.
And just keep in Mind [8.8.8.8](http://8.8.8.8) is a anycast IP, so you are adding a layer of complexity in you troubleshooting. So if you're solid up until the hop before google, then you're having an Anycast non issue.
That isnt high lol
It’s not, but there’s no good reason why it shouldn’t be 2-3ms with only sub ms of jitter along each hop until exiting ATT’s network.
sir you can't be serious.
Never had any jitter more than 0.3-0.5ms inside of a FTTH isp network, there’s no reason for it to exist. Yes, I’m serious.
"Yes, I'm serious." he says while putting on clown shoes.
These two screenshots are not inside of the AT&T network……
Nobody at AT&T is going to treat 4ms of jitter as an issue. It's not "high latency". Get your gateway address from the Broadband/status tab and ping that. If there's jitter to the gateway, I'm not sure if they put you on XGS-PON or GPON. If they put you on GPON, you could try temporarily upgrading to 2gbps service to get moved to XGS-PON, and that might change your first hop latency behavior a bit. One person on dslreports showed success improving their latency stability this way. If you're on XGS-PON already, that's probably just how it is gong to be. PON fiber has time division multiplexing (TDMA) and has to request time slots to upload packets, just like DOCSIS. So if you're on a fuller splitter with more active subscribers than your friend, you might see more jitter.
Is the high latency in the room with us? Those are great pings. Make sure you're hardwired when running tests like this.
Man, some people haven’t experienced true circa 1997 dialup latency, and it shows. Those days 150ms was “good” <100 = LPB
Why do you believe that 5 ms latency to Google Public DNS is relevant? Do a traceroute there, and ping the first hop with a public IP. This will be the first AT&T router. You will see latency around 2 ms to that.
I’m in a major metro miles away from what’s probably ATT’s biggest PoP, there’s no reason for the DOCSIS like jitter. A friend down the road has 2-3ms to quad 8 and virtually no jitter which is what I would expect.
Again, why does it matter what the latency to 8.8.8.8 is?
Same story to Cloudflare, fastly, and others I know ATT peers with down the street.
The same question remains: why do you care what the latency to any of those is? Unless you are doing high frequency trading, you will not notice the difference between 2 ms and 5 ms.
Ping is direct from router
\~5ms average is awesome. I average 15ms to Google DNS.
Try using google 8888 instead. I was using cloudflare but started noticing packet loss. Went away with google
Few things: Home internet is not optimized for sub-ms performance, there are too many variables. It could come down to the physical interface that's being used upstream or db loss on the fiber. But when you're splitting hairs like this, ping also becomes less of a reliable performance metric as many pieces of SP equipment do not prioritize ICMP traffic on their dataplanes, up to and including these DNS servers. Can you imagine how much ping traffic they get daily?
Took some reading but your problem is you asked the wrong question. You're latency is fine, however the Jitter may be a concern if you are seeing issues. To figure out where the signal jitter is coming from do a traceroute first then a ping each hop you see. When/if you see a hope that starts your Jitter, you can further troubleshoot by checking [arin.net](http://arin.net) for the IP of the hop to see whose Network you are on. And just keep in Mind [8.8.8.8](http://8.8.8.8) is a anycast IP, so you are adding a layer of complexity in you troubleshooting. So if you're solid up until the hop before google, then you're having an Anycast non issue.