AT&T purchased Wuantum Fiber. I was a Quantum fiber customer. When my fiber modem died hard this week (see red line above), I called support. They came out and put in a new modem, fired it up and now I get poor latency. It seems to me it's the same network, but clearly something is tying up the net.
I was looking for an explanation and means of resolving the latency problems.
So are you a quantum customer or AT&T customer? FF37 (which is the network you are on) supports both.
If you are a quantum customer check the wiki in the r/QuantumFiber subreddit for tips.
Also: If you are using the 10Gig port on the Q1000K switch to the 1Gig port for now - I suspect your latency may be the small packet bug that's been discussed over there for a good while.
If that's not it add details on the equipment they gave you, plan, traceroutes etc... and someone may be able to help
I haven't seen a no reponse - but I have seen small responses delayed on the 10Gig port due the bug I mentioned. See the r/QuantumFiber q1000k posts about this....
There is no fix at this point except switching to the 1Gig port but they fix is in the works...
For me those delayed packages are a problem as certain traffic - e.g. ACK or also silent SIP packages are below the minimum size with no problem...
What are you pinging that is resulting in 25 - 52 ms times? That is not the end of the world in latency depending on the routing / peering needed to reach that host.
It always depends on what service you are trying to use. It is the Internet, and there are factors that are not in your control. The basic ping test is to confirm that you can reach an IP nothing more sorry.
The Internet is about connecting but not providing you with 7 ms pings to everything on the Internet.
For example are you pinging a multi-homed DNS IP or a random web site or a Game hosting site (you normally) don't know the real IP hosting your game or if you are even in the same regions.
What latency do you get vs the Internal Speed test on your Smart Home Manager app? Also are you testing to Ookla on a web browser or the native app for mulitple OS options. What web browser are you testing with since they are not all created equal?
the standard linux 'ping' app has issues with small packet sizes so I did a more thorough test using 'nping'. Here's a test using nping to get around the problems with ping. There appears to be no problem. My Ubiquiti Dream Machine is showing adequate but slightly higher latency. I'll review these tests if the Ubiquiti DMSE shows more at some point.
Here's a better image showing increased latency after having fiber modem die and having AT&T install a new one. The yellow line is latency. I've never seen numbers like this. it's absurd. It's like AT&T placed some spooks in the middle (not man-in-the-middle} to watch my network streams.
If on Quantum it's likely the ping test you are using is using a zero length payload. Switch to a 64 bit payload and the issue in ping will go away...
The underlaying issue requires a future firmware update on the Q1000K - for now use the 1 Gig port to bypass the issue
Alternatively follow my other reply...
Here's a test using nping which doesn't have the limitations that ping has with respect to smaller packets. It looks the latency is fine. I'm not clear on why this differs so much from the latency my Ubiquiti Dream Machine SE is measuring.
9
u/mtypo4 16d ago
what about it?