A page refuses to load and throws a number at you — 404, 500, 502, 503. Each one is telling you something specific. Here is what every common website error code actually means, and whether it is a problem you can fix or one you simply have to wait out.
You click a link and instead of the page you expected, the screen hands you a cold-looking number and a few words of explanation. 404 Not Found. 503 Service Unavailable. For most people these codes are meaningless noise — a sign that something broke, with no clue as to what or why. But each one carries a precise meaning, and once you understand the pattern behind them, you can tell in seconds whether the problem is yours to solve or the website's. This guide breaks down every common HTTP error code, explains what is happening behind the scenes, and tells you exactly whether you can fix it.
What a Website Error Code Actually Is
Every time you load a web page, your browser sends a request to a server and the server sends back a status code along with its response. Most of the time that code is 200 OK, which simply means "here is the page you asked for" — and you never see it because everything worked. You only notice a status code when something goes wrong and the server returns an error instead of a page.
These codes are grouped into ranges, and the first digit tells you almost everything you need to know:
- 4xx errors mean the problem is with the request — something about what your browser asked for was wrong, blocked, or no longer exists. These are often fixable on your end.
- 5xx errors mean the problem is on the server — the website's own infrastructure failed to deliver the page. These are almost never something you can fix; you wait for the website's team to resolve them.
That single distinction — 4xx is usually about you, 5xx is about them — is the most useful thing you can learn about error codes. Keep it in mind as we work through each one below.
404 Not Found
The 404 is the most famous error code on the internet, and the most misunderstood. It does not mean the website is down. It means the server is alive and well, but the specific page you requested does not exist at that address. The link you followed might be outdated, the page may have been moved or deleted, or there could simply be a typo in the URL.
Can You Fix It?
Often, yes. A 404 is one of the few errors where you have real control:
- Check the URL for typos. A single wrong character is enough to trigger a 404. Re-type the address carefully if you entered it manually.
- Trim the address. Delete everything after the main domain and load the homepage, then navigate to the page you wanted from there.
- Search for the page instead. Type the site name and the page topic into a search engine — the content may still exist at a new address.
If you reached the 404 by clicking a link on the site itself, the fault is with the website's broken link rather than anything you did wrong.
403 Forbidden
A 403 means the server understood your request perfectly but is refusing to fulfil it. You are being denied access on purpose. This can happen for a range of reasons: the content is restricted to logged-in users, the page is geo-blocked in your country, or the site's security system has flagged your IP address as suspicious.
Can You Fix It?
Sometimes. It depends on why you are being blocked:
- Log in. If the content requires an account, signing in will often clear the 403 immediately.
- Check for geo-restrictions. Some pages are unavailable in certain regions due to licensing or legal rules. This is common with streaming and news sites.
- Clear cookies or try a different network. If your IP has been flagged, switching to mobile data or clearing site data can sometimes resolve it — though if a security system has blocked you deliberately, there may be nothing you can do.
429 Too Many Requests
A 429 appears when you have sent too many requests to a server in a short space of time and it has temporarily told you to slow down. This is called rate limiting, and it is a defensive measure that protects servers from being overwhelmed — whether by accident or by automated abuse.
Can You Fix It?
Usually, yes — by waiting. The fix is simply patience:
- Stop refreshing. Hammering the refresh button only resets the clock and makes the block last longer.
- Wait a minute or two. Rate limits are almost always temporary and lift on their own.
- Disable aggressive extensions. Some browser tools fire off background requests that quietly trip rate limits without you realising it.
500 Internal Server Error
The 500 is the server's way of saying "something went wrong on my end, but I am not sure how to describe it." It is a catch-all error that fires when the website's code crashes, a database query fails, or an unexpected bug stops the server from completing your request. Crucially, this has nothing to do with your device, your browser, or your connection.
Can You Fix It?
No — this one is on the website. There is no setting on your end that will resolve a genuine 500 error. That said, it is worth a couple of quick checks before you give up:
- Refresh once after a short pause. Some 500 errors are momentary and clear on the next attempt.
- Try again later. If the site's developers have shipped a broken update, the error will persist until they fix it.
Beyond that, all you can do is wait for the website's team to repair whatever broke.
502 Bad Gateway
Modern websites rarely run on a single machine. Requests often pass through a chain of servers — a gateway or proxy sits in front, forwarding your request to the server that actually generates the page. A 502 Bad Gateway means that front-line server reached out to the one behind it and received an invalid or broken response. In plain terms: two of the website's own servers failed to talk to each other properly.
Can You Fix It?
No — this is a server-side failure. The breakdown is happening inside the website's infrastructure, somewhere you cannot reach. A 502 typically points to an overloaded backend, a crashed service, or a misconfigured proxy. You can refresh in case it was a brief hiccup, but a persistent 502 means the website's engineers need to step in.
503 Service Unavailable
A 503 is the server telling you, quite directly, that it cannot handle your request right now. Unlike a crash, this is often deliberate. The most common causes are scheduled maintenance — where the team intentionally takes the site offline for a short window — and traffic overload, where a surge of visitors arrives faster than the server can cope with. A product launch, a viral post, or a news event can all trigger a 503 in minutes.
Can You Fix It?
No — but a 503 is usually temporary by nature. Because it is frequently tied to maintenance or a traffic spike, the situation tends to resolve itself once the work finishes or the rush subsides:
- Wait and retry. Many 503 pages include a "try again shortly" message for exactly this reason.
- Check the service's status page or social media. Planned maintenance is often announced in advance, and outages caused by traffic spikes are usually acknowledged quickly.
504 Gateway Timeout
A 504 is closely related to the 502. Again, a front-line server is forwarding your request to a server behind it — but this time, instead of getting a broken response, it gets no response at all within the time it is willing to wait. The backend server is too slow, stuck, or unresponsive, so the gateway gives up and returns a timeout.
Can You Fix It?
Mostly no, but occasionally yes. A 504 is generally a server-side problem — an overloaded or stalled backend that has nothing to do with you. Very rarely, an unusually slow or unstable connection on your end can contribute, so it is worth one quick check:
- Refresh after a short wait. If the backend was momentarily swamped, a retry may succeed.
- Confirm your own connection is stable. Load a couple of other sites — if they are fine, the 504 is firmly the website's problem to solve.
A Global Outage, or Only on Your End?
By now the pattern should be clear. A 4xx error is often something you can act on — a bad link, a login you skipped, a rate limit to wait out. A 5xx error almost always means the website's own servers have failed, and no amount of local troubleshooting will bring the page back. But that raises one final, decisive question: when you hit a 500, 502, or 503, is the service genuinely down on a global scale — or is something unusual happening only on your end?
The fastest way to find out is Downscanner, a community-driven platform where real users report and vote on outages as they happen. Instead of guessing, you can search for the service and see at a glance whether a wave of other people are hitting the same error at the same moment. If reports are surging across multiple regions, you have your answer: the outage is real and widespread, and all you can do is wait it out. If almost no one else is reporting a problem, that points to something local — your network, your device, or a stale cache — and the fixes in this guide are your path forward.
Error codes tell you what broke. Downscanner tells you who it broke for. Together, they turn a confusing wall of numbers into a clear, simple answer:
Is the problem the service itself, or something on my side?
Bookmark Downscanner so the next time a cryptic error code stops you in your tracks, you know exactly where to go.
