Monitoring
Status Pages
Pricing
Last updated: 4 February 2026
HTTP error codes are more than just messages shown to users, They’re signals from distributed systems. For engineers, SREs, and platform teams, these codes are often the first indicator of degraded reliability, misconfiguration, or upstream failure.
This guide focuses on how HTTP error codes behave in real production environments: behind CDNs, load balancers, reverse proxies, APIs, and microservices. Rather than just defining error codes, we explain why they happen, what they usually mean operationally, and what to check first when you encounter one.
| Code | Class | Client or Server | Typical production meaning |
|---|---|---|---|
| 400 | 4xx | Client | Malformed or invalid request |
| 401 | 4xx | Client/Auth | Missing or invalid authentication |
| 403 | 4xx | Client/Auth | Permission denied |
| 404 | 4xx | Client/App | Route or resource not found |
| 408 | 4xx | Client/Network | Client timed out waiting for response |
| 500 | 5xx | Server | Unhandled server-side failure |
| 502 | 5xx | Server/Infra | Bad gateway or upstream failure |
| 503 | 5xx | Server/Infra | Service unavailable (overload or maintenance) |
| 504 | 5xx | Server/Infra | Gateway timeout |
At a high level:
Operationally, this distinction is critical:
Misclassifying these errors can hide real incidents, trigger unnecessary alerts, and cause retries that amplify failures. Understanding the differences allows teams to design better alerts, retries, and incident responses.
The server could not process the request because it was malformed or invalid.
Authentication is required, but the request lacks valid credentials.
The server understood the request but refuses to authorise it.
The requested resource does not exist or cannot be located.
The server timed out waiting for the client to send the request.
The server encountered an unexpected condition that prevented it from fulfilling the request.
A server acting as a gateway or proxy received an invalid response from an upstream server.
In modern architectures, this usually means one service could not successfully communicate with another.
This error is most commonly generated by:
The server is currently unable to handle the request.
A gateway did not receive a timely response from an upstream server.
A 502 indicates an invalid response from an upstream service, while a 503 indicates the service is unavailable (often due to overload or maintenance).
Generally no. Search engines expect some 4xx responses. Persistent 404s on important pages, however, should be addressed.
Most teams alert on sustained increases in 5xx error rates, not individual errors.
Yes. CDNs often generate their own 5xx responses when origin servers fail to respond correctly.
HTTP error codes are most useful when combined with uptime monitoring, error rate alerting, and regional checks. Tools like StatusCake help teams detect, classify, and respond to these failures before users notice.
Share this
4 min read On 13th August 2026, a storm knocked out cooling at RadiusDC’s Phoenix data centre, which hosted essential Namecheap operations. To protect hardware from thermal damage, Namecheap took services offline while temporary chillers were brought in. The incident and recovery ran for roughly 30 hours, with Namecheap’s own site unreachable for about 11 hours 42 minutes
3 min read On Wednesday 19 August, Monzo had an outage. DownDetector logged more than 3,000 reports by midday. Monzo’s own statement was direct about what it did next: it activated Monzo Stand-in, its fully independent backup bank, while it investigated an issue affecting customers. By the end of the day, Monzo said the issue was resolved and
3 min read GitHub’s incident on 17 August 2026 ran from 13:28 to 21:15 UTC, seven hours and forty-seven minutes. At peak, web and API traffic saw error rates of around 20%, while archive and raw-content downloads reached roughly 50%. SAML and OIDC authentication, SCIM and Team Sync were affected alongside Git operations, Actions, Pages, Issues, Pull Requests
3 min read Adding a new website, launching a customer portal, or handing a service to a new team should be straightforward. Setting up monitoring is part of that job, but it is easy for a manual step to be missed when information is spread across several systems. StatusCake now integrates with viaSocket, giving teams a way to connect
7 min read A website may be standing and still be in trouble. It may answer a request, return a cheerful 200 OK, and yet load slowly enough that visitors begin to lose patience. Its certificate may be nearing expiry. Its domain records may have changed. A server may be filling its disk in the background, patient and
6 min read StatusCake tells you that something might be broken. Hermes can check whether it really looks broken, decide who should hear about it, send the email, and keep the record for tomorrow morning’s summary.
Find out everything you need to know in our new uptime monitoring whitepaper 2021
