893 Load Balancing Overflow

The HTTP 893 Load Balancing Overflow status code is an unofficial status code used internally by Edgio (formed from the merger of Limelight Networks and Verizon's Edgecast CDN in 2022) when load balancing high-volume traffic for a specific asset within a POP (point of presence).

Table of Contents

Usage

Edgio's delivery network uses reserved status codes for internal communication between infrastructure components. The 893 code appears when a POP's load balancer determines traffic for a single asset has exceeded the capacity of the local serving tier.

This code is an internal signal, not a client-facing response. End users and API consumers do not receive 893 in normal operation. The edge infrastructure intercepts the signal and either retries the request on another server within the POP, Redirects the request to a neighboring POP, or returns a standard HTTP error to the client if no alternative path is available.

The 893 code is rare. Triggering the condition requires sustained, concentrated traffic to a single asset at a volume overwhelming the local serving capacity within one POP. Typical CDN traffic patterns, distributed across many assets and geographies, do not produce this condition.

Edgio shutdown

Edgio filed for bankruptcy in September 2024. Its CDN assets were sold. This vendor-specific status code is unlikely to appear in any active infrastructure.

Note

The 893 status code is an internal infrastructure signal. Clients and crawlers never receive this code directly. No SEO impact applies because the code does not reach external HTTP responses.

Example

An internal trace from within the Edgio POP shows the load balancer returning 893 for a high-traffic asset. The edge server intercepts the response and handles the overflow internally.

Internal trace (not visible to clients)

GET /assets/video/popular.mp4 HTTP/1.1
Host: edge-internal.example.re
X-EC-Debug: _all

HTTP/1.1 893 Load Balancing Overflow
X-EC-Debug-Info: pop=LAX,overflow=true

The client receives a standard response after the edge layer reroutes the request:

Client-facing response

HTTP/1.1 200 OK
Content-Type: video/mp4
Content-Length: 52428800
X-Cache: HIT

How to fix

No direct action is available because the 893 code operates within Edgio's internal infrastructure. CDN customers do not control load balancer behavior at this level.

If analytics or log exports surface 893 entries, they indicate a specific asset is receiving disproportionately high traffic at a single POP. Strategies to reduce concentration include:

  • Enable multi-POP origin shielding to distribute origin fetches across multiple POPs instead of concentrating on one.
  • Pre-warm popular assets in cache across geographic regions before anticipated traffic spikes (product launches, live events).
  • Use a multi-CDN strategy to split traffic across providers, reducing the peak load at any single Edgio POP.

For persistent 893 entries affecting delivery quality, contact Edgio support for POP-level capacity adjustments.

Takeaway

The 893 Load Balancing Overflow status code is an internal signal within Edgio's CDN infrastructure, triggered when a single asset overwhelms the local serving capacity at a POP. Clients never receive this code directly. The edge layer handles the overflow by rerouting traffic internally.

See also

Last updated: March 6, 2026