Missing resources, wrong scope, lifecycle drift, and state mismatches.
Last reviewed: February 13, 2026|52 mapped errors|Page 4 of 4
Resource-state errors appear when identifiers, region or account scope, lifecycle state, or consistency timing do not match request assumptions.
Provider-specific error pages mapped to this category (52 total). Showing 46-52.
HTTP 308 Permanent Redirect means resource moved permanently and redirect must preserve request method and body.
HTTP 402 Payment Required is reserved for future use in the standard and is usually provider-specific in practice.
HTTP 404 Not Found means the origin server did not find a current representation for the target URI.
HTTP 407 Proxy Authentication Required means the client must authenticate with a proxy before the request can proceed.
HTTP 410 Gone means the target resource is no longer available at this URI and is expected to be permanently removed.
HTTP 423 Locked means the source or destination resource is locked and cannot be modified yet.
HTTP 426 Upgrade Required means the server refuses current protocol and requires the client to switch protocols.
Compare Guide
Use 403 for explicit access denial, or 404 to conceal resource existence when security policy requires reducing endpoint and object enumeration risk.
Compare Guide
Learn when to return 404 (missing or temporary absence) versus 410 (intentional permanent removal), including redirect and cache implications.
Playbook
Use this playbook to separate temporary missing-resource lookups from permanent removals, then fix scope, lifecycle, and identifier drift safely.
Temporary 404s often resolve after propagation or deployment completion, while permanent removals are typically explicit lifecycle events (for example 410 semantics).
Many control planes are eventually consistent. Read-after-write visibility can lag and briefly return not-found responses.
Confirm exact scope and identifier tuple: resource name, region, account/subscription/project, and parent container.