Skip to main content

Is Speedtest by Ookla Down?

No — Speedtest by Ookla is up

Reachable from all 8 checked regions

Average response time: 441ms

Last checked · checks run every 6 hours

Official status page: https://status.ookla.com

Speedtest by Ookla uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
362ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 8 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

8-day clean streak
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: no data
Jul 30: no data
Jul 31: no data
Aug 1: no data
Aug 2: no data
Aug 3: no data
Aug 4: no data
Aug 5: no data
Aug 6: no data
Aug 7: no data
Aug 8: no data
Aug 9: no data
Aug 10: no data
Aug 11: no data
Aug 12: no data
Aug 13: no data
Aug 14: no data
Aug 15: no data
Aug 16: 100.00% uptime, 8 checks
Aug 17: 100.00% uptime, 31 checks
Aug 18: 100.00% uptime, 40 checks
Aug 19: 100.00% uptime, 32 checks
Aug 20: 100.00% uptime, 32 checks
Aug 21: 100.00% uptime, 23 checks
Aug 22: 100.00% uptime, 32 checks
Aug 23: 100.00% uptime, 40 checks
Jul 25 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

fra
326ms
DNS 158ms TCP 1ms TLS 7ms TTFB 321ms
gru
526ms
DNS 40ms TCP 2ms TLS 7ms TTFB 523ms
iad
651ms
DNS 428ms TCP 1ms TLS 10ms TTFB 648ms
jnb
422ms
DNS 118ms TCP 0ms TLS 6ms TTFB 418ms
lax
238ms
DNS 106ms TCP 1ms TLS 6ms TTFB 233ms
lhr
191ms
DNS 35ms TCP 2ms TLS 8ms TTFB 174ms
nrt
433ms
DNS 237ms TCP 1ms TLS 5ms TTFB 429ms
ord
314ms
DNS 68ms TCP 13ms TLS 25ms TTFB 311ms
sin
759ms
DNS 311ms TCP 2ms TLS 10ms TTFB 756ms

What Speedtest by Ookla does

Speedtest by Ookla measures connection bandwidth and latency against a large network of hosted test servers, through its website and mobile apps. It is the reference people reach for when a connection feels slow, and internet providers and businesses cite its results, which makes its own availability oddly consequential during a broadband fault.

What an outage looks like

The test page loads but stalls while selecting a server, or the test starts and never reports a result. Apps report that no test server could be found. Because people open Speedtest precisely when their connection is misbehaving, a failed test is ambiguous by nature: it may be the service or the connection under test.

What to do about it

Try a second measurement tool before concluding anything, since a failed Speedtest during a suspected broadband fault tells you very little on its own. Check status.ookla.com to separate the two, and try selecting a different test server by hand. If other sites load normally while Speedtest alone fails, the connection is working.

Is it down for everyone, or just you?

If this page says Speedtest by Ookla is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

Speedtest by Ookla outage FAQ

Speedtest will not load. Is my internet down?
Not necessarily, and this is the hardest case to read. If other websites load, the connection is up and the fault lies with Speedtest or the nearest test server. If nothing loads, the connection is the problem and Speedtest failing is a symptom rather than the cause. Test a second site first.
Why can Speedtest fail while everything else works?
The test depends on a nearby hosted server, and those are run by many different operators rather than by Ookla alone. When the server your client selects is offline or overloaded, the test fails even though the wider service is healthy. Choosing a different server by hand often gets a result.
Is a slow result an outage?
No, and the distinction matters. A completed test showing poor throughput is a measurement of your connection, which means the service worked correctly. An outage means the test cannot run at all. A slow number belongs in a conversation with your internet provider rather than in a report to Ookla.
Does an Ookla outage affect my provider's own speed test?
It depends on what they run. Many providers host independent test tools on separate infrastructure, which keep working. Others use a licensed Ookla platform under their own branding, and those can be affected by the same incident. If the provider's tool works while speedtest.net does not, it is running independently.

How we measure this

  • We request Speedtest by Ookla's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Speedtest by Ookla publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Speedtest by Ookla goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required