Error map

API-005 API Service Unavailable

API · layer 4, Application & API

Open the full error page →

Centre: this error. First ring: errors it is linked with (3). Outer ring: what those are linked with. Colours show the layer of a request each error belongs to. Click any dot to re-centre the map on it; hover to follow its connections. The centre dot opens the error page.

2 · Network 3 · Edge & web server 4 · Application & API 6 · Platform & cloud
API-005 — API Service Unavailable (API)API-005503 — HTTP 503 Service Unavailable (HTTP)503504 — HTTP 504 Gateway Timeout (HTTP)504502 — HTTP 502 Bad Gateway (HTTP)502CrashLoopBackOff — Kubernetes: CrashLoopBackOff (Kubernetes)CrashLoopBackOff429 — HTTP 429 Too Many Requests (HTTP)429500 — HTTP 500 Internal Server Error (HTTP)500408 — HTTP 408 Request Timeout (HTTP)408499 — HTTP 499 Client Closed Request (Nginx) (HTTP)499Maximum execution time — PHP Fatal error: Maximum execution time of 30 seconds exceeded (PHP)Maximum execution t…ECONNREFUSED — Error: connect ECONNREFUSED 127.0.0.1:5432 (Node.js)ECONNREFUSED407 — HTTP 407 Proxy Authentication Required (HTTP)407520 — Cloudflare Error 520: Web Server Returned an Unknown Error (Cloudflare)520

Directly related (3)

503HTTP

HTTP 503 Service Unavailable

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

504HTTP

HTTP 504 Gateway Timeout

A proxy or gateway waited too long for the upstream server to respond and gave up.

502HTTP

HTTP 502 Bad Gateway

A proxy or gateway (Nginx, load balancer, CDN) got an invalid response — or no response — from the upstream server behind it.

Two steps away (9)

CrashLoopBackOffKubernetes

Kubernetes: CrashLoopBackOff

The container starts, crashes (or exits), and Kubernetes keeps restarting it with increasing back-off delays.

429HTTP

HTTP 429 Too Many Requests

You’ve hit a rate limit — too many requests in a given time window. Slow down and retry later.

500HTTP

HTTP 500 Internal Server Error

The server hit an unexpected condition — usually an unhandled exception or misconfiguration in the application.

408HTTP

HTTP 408 Request Timeout

The server closed the connection because the client took too long to send the complete request.

499HTTP

HTTP 499 Client Closed Request (Nginx)

Nginx-specific code logged when the client disconnected before the server finished responding.

Maximum execution timePHP

PHP Fatal error: Maximum execution time of 30 seconds exceeded

The script ran longer than `max_execution_time` and PHP stopped it.

ECONNREFUSEDNode.js

Error: connect ECONNREFUSED 127.0.0.1:5432

Nothing is listening at that host:port — the target service is down or you’re connecting to the wrong address.

407HTTP

HTTP 407 Proxy Authentication Required

A proxy between you and the server requires credentials before it will forward your request.

520Cloudflare

Cloudflare Error 520: Web Server Returned an Unknown Error

Cloudflare connected to your origin, but the origin returned an empty, unknown or invalid response.

Map another error

Popular: 4035004000xC000007BTypeErrorCritical error404NullPointerException