Speed test having real issues

[DWomack]

Don't know if the problem is speedtest-cli.

I have tried it on another Pi and it is giving really screwy results.

I have been running this for many months, but in the last two weeks it's like speed test has gone flaky.

No issue with the ping chart across the bottom.

Am I the only one seeing this problem?

[cvsickle]

I'm having major issues with it too, but jitter spikes also. My internet has been usable pretty much constantly, and no devices seem to be having speed issues.

[DWomack]

Trouble with Speedtest and Speedtest pingI think the issue is with Speedtest-cli, which internet-pi uses. Mine is set to test http to GitHub and Google. I am using a VZ ASK cube for home internet. It has issues as you can see from the http graph.  It disconnects and reconnects every 4 hours 12 minutes. Like clockwork since the first of March. DennisSent from my iPhoneOn Jun 9, 2023, at 7:42 PM, cvsickle @.***> wrote: I'm having major issues with it too, but ping issues also. My internet has been usable pretty much constantly, and no devices seem to be having speed issues.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

[DWomack]

So I managed to buy an 8 gig Pi4 kit from Chicago Electronics and fully updated, and then installed Docker and Docker Compose.

I looked at the internet-pi code and found internet-monitoring buried there.

Glad to say it works.

[DWomack]

Close, but no cigar. It's having the same issues as internet-pi. The problem may be with speedtest-exporter. When you look at metrics sometimes speedtest_up returns 0.0.

[DWomack]

I have VZ 5G Home Internet via ASK Cube firmware fully patched.

The issues ie: failures are due to the way the exporter handles errors that are returned by speedtest cli.

Speedtest cli occasionally throws errors when on VZ.

I installed the latest speedtest cli from Ookla on a box with Ubuntu 22.04 fully patched for testing. Running it from the command line I see it error occasionally.

I suspect the exporter is not catching the error and retrying the test when speedtest cli is called.

The http calls to www.Google.com and www.GitHub.com only fail when the cube has been power cycled. This is working fine though speedtest is not.

[DWomack]

dennis@xxxx:~$ speedtest --progress=no

Speedtest by Ookla

  Server: Verizon - Nashville, TN (id: 30809)
     ISP: Verizon Wireless

Idle Latency: 33.71 ms (jitter: 6.96ms, low: 28.28ms, high: 42.88ms) Download: 207.42 Mbps (data used: 374.1 MB)
113.92 ms (jitter: 37.85ms, low: 36.66ms, high: 615.84ms) Upload: 20.35 Mbps (data used: 26.3 MB)
83.73 ms (jitter: 18.81ms, low: 45.79ms, high: 287.21ms) Packet Loss: 0.0% Result URL: https://www.speedtest.net/result/c/dc596e4c-1e78-4c2f-9c9d-f9aea781045d dennis@xxxx:~$ speedtest --progress=no

Speedtest by Ookla

  Server: Verizon - Nashville, TN (id: 30809)
     ISP: Verizon Wireless

Idle Latency: 34.34 ms (jitter: 5.71ms, low: 29.98ms, high: 39.97ms) Latency: FAILED
[error] Cannot read:

[DWomack]

I have confirmed the issue is with Verizon's Nashville Speedtest server. That is the server that is auto selected. If I specify a different server the issue goes away.

Verizon may have under provisioned the server. A lot of C-Band is coming online in Nashville, not to mention mmWave. Everybody and their brother may be testing their speeds against that server.

[DWomack]

VZ finally fixed the issue with their Nashville Speedtest.net server.

[DWomack]

Problem is back.

[github-actions[bot]]

This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark issues as stale.

[github-actions[bot]]

This issue has been closed due to inactivity. If you feel this is in error, please reopen the issue or file a new issue with the relevant details.