503
503.my.id
THE 503 ERROR DIAGNOSTIC CENTER
503
Service Temporarily Unavailable
whose 503 is it?

The symptom

One 503. Two possible senders.

Behind Cloudflare, the same error page can come from the edge or from your origin — the fix lives on different sides.

Server: cloudflare CF-Ray: a5b791b229ad895f-SIN present in BOTH cases — they prove nothing alone

The distinguisher

Watch the origin log and the edge timing — one of them always talks.

EDGE 503 — CLOUDFLARE SENT IT

Retry-After: 300 X-Edge-Marker: EDGE-503-LAB6 server-timing: cfOrigin;dur=0 origin log: (no entries — the request never arrived)

dur=0 · origin never contacted

ORIGIN 503 — YOUR SERVER SENT IT

Retry-After: 600 X-Origin-Marker: ORIGIN-503-LAB6 server-timing: cfOrigin;dur=515 origin log: 15:36:22 GET / -> 503 mode=origin503

dur=515 · origin answered

The decision

Whose 503 it is picks the fix.

EDGE SENT ITFix the Cloudflare side: the rule, the Worker, the rate limit.
ORIGIN SENT ITLeave Cloudflare alone — fix the overloaded server or app.

Fix the right side, and the same address answers 200 OK again.

The takeaway

Same number. Different sender, different fix.

Pause Cloudflare or read the origin log — one quick test tells you which side of the edge to repair.

Cloudflare 503 Error: Origin or Cloudflare? Fix It by 503.my.id.