Error map
SkuNotAvailable Azure: SkuNotAvailable / QuotaExceeded when creating a VM or resource
Azure · layer 6, Platform & cloud
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)
AWS: ThrottlingException / Rate exceeded
You exceeded the request rate for an AWS API; retry with exponential backoff.
HTTP 402 Payment Required
The service wants payment before it will process the request — an unpaid invoice, exhausted credits or a failed card.
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…
ARM/Bicep: DeploymentFailed / InvalidTemplateDeployment / InvalidTemplate
An Azure Resource Manager (ARM/Bicep/Terraform) deployment failed; the inner error under “details” has the real cause.
Azure: AuthorizationFailed — The client does not have authorization to perform action
The signed-in identity (user, service principal or managed identity) lacks an Azure RBAC role for that action on that scope.
FATAL: sorry, too many clients already / remaining connection slots are reserved for non-replication superuser connections
PostgreSQL reached max_connections.
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.
ERROR: could not extend file "base/…": No space left on device
The disk holding the PostgreSQL data directory (or WAL) is full.
HTTP 509 Bandwidth Limit Exceeded
A hosting-control-panel status (cPanel/Apache) meaning the account used up its monthly bandwidth allowance.
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.
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.
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).
Two steps away (35)
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.
HTTP 429 Too Many Requests
You’ve hit a rate limit — too many requests in a given time window. Slow down and retry later.
AWS Lambda: Task timed out after X seconds
The function ran longer than its configured timeout (default 3 seconds) and Lambda stopped it.
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…
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.
HTTP 500 Internal Server Error
The server hit an unexpected condition — usually an unhandled exception or misconfiguration in the application.
HTTP 503 Service Unavailable
The server is temporarily unable to handle the request — overloaded, in maintenance, or has no healthy backends.
MySQL ERROR 1040 (08004): Too many connections
MySQL reached `max_connections` and refuses new clients.
Stack is in ROLLBACK_COMPLETE state and can not be updated
The stack’s first creation failed and rolled back; a stack in ROLLBACK_COMPLETE can only be deleted, not updated.
CloudFormation stack in UPDATE_ROLLBACK_FAILED
An update failed, and then the rollback also failed, leaving the stack stuck until you continue the rollback.
Elastic Beanstalk: Environment health has transitioned from Ok to Severe
Most instances in the Elastic Beanstalk environment are failing health checks or returning errors.
Azure Storage: AuthorizationPermissionMismatch (403) — This request is not authorized to perform this operation using this permission
You’re accessing blob/queue data with Microsoft Entra ID, but the identity has only management roles (Owner/Contributor) — not a…
PERMISSION_DENIED: The caller does not have permission (insufficient permissions)
You are authenticated, but your identity isn’t allowed to perform this action on this resource.
AccessDeniedException: User: arn:aws:iam::... is not authorized to perform: service:Action on resource: ...
The IAM user or role making the call has no permission for that action on that resource — the message names both.
PostgreSQL: could not connect to server / connection refused — Is the server running on host and accepting TCP/IP connections?
The client reached no PostgreSQL listener at that host/port — the server is down, listening elsewhere, or not accepting remote co…
FATAL: database "x" does not exist
The connection names a database that isn’t on that server.
server closed the connection unexpectedly — This probably means the server terminated abnormally before or while processing the request.
The connection to PostgreSQL dropped — the server restarted/crashed, a proxy/firewall killed an idle connection, or the backend w…
no space left on device (Docker / Linux)
The disk (or inode table) is full — Docker images, build cache, logs and volumes are common culprits.
MySQL ERROR 126 (HY000): Incorrect key file for table; try to repair it
MySQL can’t use a table’s index file — usually a full tmp disk during a query, or MyISAM corruption.
StorageAccountAlreadyTaken: The storage account named x is already taken
Storage account names are globally unique across Azure; another customer (or you elsewhere) already uses the name.
FATAL: too many connections for role "x"
The role reached its per-role CONNECTION LIMIT (often set by hosting providers or free tiers).
Azure Storage: Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature (AuthenticationFailed)
The storage request’s signature or SAS token is invalid — wrong/rotated account key, expired SAS, or clock skew.
Azure Storage: ContainerNotFound / BlobNotFound — The specified container (or blob) does not exist
The container or blob path doesn’t exist in that storage account.
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.
Azure VM: AllocationFailed / ZonalAllocationFailed — Allocation failed. We do not have sufficient capacity for the requested VM size
Azure has no capacity for that VM size in the region/zone (or in the cluster the VM is pinned to) right now.
An error occurred (UnauthorizedOperation): You are not authorized to perform this operation. Encoded authorization failure message: ...
The IAM identity is missing an EC2 (or related) permission. The encoded message tells you exactly which action and resource were…
InvalidKeyPair.NotFound: The key pair 'x' does not exist
The key pair name you passed doesn’t exist in that region (key pairs are regional).
InvalidAMIID.NotFound: The image id '[ami-xxxx]' does not exist
The AMI ID isn’t available in this region/account — AMI IDs are regional and private AMIs must be shared.
EC2 status check failed: Instance reachability check failed (1/2 checks passed)
AWS can reach the host, but the operating system inside the instance isn’t responding — kernel panic, full disk, broken network c…
pods is forbidden: failed quota: must specify limits.cpu,limits.memory,requests.cpu,requests.memory
A ResourceQuota on the namespace covers CPU/memory, so every pod must declare those requests/limits — and this one doesn’t.
Disk quota exceeded (EDQUOT)
Your user or group has used its storage quota on this filesystem, even if the disk itself has space.
Kubernetes: Pod stuck in Pending — FailedScheduling: 0/3 nodes are available
The scheduler can’t find a node that satisfies the pod’s resource requests, selectors, taints or volume constraints.
Kubernetes: Pod Evicted — The node was low on resource: memory / ephemeral-storage
The kubelet removed the pod because its node ran short of memory or disk.
ResourceNotFound: The Resource 'Microsoft.X/...' under resource group 'y' was not found
The specific resource doesn’t exist in that resource group/subscription — wrong name, group or subscription, or it was deleted.
Map another error
Popular: 4035004000xC000007BTypeErrorCritical error404NullPointerException