EdgeWorkers imposes various limits on the number of activations, EdgeWorker IDs, and versions you can deploy. In some cases, you may have the option to override these limits. Contact your Akamai representative for more information.
You can also run the List limits operation to see the limits EdgeWorkers imposes on the number of activations, EdgeWorkers IDs, and versions you can deploy. If you exceed these limits, you will receive a 429 error response.
Various responses include HTTP headers that provide details on your current limits:
-
Custom headers suffixed
*-Limitreport on the overall limit. -
Corresponding headers suffixed
*-Remainingtell you how many items you have left to deploy. -
For rate-limited activations, an additional
*-Resetheader lets you know when the current*-Remainingvalue rises to the original*-Limitvalue.
EdgeWorkers imposes these limits:
| Limit | Default value | Description |
|---|---|---|
X-Limit-Ew-Id-Per-Account-Limit | 200 | Maximum number of EdgeWorker IDs per account. |
X-Limit-Version-Per-Ew-Id-Limit | 1000 | Maximum number of versions per EdgeWorker ID. |
X-RateLimit-Version-Per-Minute-Limit | 20 | Maximum number of EdgeWorker versions each minute per account |
X-RateLimit-Activation-Per-Network-Per-Minute-Limit | 20 | Maximum number of activations each minute on a network per account. |
X-RateLimit-Activation-Per-Day-Limit | 500 | Maximum number of activations each day per account. |
X-RateLimit-Logging-Override-Per-Network-Per-Minute-Limit | 20 | Maximum number of logging overrides each minute on a network per account. |
X-RateLimit-Logging-Override-Per-Day-Limit | 500 | Maximum number of logging overrides each day per account. |