Edgio
Edgio Console

Limits

Edgio sets limits on requests, responses, and access logs.

Units

Data storage units are defined below.
  • KB stands for kilobytes and means 1,024 bytes (2^10 bytes)
  • MB stands for megabytes and means 1,024 kilobytes (2^20 bytes)
  • GB stands for gigabytes and means 1,024 megabytes (2^30 bytes)

Request and Response Limits

Edgio requires that all requests and responses meet the following requirements:
TypeLimitDescription
Response time from origin server60 secondsThe maximum number of seconds that Edgio will wait for a response from an origin server (e.g., your web server). Exceeding this limit results in a 536 Project HTTP Response Timeout response.
Response body size2GBThe maximum size for the response body.
Cookie size32KBThe maximum size for request or response cookies.
Maximum number of nested requests3The term “nested” means that an Edgio site is the upstream of itself or of another Edgio site. Exceeding this limit results in a 538 Project Request Loop response.

Cloud Functions Limits

Limitations for Edgio Cloud Functions are listed below. If your project was deployed using @edgio/core version 7.13.3 or lower, then additional limitations are applicable.
TypeLimitDescription
Request body size6MBThe maximum size for the request body. Exceeding this limit results in a 413 Request Entity Too Large response.
Response body size6MBThe maximum size for the uncompressed response body. A cloud function is able to return either 6MB of raw string data or approximately 4.5MB of buffered/binary data due to base64 encoding overhead. However, Edgio compresses responses using brotli, gzip or deflate. This allows Edgio to provide a response to most modern clients whose total size exceeds this limit. Exceeding this limit results in a 532 Project Response Too Large response.
Request headers size8KBThe maximum overall size for all headers defined within a request. The overall limit is lower with increasing number of headers. Exceeding this limit results in either a 431 Request Header Fields Too Large or a 413 Request Entity Too Large response.
Response headers size80KBThe maximum overall size for all headers defined within a response. The size of each individual header is limited to 32KB. Exceeding this limit results in a 542 Project Header Overflow response.
Response headers countUnlimitedThe maximum number of developer-controlled headers in the response is not limited. However, the total size for these headers must comply with the Response headers size limit.
Path and query string size11KBThe maximum total size for the path including query string. Exceeding this limit results in a 414 URI Too Long response.
Timeout20 secondsThe number of seconds that Edgio will wait for project code to process the request before timing out. Exceeding this limit results in a 539 Project Timeout response.
Memory896MBFree tier only: The maximum memory allocated for your Cloud Functions project. Exceeding this limit results in a 540 Edgio Out of Resources response. Contact your account manager or our sales department at 1 (866) 200 - 5463 to upgrade your account.
Temporary storage512MBThe maximum available storage for the /tmp directory. The content stored in this directory does not persist between multiple requests.
Additional Edgio Cloud Functions limitations for projects deployed using @edgio/core version 7.13.3 or lower:
TypeLimitDescription
Request headers size64KbThe maximum overall size for all headers defined within the request. Exceeding this limit results in a 542 Project Header Overflow response.
Response headers size64KbThe maximum overall size for all headers defined within the response. Exceeding this limit results in a 542 Project Header Overflow response.
Response headers count70The maximum number of developer-controlled headers defined within the response. Exceeding this limit results in a 542 Project Header Overflow response.
Scheduling timeout60 secondsThe maximum number of seconds that Edgio will try to schedule the processing of a request before timing out. Exceeding this limit results in a 541 Edgio Out of Workers response.

Reserved Headers

The following headers are served for use by Edgio. You may not modify these request headers.
  • accept-ranges
  • age
  • connection
  • content-encoding
  • content-length
  • content-range
  • date
  • server
  • trailer
  • transfer-encoding
  • upgrade
  • vary
  • via
  • warning
  • All header names that start with x-edg and x-ec are reserved.

RTLD Log Data

RTLD limitations are described below.
ValueLimitDescription
Time3 daysIf our service is unable to deliver log data, then we will store it for up to 3 days and deliver it when communication resumes. If we cannot deliver log data within 3 days, then it will be permanently deleted.
SizeUnlimited