Gigabit Fiber Upload speed gotten significantly slower since Apr 18 2025 (San Francisco)

[cronos17]

Yes, using my own gateway and an Adtran 411 ONT I believe.

[cronos17]

directly from the gateway, latency looks good.

[klui]

You may want to double check. Your GW stats only show one value for latency which is probably associated with idle. Your posted results' idle values are in the expected range. Your newer results show 3 numbers, associated with idle, download, and upload.

[cronos17]

turned of QOS and latency looks better

Code: Select all

❯ speedtest

   Speedtest by Ookla

      Server: Sonic.net, Inc. - Santa Rosa, CA (id: 62981)
         ISP: Sonic.net, LLC
Idle Latency:     3.18 ms   (jitter: 0.40ms, low: 2.47ms, high: 3.54ms)
    Download:   940.10 Mbps (data used: 459.1 MB)
                 15.78 ms   (jitter: 1.23ms, low: 3.17ms, high: 46.76ms)
      Upload:   939.76 Mbps (data used: 763.1 MB)
                  8.74 ms   (jitter: 0.49ms, low: 3.60ms, high: 11.20ms)
 Packet Loss:     0.0%
  Result URL: https://www.speedtest.net/result/c/98e7da8d-1d06-426d-b1aa-4c0cc2547a67

  ~ ····································································································································  13s
❯ speedtest

   Speedtest by Ookla

      Server: Sonic.net, Inc. - Santa Rosa, CA (id: 62981)
         ISP: Sonic.net, LLC
Idle Latency:     3.52 ms   (jitter: 0.37ms, low: 2.52ms, high: 3.64ms)
    Download:   938.85 Mbps (data used: 459.2 MB)
                 15.56 ms   (jitter: 1.36ms, low: 3.16ms, high: 44.72ms)
      Upload:   934.35 Mbps (data used: 480.3 MB)
                  6.40 ms   (jitter: 9.38ms, low: 4.25ms, high: 349.53ms)
 Packet Loss:     0.0%
  Result URL: https://www.speedtest.net/result/c/c2baa3f6-9733-4242-aef1-c7cf5b187ddc

[kgc]

Thanks for the test results. We'd missed some IPv6 tuning necessary for good speedtest performance and also applied some additional NIC tuning options this morning which has improved how things look on our end too.

[cronos17]

Thank you so much for the explanation of the resolution. Glad to be a part of getting this resolved.

[joyjit]

BTW, just reporting back on my original issue:

My upload speeds are back to NORMAL, since Apr-29:
https://www.speedtest.net/result/c/7d26 ... 9bc65af909
https://www.speedtest.net/result/c/0827 ... 30aff571df
https://www.speedtest.net/result/c/666a ... 7325dc601c

All showing 900+ Mbps Up and Down

[cjd_1986]

Thanks for the test results. We'd missed some IPv6 tuning necessary for good speedtest performance and also applied some additional NIC tuning options this morning which has improved how things look on our end too.

Anyway you can look into why my upload is high ping? Been TS this for a while and involving noc and stuff, we've just about had a tech out 3 times to swap just about everything but the drop itself even tried eero from you guys rented and direct and yeah the uploads always very wonky and will introduce several constant huge ping spikes making stuff like gaming near to impossible to accomplish.


Speedtest by Ookla

Server: Sonic.net, Inc. - Santa Rosa, CA (id: 62981)
ISP: Sonic.net, LLC
Idle Latency: 3.01 ms (jitter: 0.08ms, low: 2.99ms, high: 3.13ms)
Download: 948.93 Mbps (data used: 428.1 MB)
14.75 ms (jitter: 0.53ms, low: 2.70ms, high: 19.84ms)
Upload: 948.18 Mbps (data used: 464.2 MB)
38.89 ms (jitter: 1.67ms, low: 2.93ms, high: 41.63ms)
Packet Loss: 0.0%
Result URL: https://www.speedtest.net/result/c/7fe8 ... d052084264

Speedtest by Ookla

Server: Sonic.net, Inc. - Santa Rosa, CA (id: 62981)
ISP: Sonic.net, LLC
Idle Latency: 3.21 ms (jitter: 0.11ms, low: 3.02ms, high: 3.27ms)
Download: 950.43 Mbps (data used: 452.6 MB)
16.53 ms (jitter: 0.94ms, low: 6.40ms, high: 21.60ms)
Upload: 947.89 Mbps (data used: 476.4 MB)
59.92 ms (jitter: 7.01ms, low: 2.79ms, high: 80.23ms)
Packet Loss: 0.0%
Result URL: https://www.speedtest.net/result/c/981d ... c1a4875005

[kgc]

The short answer is that if you saturate a network link latency over that link will increase more or less in relationship to the depth of the queues on that link.

On the second test : "Idle Latency: 3.21 ms (jitter: 0.11ms, low: 3.02ms, high: 3.27ms)" which seems fine.
And during the upload phase - you got 947.89 Mbps which is effectively the max line rate of your serivce and had the following latency: "59.92 ms (jitter: 7.01ms, low: 2.79ms, high: 80.23ms)" which seems reasonable given a saturated link.

If you're routinely doing large transfers or otherwise saturating your network, setting up QoS to prioritize the different applications is the standard way to mitigate this problem to allow your gaming traffic to continue to enjoy low-latency by limiting the total amount of bandwidth available to the applications (or hosts) that are causing the saturation.

[cjd_1986]

The short answer is that if you saturate a network link latency over that link will increase more or less in relationship to the depth of the queues on that link.

On the second test : "Idle Latency: 3.21 ms (jitter: 0.11ms, low: 3.02ms, high: 3.27ms)" which seems fine.
And during the upload phase - you got 947.89 Mbps which is effectively the max line rate of your serivce and had the following latency: "59.92 ms (jitter: 7.01ms, low: 2.79ms, high: 80.23ms)" which seems reasonable given a saturated link.

If you're routinely doing large transfers or otherwise saturating your network, setting up QoS to prioritize the different applications is the standard way to mitigate this problem to allow your gaming traffic to continue to enjoy low-latency by limiting the total amount of bandwidth available to the applications (or hosts) that are causing the saturation.

What's weird is in my case if I connect to a VPN those numbers become normal (like 5ms) and not high because it takes a different route to the server. This happens even on a direct line to the ONT without any routing, the lines barely saturated at all times yet acts like its struggling the longer something that needs stability runs like gaming, a video call or voice. Why does the VPN fix all the high latency issues that never happened until last month? Done swapped everything in and out of the equation and they're pretty much saying its a routing issue at this point and investigating if its within sonic net or you know level 3 or something.