503
503.my.id
THE 503 ERROR DIAGNOSTIC CENTER
GET /
↓
200 OK

A normal minute

A request comes in. The site answers.

Browser asks, server serves, database replies — the whole trip takes a blink when every worker is free.

GET / HTTP/1.1 HTTP/1.1 200 OK
PHP-FPM WORKERS
Worker 1BUSY
Worker 2BUSY
Worker 3BUSY

The queue builds

Visitors arrive faster than workers free up.

Each request holds one PHP-FPM worker until it finishes. When all three are busy, the next requests wait in line.

php-fpm error log: server reached pm.max_children setting (3), consider raising it
FULL
Retry-After: 600

503 — Service Unavailable

Full — so the server refuses, politely.

Rather than hang forever, the server answers at once: busy, with a named time to try again.

HTTP/1.1 503 Service Temporarily Unavailable Retry-After: 600

Two visitors, two fates

People bounce. Googlebot takes the hint.

VISITORSees the 503 page, closes the tab, maybe returns later.tab closed
GOOGLEBOTReads Retry-After, schedules a revisit, keeps the page indexed.back in 10 min

Same answer — read two different ways.

The recovery

The backlog drains, workers free up — the next request sails through.

A 503 is a server asking for time. Read its headers, find your cause, fix that one first.

503 Service Unavailable: Causes and How to Fix It by 503.my.id.