Is speedtest.net down or not working?

What happened to speedtest.net, why did the website go down and not work? Here you can see who else is having the same problem with speedtest.net, as well as possible solutions. According to our statistics, the following most often do not work: Website, Login, Account, Mobile App.

Current status: No failures

At the moment, according to our data, speedtest.net is working fine, but single failures are possible. If speedtest.net does not work for you, then report your problem and write a comment.
Add comment

What to do if the site speedtest.net is not available? Try our guide.

speedtest.net outage reports in the last 24 hours

speedtest.net - error and failure reports, troubleshooting methods

Leave your comment describing the failure and share with other users how to solve the problem.
  • No registration required.
  • Messages with obscene language and insults, as well as breaking the law, are not allowed to be published.
  • Active links in the text of the message are not published, but displayed in plain text.
  • It is forbidden to post your own and other people's personal data: addresses, phone numbers, emails, accounts in instant messengers, etc.

Technical information

Main page title:
Speedtest by Ookla - The Global Broadband Speed Test
Main page description:
Use Speedtest on all your devices with our free desktop and mobile apps.
Main page keywords:
ookla,speed,test,speedtest,speed test,bandwidth speed test,internet speed test,broadband speed test,speakeasy,flash,cnet,internet,network,connection,broadband,bandwidth,latency,ping,throughput,download,upload,connection,dsl,adsl,cable,t1,isp,voip,ip,ip address,tcp
Protocol:
https
Status code:
200
Page size:
129.8 KB
Response time:
0.167sec.
IP:
151.101.2.219
Response headers:
date: Mon, 30 Sep 2024 20:09:22 GMT
content-type: text/html; charset=utf-8
transfer-encoding: chunked
connection: close
cache-control: private
x-frame-options: DENY
content-security-policy: frame-ancestors 'none'; upgrade-insecure-requests
access-control-allow-credentials: true
set-cookie: euIPAddressNotice=true; Path=/; Expires=Sun, 29 Dec 2024 20:09:22 GMT,__cf_bm=NG64O7cx1V6kO93s0f1KuKojdkV1VhK8R7fZ9n3I9zI-1727726962-1.0.1.1-9ZImFGvtAJDR5M3TFHHjJtpzj_aZEbTlGWbce7sQFcOhVRnXdynx0Wk79ehNqdbW1w6Ka08PQT47SZbfnigbeQ; path=/; expires=Mon, 30-Sep-24 20:39:22 GMT; domain=.www.speedtest.net; HttpOnly; Secure; SameSite=None
etag: W/"20778-WIzhXtvtMRz06put+RAI2q5B4EU"
vary: Origin, Accept-Encoding
cf-cache-status: DYNAMIC
server: cloudflare
cf-ray: 8cb6d9ad6be76670-AMS
DNS records:
A address151.101.194.219
ttl14400
A address151.101.130.219
ttl14400
A address151.101.2.219
ttl14400
A address151.101.66.219
ttl14400
AAAA address2a04:4e42:400::731
ttl14400
AAAA address2a04:4e42::731
ttl14400
AAAA address2a04:4e42:600::731
ttl14400
AAAA address2a04:4e42:200::731
ttl14400
MX exchangealt2.aspmx.l.google.com
priority5
MX exchangeaspmx.l.google.com
priority1
MX exchangeaspmx2.googlemail.com
priority10
MX exchangealt1.aspmx.l.google.com
priority5
NS valuens-787.awsdns-34.net
NS valuens-1071.awsdns-05.org
NS valuens-1643.awsdns-13.co.uk
NS valuens-372.awsdns-46.com
TXT entries_globalsign-domain-verification=vmboLy_o2GxMJgzVZCREzPoasKKYdy8TP-4sfex0cz
TXT entriesgoogle-site-verification=gMY5s5pgG8KtwIC7UxMP4sb7URe2hdAWfHHbTtytLrw
TXT entriesv=spf1 include:_spf.google.com include:sendgrid.net include:mail.zendesk.com ~all
TXT entries9sptn7qrkc217ndpzfpllrfkpttppnd1
TXT entriesgoogle-site-verification=8LzC5phVf0sQEH4B1XsY1UuSITg4TRv_ddAqsRhm9lY
TXT entries_globalsign-domain-verification=B57sRQpmte4G4w-gavZbVNmmNsMxGp5kcL19UP2599
TXT entriesfacebook-domain-verification=jpz6991hmnajruf5oaiutvjsr0jnx9
SOA nsnamens-1643.awsdns-13.co.uk
hostmasterawsdns-hostmaster.amazon.com
serial1
refresh7200
retry900
expire1209600
minttl86400

SEO headers

h3 Speedtest®
h3 Ziff Davis
h3 Ookla® Brands
h3 Apps
h3 Languages

How to solve problems with speedtest.net

Errors on the speedtest.net website can be either on the server side or on your side (client side). If there is practically nothing to be done about errors on the server side (it remains only to wait for the site to work again), then with errors on the client side it is possible to solve the problem with the availability of speedtest.net on your own.