A 503 error indicates the server is temporarily unable to handle the request — but the reason behind that varies significantly.
Planned: Maintenance Mode
Many CMS platforms deliberately return a 503 during updates, which is actually correct behavior — it tells search engines this is temporary and not to drop the page from their index.
Unplanned: Server Overload
If you didn't trigger a maintenance mode, a 503 usually means the server has hit a resource limit or is overwhelmed by traffic it can't currently handle.
Diagnosing the Cause
Check whether an update or plugin is actively running, review resource usage in Plesk, and check if traffic has spiked unusually around the time the error started.
Español
Deutsch