How to Fix the “503 Service Unavailable” Error

A "503 Service Unavailable" error means the server is temporarily unable to handle the request — it is up, but too busy, overloaded, or deliberately in maintenance mode. Unlike a 500, a 503 is usually about capacity or state, not broken code.

Is it maintenance mode?

The friendliest cause: WordPress shows a 503 while updating. If it gets stuck there, a leftover .maintenance file is to blame. Delete that file from your site's root using File Manager (you may need to show hidden files) and the site returns.

Is it overload?

If a burst of traffic or a heavy process overwhelmed the account, the server sheds requests with a 503. Check your resource usage to confirm, and reduce load:

Enable caching so pages are served without rebuilding each time — see LiteSpeed Cache.
Deactivate a heavy plugin that spikes usage.
Block aggressive bots hammering the site — see blocking bad bots.

Is it a plugin or theme?

A badly behaved plugin can trigger a 503 too. Rename the plugins folder via File Manager to disable them all at once; if the site recovers, re-enable them one by one to find the culprit.

Step-by-step

Check for and delete a stuck .maintenance file.
Look at resource usage for an overload.
Add caching and trim heavy plugins.
Read the error log for specifics.

Frequently asked questions

My site got a 503 during a WordPress update and never came back.

That is the classic stuck-maintenance case. Delete the hidden .maintenance file in your site root and reload. If needed, also update WordPress manually afterwards.

The 503 only appears at busy times.

That points squarely at overload. Caching is the highest-impact fix; if a well-optimised site still tips over at peak, you have likely outgrown your plan — see upgrading.

Could a 503 mean my site is attacked?

A sudden flood of bot or attack traffic can overwhelm resources and cause 503s. Check your visitor logs; if it looks like an attack, block the sources and consider a CDN for protection.