540 Temporarily Disabled
The 540 status code has platform-specific meanings: Shopify returns 540 Temporarily Disabled for offline endpoints, Akamai EAA returns 540 Connectivity Disrupted for connector failures, and Edgio returned 540 Out of Memory for memory exhaustion.
Usage
Shopify returns 540 when a specific API endpoint has been taken offline temporarily. The endpoint is expected to come back without manual intervention. This differs from 503 Service Unavailable, where the entire service is down. A 540 response targets a single endpoint while the rest of the API remains operational.
Shopify documents the code only as a temporary disablement with the endpoint expected back online shortly. Likely reasons include maintenance on a subsystem or a targeted mitigation isolating a specific resource.
The response is transient. Retrying the same request after a short delay typically succeeds once the endpoint is re-enabled. No action is required from the API consumer beyond waiting and retrying.
Akamai Enterprise Application Access
Akamai EAA returns 540 Connectivity Disrupted when the EAA connector lacks dial-out connections to the data POP serving the application or has lost access to the configured directory. The connector sits between the Akamai cloud and the origin application. Without active dial-out connections, requests have no path to the backend. Verifying connector health, restarting the connector, and increasing dial-out capacity for the affected application resolves the issue.
Edgio
Edgio (formerly Layer0) returned
540 Out of Memory when serverless code running
on the platform triggered an out-of-memory
condition. Edgio allocated a fixed memory budget
per serverless worker, and requests exceeding the
budget received a 540 response. The wm field
in the x-0-t response header reported worker
memory usage in megabytes, providing a way to
monitor consumption before the worker reached the
limit.
Edgio shutdown
Edgio filed for bankruptcy in September 2024 and its application platform was shut down in early 2025. The Edgio 540 variant no longer appears in active infrastructure and is documented here for historical reference.
SEO impact
Search engines treat 540 responses as server errors. Persistent errors cause crawlers to reduce crawl frequency and eventually drop affected URLs from the index.
Example
A client requests product data from the Shopify Admin API, but the specific endpoint has been temporarily disabled during a platform deployment.
Request
GET /admin/api/products.json HTTP/1.1
Host: store.example.re
X-Shopify-Access-Token: shpat_xxxxxxxxxxxx
Response
HTTP/1.1 540 Temporarily Disabled
Content-Type: application/json
Retry-After: 30
{"errors":"This endpoint is temporarily disabled"}
How to fix
Wait and retry the request. The endpoint is expected to come back on its own. Start with a 30-second delay and use exponential backoff if the error persists. Check the Retry-After header when present for a server-suggested wait time.
Verify the Shopify status page for ongoing platform incidents affecting the specific API surface.
Confirm the application handles 540 as a retryable error distinct from permanent failures like 404 or 410. Retry logic designed for 503 applies equally to 540.
If a specific endpoint returns 540 for an extended period, check the Shopify changelog and developer forums for announcements about endpoint deprecation or migration.
