service_unavailable
service_unavailable
Section titled “service_unavailable”HTTP status: 503 Service Unavailable
How to fix
Section titled “How to fix”- Retry with exponential backoff. Start at 1 second, double on each retry, cap at 60 seconds.
- Check for a
Retry-Afterresponse header. If present, wait at least that many seconds before retrying — we're telling you when the cooldown ends. - Check our status page for ongoing incidents (deploys, infrastructure events, planned maintenance).
- For sustained 503s beyond ~5 minutes, file a support ticket — that's outside a normal deploy window.
What this means
Section titled “What this means”Our infrastructure is temporarily unable to serve the request — usually because a deploy is in progress, a service is scaling up, or a brief upstream dependency outage is in flight. This is distinct from internal_error (our bug) — 503 means our code is healthy but the platform around it isn't ready.
Related errors
Section titled “Related errors”internal_error— our bug, not infrastructureprovider_unavailable— upstream scraping vendor failedquota_exceeded— rate gate (429), not infrastructure
Still stuck?
Section titled “Still stuck?”Contact support with your request_id (looks like req_01HF3JKB...). We'll confirm which service was unhealthy at the time.