What is HTTP error 503 and how do you fix it?
It may not always be obvious what's behind a 503 error, but there are steps you can take to get back online
An HTTP 503 error is encountered when your browser encounters a website that is unable to establish a connection with its server.
Many people seem to confuse this for the classic 502 bad gateway, but it's a slightly more troubling issue, particularly if you're not an experienced IT professional.
If you're lucky, simply refreshing the page can and should resolve the issue, but there will be times when this easy fix is not enough.
While it might be worth troubleshooting for issues on your own network, in the majority of cases, a 503 error is caused by issues with the web server that the browser is trying to reach. If that is the case, there isn't much one can do aside from reaching out to the IT admin that runs the page, if you even have that information to hand.
What does HTTP error 503 mean?
Essentially, the 503 error is your first warning that something is preventing the browser from accessing the website server. This is where said server is unable to deal with the information requested, though the exact cause won't be made clear at the time. Often you'll just get the annoyingly vague advice to 'try again later'.
A number of popular sites had 503 issues last year due to the infamous Fastly outage. That included payment sites such as PayPal and Shopify, internet forums like Quora and Reddit, and also streaming giants like Spotify and Twitch. This also affected gov.uk, as well as numerous online newspapers and news outlets, including the New York Times, BBC, Financial Times, CNN, the Guardian, Bloomberg News, and The Verge, with the latter having to use Google Docs to publish stories.
While many of the websites showed the "503 error", the cloud computing services provider described the issue as a "global CDN disruption", with its own website displaying an "I/O error" message.
What causes an HTTP error 503?
When met with an HTTP error 503, the first question is usually “why?”, coupled with the hope that determining the cause of the issue will help us solve it quickly and painlessly. Unfortunately, this is not always the case.
Similar to other HTTP errors, determining the root cause of the Error 503 is much harder than one would expect – especially without technical IT expertise. However, there are a few possible scenarios that can be considered as plausible causes for an HTTP error 503.
In the majority of cases, the 503 is triggered when the website in question is no longer able to connect with its supported server, meaning that any information requested or issued by your browser is simply hitting a wall. This usually happens when the server experiences a technical issue, is undergoing maintenance works, or is facing some sort of malicious disruption, such as a denial of service (DDoS) attack. Regardless of the cause, this information will likely not be readily available.
Frequent technical issues, such as those occurring multiple times a month, can be especially disruptive and excessive downtime can cause serious financial difficulty – especially if it heavily depends on online traffic or orders made through e-commerce. Perhaps the best example of this is Amazon's Prime Day disruption in 2018, which should serve as a blueprint for businesses in how not to handle an outage.
Hence, if your website is displaying an HTTP error 503 more often than its own home page, it might be worth switching hosting providers.
Although an HTTP error 503 can diminish the number of customers visiting the site, it can also be caused by an inundation of visitors, such as during seasonal sales. In these cases, the server remains connected, yet is incapable of supporting the avalanche of requests from many different users.
Alternatively, this can also be caused by malicious traffic instead of eager customers, such as in the case of distributed denial of service (DDoS) attacks. Misconfigured web apps may also cause a 503 error to appear, such as a plugin conflict caused by WordPress, while regular 503 errors could suggest an issue with the domain name system (DNS), whether that's an incorrect server configuration or an issue with the DNS server itself.
How to fix an HTTP error 503
The fastest method to resurrect the site you're trying to access is by refreshing the web page and hoping that this will solve the problem.
However, there are also several other steps you can take to make sure the problem isn't linked to your connection. For example, you can restart your router or computer. If an error message shows "Service Unavailable – DNS Failure", then this usually means there may be an error with your hardware configuration, which thankfully can be corrected by performing a reboot. You might find there is a problem with the allocated DNS server, but this is normally resolved by choosing to use a different DNS server.
Navigate disruption and drive positive business outcomes with cloud migration
Build highly resilient, efficient digital business models through the cloudFree Download
However, if the 503 error is a result of a problem found on the server's side, then unfortunately there isn't a lot you can do yourself to remedy it. This is where the IT administrator for the site should troubleshoot the issue to find a solution to the fault that users are reporting if they are encountering HTTP 503 errors. If you find yourself in that position and discover that updates need to be applied to a site, it's recommended to schedule them when your site's traffic is likely to be lowest, so your users don't regularly come across errors.
Alternatively, if recurring HTTP 503 errors are regularly caused by traffic spikes, it's best to use this as a sign that you might want to increase your web server resources investment. In addition to this, a surge of traffic could be the result of a denial of service (DoS) attack, in which case it might be a clever idea to approach your hosting provider to ask about the possible mitigations they can offer you to prevent attacks in the future.
Further investing in security protections or increasing the frequency of patch management could also serve to prevent any subsequent incidents from occurring. Several providers already include DDoS protection as part of their default packages, which may restrict the number of users that are allowed to access a site at any one time.
Finally, should the HTTP 503 error be a result of a programming bug, you'll need to undergo further investigation to pinpoint the issue and rectify it permanently.
The state of Salesforce: Future of business
Three articles that look forward into the changing state of Salesforce and the future of businessFree Download
The mighty struggle to migrate SAP to the cloud may be over
A simplified and unified approach to delivering Enterprise Transformation in the cloudFree Download
The business value of the transformative mainframe
Modernising on the mainframeFree Download
The Total Economic Impact™ Of IBM FlashSystem
Cost savings and business benefits enabled by FlashSystemFree Download