503 HTTP Origin: Network OSI layer 7 · Application Last updated 14 Oct 2026

HTTP 503 Service Unavailable

The server is temporarily unable to handle the request — overloaded, in maintenance, or has no healthy backends.

Exact message you may see service unavailable503 Service UnavailableService Temporarily Unavailableno healthy upstreamserver reached pm.max_children

Meaning

503 signals a temporary condition. Servers may include Retry-After. It’s returned by maintenance modes (Laravel php artisan down, WordPress updates), by load balancers with no healthy targets, and by servers that have exhausted worker processes.

Common causes

  • Maintenance mode enabled (and not disabled after a deploy)
  • No healthy targets behind the load balancer
  • All worker processes busy (PHP-FPM pm.max_children, Apache MaxRequestWorkers)
  • Rate limiting returning 503 (Nginx limit_req default)
  • Dependency outage with a circuit breaker open
  • Kubernetes service with no ready pods

⚡ Quick fix

  1. Check whether maintenance mode is on (php artisan up, delete WordPress .maintenance file)
  2. Check load balancer target health
  3. Look for worker exhaustion in server logs and scale or raise limits
  4. Retry after the Retry-After interval

Detailed fix by platform

PHP

  1. PHP-FPM log "server reached pm.max_children setting": raise pm.max_children based on available RAM ÷ average process size.

WordPress

  1. Delete the .maintenance file in the site root if an update was interrupted.

Kubernetes

  1. kubectl get endpoints <svc> — empty endpoints means no ready pods; check readiness probes and pod status.

AWS

  1. ALB returns 503 when the target group has no registered/healthy targets — check health check path and security groups.

How to diagnose

  1. Maintenance — Is maintenance mode on?
  2. Capacity — Are workers/pods saturated?
  3. Health — Are backends passing health checks?
  4. Dependencies — Is a downstream service failing?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Network. Errors that are often confused with or caused by this one (click to open):

1114 — MySQL ERROR 1114 (HY000): The table 'x' is full (MySQL)11141200 — Cloudflare Error 1200: Cache connection limit (Cloudflare)1200420 — HTTP 420 Enhance Your Calm (HTTP)420429 — HTTP 429 Too Many Requests (HTTP)429500 — HTTP 500 Internal Server Error (HTTP)500502 — HTTP 502 Bad Gateway (HTTP)502503 — 503 Service Unavailable with Retry-After (maintenance) (HTTP)503504 — HTTP 504 Gateway Timeout (HTTP)504503

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.