Every time your browser loads a page, the server answers with a three-digit status code. You normally never see it – until something goes wrong. Knowing what the codes mean tells you instantly whether to fix something on your side or simply wait.
The five families
- 1xx – informational, rarely visible.
- 2xx – success. 200 OK means everything worked.
- 3xx – redirects. The page moved, and your browser follows automatically.
- 4xx – client errors. Something about the request is wrong – often on your side.
- 5xx – server errors. The website itself has a problem.
403 Forbidden
The server understood the request but refuses it. Common causes: you are not logged in, your IP address or VPN is blocked, or the site blocks automated traffic. What to do: log in again, turn off VPN, clear cookies. For outage checks, a 403 still proves the server is online.
404 Not Found
The page doesn’t exist – a typo, a deleted page or an old link. The site itself is usually fine. What to do: check the address, go to the homepage and search.
429 Too Many Requests
You (or your network) sent too many requests in a short time, and the service is slowing you down. Common during big launches and with APIs. What to do: wait a few minutes. Repeatedly refreshing makes it worse.
500 Internal Server Error
A generic “something broke on our side”. It is the website’s problem. What to do: wait and try again; check our global scan to see if others are affected.
502 Bad Gateway
A server in the middle (like a load balancer or CDN) got a bad answer from the server behind it. Often seen during deployments and outages. What to do: wait a few minutes.
503 Service Unavailable
The server is overloaded or in maintenance. Typical during huge traffic peaks, such as a major game launch. What to do: wait; check the official status page for maintenance windows.
504 Gateway Timeout
The middle server waited too long for an answer. Like 502, it points to problems behind the scenes. What to do: wait and retry.
Cloudflare errors 520–530
Many sites run behind Cloudflare. Codes like 521 (web server down) or 522 (connection timed out) mean Cloudflare is working but the website’s own server isn’t answering. If many unrelated sites show Cloudflare errors at once, check our Cloudflare status page.
How DownFromSpace uses status codes
When our probes test a service from 50 countries, any normal answer below 500 counts as online – even 403 or 405, because the server clearly responded. 5xx codes, timeouts and no answer count as down. Read more in how outage detection works.