Error map
429 HTTP 429 Too Many Requests
HTTP · layer 2, Network
Centre: this error. First ring: errors it is linked with (12). 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.
Directly related (12)
HTTP 403 Forbidden
The server understood the request but refuses to authorize it — you (or the server process) are not allowed to access this resour…
Cloudflare Error 1015: You are being rate limited
The site’s Cloudflare rate-limiting rule blocked you for sending too many requests in a short time.
HTTP 503 Service Unavailable
The server is temporarily unable to handle the request — overloaded, in maintenance, or has no healthy backends.
Firebase Auth: auth/too-many-requests — Access to this account has been temporarily disabled due to many failed login attempts
Firebase throttled sign-in or SMS verification because of too many attempts from the device/IP or for the account.
AWS: ThrottlingException / Rate exceeded
You exceeded the request rate for an AWS API; retry with exponential backoff.
Cloudflare Error 1020: Access Denied
A Cloudflare firewall/WAF custom rule blocked the request — the visitor’s IP, country, user agent or request pattern matched a bl…
HTTP 402 Payment Required
The service wants payment before it will process the request — an unpaid invoice, exhausted credits or a failed card.
Cosmos DB 429: Request rate is large (TooManyRequests, RU/s exceeded)
The container or database used more Request Units per second than provisioned, so Cosmos DB throttled requests.
HTTP 508 Loop Detected (Resource Limit Is Reached)
Either the server detected an infinite loop (WebDAV) or — much more often — a cPanel/CloudLinux host is saying your account hit i…
HTTP 509 Bandwidth Limit Exceeded
A hosting-control-panel status (cPanel/Apache) meaning the account used up its monthly bandwidth allowance.
API Error: Too many concurrent requests (concurrency limit reached)
You have more requests in flight at once than the API allows for your key — even if your requests-per-minute rate is fine.
ProvisionedThroughputExceededException: The level of configured provisioned throughput for the table was exceeded
Requests exceed the table’s (or index’s) provisioned read/write capacity, or one partition is hot.
Two steps away (33)
Git: Permission denied (publickey). fatal: Could not read from remote repository.
SSH authentication to GitHub/GitLab/Bitbucket failed — no key, wrong key, or the key isn’t added to your account.
AWS S3: AccessDenied (403) when calling GetObject / PutObject
An IAM policy, bucket policy, ACL/ownership setting, Block Public Access or KMS key policy denied the S3 request.
Linux: Permission denied
Your user (or the service user) lacks read/write/execute permission on a file, directory or one of its parents.
S3 SlowDown: Please reduce your request rate (503)
S3 is throttling requests to a prefix because the request rate is above what it can currently serve.
Cloudflare Error 1005: Access denied — The owner of this website has banned the autonomous system number (ASN) your IP address is in
The site owner blocked your network provider (ASN) — common for VPNs, cloud/data-center IPs and some mobile carriers.
Cloudflare Error 1006 / 1007 / 1008: Access denied — Your IP address has been banned
The site owner (or a Cloudflare security setting) blocked your IP address.
Kubernetes: CrashLoopBackOff
The container starts, crashes (or exits), and Kubernetes keeps restarting it with increasing back-off delays.
HTTP 500 Internal Server Error
The server hit an unexpected condition — usually an unhandled exception or misconfiguration in the application.
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.
toomanyrequests: You have reached your pull rate limit (Docker Hub)
Docker Hub limits anonymous and free pulls; your IP or account has used its quota for the current window.
Google Sign-In: com.google.android.gms.common.api.ApiException: 10 (DEVELOPER_ERROR)
Google Sign-In is misconfigured — the app’s package name or SHA-1/SHA-256 signing fingerprint isn’t registered in Google Cloud/Fi…
IllegalStateException: Default FirebaseApp is not initialized in this process
Firebase couldn’t initialise because google-services.json or the Google Services Gradle plugin is missing/misapplied, or initiali…
Azure: SkuNotAvailable / QuotaExceeded when creating a VM or resource
The VM size isn’t offered in that region/zone for your subscription, or you’ve hit the vCPU quota.
AWS Lambda: Task timed out after X seconds
The function ran longer than its configured timeout (default 3 seconds) and Lambda stopped it.
VcpuLimitExceeded: You have requested more vCPU capacity than your current vCPU limit
Your account’s On-Demand (or Spot) vCPU quota for that instance family and region is used up.
Cloudflare Error 520: Web Server Returned an Unknown Error
Cloudflare connected to your origin, but the origin returned an empty, unknown or invalid response.
driver failed programming external connectivity on endpoint: iptables: No chain/target/match by that name
Docker’s iptables rules were wiped (firewalld/ufw reload, iptables flush) while Docker was running, so it can’t publish ports.
HTTP 451 Unavailable For Legal Reasons
The content is blocked for legal reasons — a court order, government censorship, sanctions, or GDPR geo-blocking.
HTTP 507 Insufficient Storage
The server can’t store what’s needed to complete the request — the disk, quota or mailbox is full.
API Error: Feature not enabled for this account (feature_not_enabled / not available on your plan)
The endpoint or option exists, but your account, plan, region or project hasn’t been granted access to it.
Error creating: pods is forbidden: exceeded quota: compute-resources, requested: limits.memory=1Gi, used: ..., limited: ...
The namespace’s ResourceQuota doesn’t have room for the new pod’s requests/limits (or object count).
MySQL ERROR 1040 (08004): Too many connections
MySQL reached `max_connections` and refuses new clients.
MySQL ERROR 1114 (HY000): The table 'x' is full
MySQL couldn’t extend the table — disk full, a size limit, or a MEMORY table hitting max_heap_table_size.
FATAL: sorry, too many clients already / remaining connection slots are reserved for non-replication superuser connections
PostgreSQL reached max_connections.
ERROR: could not extend file "base/…": No space left on device
The disk holding the PostgreSQL data directory (or WAL) is full.
FATAL: too many connections for role "x"
The role reached its per-role CONNECTION LIMIT (often set by hosting providers or free tiers).
InsufficientInstanceCapacity: We currently do not have sufficient capacity in the Availability Zone you requested
AWS has no free capacity for that instance type in that Availability Zone right now.
HTTP 409 Conflict
The request conflicts with the current state of the resource — e.g. a duplicate or an edit based on an outdated version.
java.util.ConcurrentModificationException
A collection was modified while being iterated (even in a single thread).
HTTP 412 Precondition Failed
A conditional request header (If-Match, If-Unmodified-Since) didn’t match the current state of the resource.
ConditionalCheckFailedException: The conditional request failed
A write’s ConditionExpression evaluated to false, so DynamoDB didn’t perform it — often exactly as designed.
DynamoDB ValidationException: One or more parameter values were invalid: Missing the key pk in the item / The provided key element does not match the schema
The item or key doesn’t match the table’s primary key schema — wrong attribute name, wrong type, or missing sort key.
DynamoDB ResourceNotFoundException: Requested resource not found (table)
The table (or index) doesn’t exist in the region/account the client is using.
Map another error
Popular: 500403400ORA-009331064Critical errorFileNotFoundException assemblyTypeError