The server is up but will not take the request right now: it is overloaded, has run out of PHP workers, is limiting how many requests it takes, or is in maintenance. It is meant to be temporary — the fix is to find what is using up the capacity, or to finish the maintenance.
Service Unavailable The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
How 5 other clients word the same error
nginx
503 Service Temporarily Unavailable nginx
OpenLiteSpeed
Service Unavailable The server is temporarily busy, try again later!
IIS
Service Unavailable HTTP Error 503. The service is unavailable.
WordPress, during an update
Briefly unavailable for scheduled maintenance. Check back in a minute.
curl -I
HTTP/2 503
| Error | 503 Service Unavailable |
| Usually fixed by | The site owner or host |
| Status | 503 (RFC 9110 §15.6.4) |
| Meant to be | Temporary — overload or planned maintenance |
| Retry-After | The server can say when to come back; WordPress sends 600 seconds |
Check the site from outside
Enter the address: we load it from our network and show the status code, how long it took, and the error if it failed.
What it means
A 503 says the server cannot handle the request now but expects to soon. It can come with a Retry-After header saying when to try again. Search engines treat it as temporary: Google slows its crawling and keeps the pages, unless the 503s go on for days.
WordPress sends a 503 while it installs updates: it writes a .maintenance file and removes it when done. If an update is interrupted the file stays behind — though WordPress ignores one older than ten minutes.
Why it happens
- Every PHP worker is busy — a traffic spike, bots, or slow pages holding workers — so new requests wait and then fail.
- The hosting account’s process or memory limit (CloudLinux, LiteSpeed LSAPI_CHILDREN).
- A rate limit: nginx’s limit_req answers 503 unless set to 429.
- Maintenance: WordPress updating, or a planned outage.
- On IIS, the application pool is stopped, or stopped itself after repeated crashes.
What the error log says
PHP-FPM, every worker busy
[pool www] server reached pm.max_children setting (5), consider raising it
Apache, every worker busy
AH00484: server reached MaxRequestWorkers setting, consider raising the MaxRequestWorkers setting
Apache, PHP-FPM not answering
AH01079: failed to make connection to backend: localhost
LiteSpeed, the account’s process limit
Reached max children process limit: 10, extra: 3, current: 13, busy: 13, please increase LSAPI_CHILDREN.
nginx, rate limiting (503 is limit_req’s default)
limiting requests, excess: 10.500 by zone "one", client: 192.0.2.7
How to fix it
- Read the error log for the lines below: they say whether it is workers, limits or rate limiting.
- Serve cached pages to anonymous visitors, block abusive bots, and fix the slow pages that tie workers up — then raise pm.max_children if memory allows.
- On shared hosting, compare the account’s resource usage (cPanel → Resource Usage) with its limits.
- For WordPress stuck in maintenance, delete the .maintenance file in the site’s root folder.
- For planned work, send 503 with a Retry-After header — for hours, not days.
If you are visiting the site
- Try again in a few minutes — a 503 is the server saying it is busy or being worked on.
See it for yourself
curl -sI https://example.com/ | grep -iE '^HTTP|retry-after'
Shows the status and whether the server says when to come back.
Questions
Will a 503 hurt my search ranking?
Not for a few hours: Google treats 503 as temporary and keeps the pages indexed. If the site keeps answering 503 for several days, Google may start dropping those pages.
Sources
Error text and meaning checked on 25 September 2026 against these official sources:
- RFC 9110: HTTP Semantics — rfc-editor.org
- php-src/sapi/fpm/fpm/fpm_process_ctl.c at master — github.com
- 503 Error — cPanel — docs.litespeedtech.com
- wordpress-develop/src/wp-includes/load.php at trunk — github.com
- Temporarily Pause Or Disable Website — developers.google.com
- Module ngx_http_limit_req_module — nginx.org