Quick answer
Netlify documents edge resource ceilings as 512 MB memory; 50 ms CPU; 20 MB compressed code. Response headers must be produced within the documented 40-second window.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| edge resource ceilingsResponse headers must be produced within the documented 40-second window. | 512 MB memory; 50 ms CPU; 20 MB compressed code | Edge Functions | NetlifyAug 22, 2026 |
Why does this limit matter?
I/O waiting and active CPU have different performance implications at the edge.
This value is scoped to Edge Functions; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Profile active CPU, compressed bundle size, memory, and time to response headers separately.
- Confirm the exact plan, model, runtime, endpoint, region, and account that serve the failing workload.
- Record the observed value, response headers or configuration, timestamp, and source without logging secrets.
Important caveats
- The CPU value should not be compared directly with synchronous serverless wall time.
- Treat the official source and live account configuration as authoritative if they differ from this verified snapshot.
HyperObserve reports the documented platform constraint. Your application, SDK, gateway, provider, region, or account can impose a lower effective limit.
Related