What it means
A 503 Service Unavailable error means the website's server is temporarily unable to handle requests, usually because it is overloaded or down for maintenance. It is meant to be temporary. It is the website's problem, not yours, so visitors usually just need to wait while the site owner frees up the server.
Common causes
- Too much traffic for the server to handle
- Planned or stuck maintenance mode
- The server ran out of CPU, memory or worker processes
- The application or app pool has stopped or crashed
- A plugin, cron job or bot flooding the site with requests
- The hosting provider is limiting the account's resources
How to fix it
Work down the list. Each fix is safe to try before moving on to the next.
FIX 01Wait a few minutes, then reloadEASY
- Wait two to five minutes.
- Press
F5on Windows orCommand + Ron a Mac to reload. - Avoid pressing reload over and over, which adds load to a struggling server.
Why it helps: A 503 is designed to be temporary, and the server often recovers once a traffic spike or maintenance ends.
FIX 02Check for a maintenance or outage noticeEASY
- Read the error page itself; many sites say when they expect to be back.
- Check the company's official status page or social media accounts for an outage notice.
Why it helps: If the site announced maintenance, there is nothing to fix on your side.
FIX 03Try another browser or networkEASY
- Open the page in a private window or a different browser.
- Try on your phone using mobile data instead of Wi-Fi.
- If the site works there, turn off any VPN or proxy on your main device and try again.
Why it helps: Some sites or firewalls block traffic from certain networks or VPN addresses with a 503.
FIX 04Contact the websiteEASY
- If the error lasts more than an hour with no notice, contact the site's support.
- Tell them the page address and the time you saw the error.
Why it helps: Only the site owner can bring the server back.
// RUN THIS SITE? FIXES FOR SITE OWNERS
FIX 05Check server load and restart servicesMEDIUMSITE OWNERS
- In your hosting control panel, open the resource usage page and look for CPU, memory or process limits being hit.
- Restart PHP-FPM, the web server or the application from the control panel if your host allows it.
- On IIS, open IIS Manager, select
Application Poolsand start the site's pool if it is stopped (a 503.0 means the pool is stopped or disabled). - Check the error log and, on IIS, the Windows Event Log for why the service stopped.
Why it helps: A 503 usually means the server has no free capacity or the app behind it is not running.
FIX 06Remove a stuck WordPress maintenance modeMEDIUMSITE OWNERS
- Open
File Manageror connect with SFTP. - In the WordPress root folder (the one with
wp-config.php), look for a hidden file named.maintenance. - Delete it and reload the site.
- Re-run any update that did not finish.
Why it helps: WordPress creates .maintenance during updates and returns a 503 while it exists; an interrupted update can leave it behind.
FIX 07Find what is overloading the siteMEDIUMSITE OWNERS
- Check the access log for one IP address or bot making a very large number of requests.
- Temporarily disable recently added or heavy plugins by renaming their folders in
wp-content/plugins. - Turn on page caching so repeat visits do not hit PHP and the database every time.
- Ask your host whether they are rate limiting or throttling your account.
Why it helps: Removing the source of the load, or serving cached pages, frees capacity so normal requests succeed.
FIX 08Check Cloudflare if you use itADVANCEDSITE OWNERS
- View the source of the 503 page; if it contains
cloudflareorcloudflare-nginx, Cloudflare generated it. - In that case check
Security > Eventsin the Cloudflare dashboard and contact Cloudflare support with your domain, the time and timezone. - If the page does not mention Cloudflare, the 503 came from your own server; check its logs for overload or maintenance mode.
Why it helps: Knowing which side produced the 503 tells you whether to fix your server or contact Cloudflare.
FIX 09Send a Retry-After header during planned maintenanceADVANCEDSITE OWNERS
- When you take the site down on purpose, return status 503 with a
Retry-Afterheader giving the expected downtime in seconds. - Show a short friendly page explaining when the site will be back.
- Make sure the 503 response is not cached by your CDN, so visitors see the real site once you are done.
Why it helps: This tells browsers and search engines the outage is temporary and avoids stale error pages after recovery.
Check it's fixed
- The site loads normally on several pages.
- The page works from another device and network.
- Server resource usage is back under its limits in your control panel.
When to get help
If the server keeps hitting resource limits during normal traffic, ask your host about a larger plan or better caching. Visitors should contact the site if the error lasts more than a few hours.
Questions
How long does a 503 error last?
There is no fixed time. Traffic spikes can clear in minutes, while maintenance can take longer. Some sites send a Retry-After value, but browsers do not usually show it.
Is 503 the same as 500?
No. A 500 means something unexpected broke. A 503 means the server is temporarily unable to serve requests and should recover.
Why do I get 503 on only one website?
Because the problem is on that site's server, not your internet connection. Other sites will keep working.
Related fixes
Still stuck?
Paste the exact message and the repair bot will find the closest fix, or search it on Google, Microsoft, Apple, Reddit and YouTube.