Verified history
This means HyperObserve has not found sufficient first-party evidence for a dated before-and-after event. It does not mean Netlify has never changed. Undated values are kept in the current baseline below instead of being presented as history.
Current monitored baseline
HyperObserve currently monitors 5 scoped observations for Netlify. The baseline covers synchronous function duration, background function duration, buffered and streamed payload, default function memory, edge resource ceilings. Each value retains its plan, product, endpoint, region, account, or runtime qualifier so a future change can be compared against the correct scope.
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| synchronous function durationScheduled functions use a separate shorter maximum. | 60 seconds | Synchronous Functions | NetlifyAug 22, 2026 |
| background function durationBackground functions also have a much smaller request payload allowance. | 15 minutes | Background Functions | NetlifyAug 22, 2026 |
| buffered and streamed payloadBinary payloads can reach the buffered limit at roughly 4.5 MB before base64 expansion. | 6 MB buffered; 20 MB streamed; 256 KB background | Function-type specific | NetlifyAug 22, 2026 |
| default function memoryMemory configuration is separate from function duration and payload size. | 1,024 MB | Functions | NetlifyAug 22, 2026 |
| 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 |
Tracked constraints and impact
Synchronous, scheduled, background, and edge function resource limits. A change is recorded only when it alters a constraint developers can act on, such as capacity planning, request shaping, model selection, deployment configuration, storage design, retry behavior, or account budgeting.
Netlify Synchronous Function Timeout
Netlify Synchronous Function Timeout, verified against Netlify's official documentation with scope, implementation impact, caveats, and a direct check.
Netlify Background Function Timeout
Netlify Background Function Timeout, verified against Netlify's official documentation with scope, implementation impact, caveats, and a direct check.
Netlify Function Payload Limits
Netlify Function Payload Limits, verified against Netlify's official documentation with scope, implementation impact, caveats, and a direct check.
Netlify Function Memory Limit
Netlify Function Memory Limit, verified against Netlify's official documentation with scope, implementation impact, caveats, and a direct check.
Netlify Edge Function Limits
Netlify Edge Function Limits, verified against Netlify's official documentation with scope, implementation impact, caveats, and a direct check.
How a change is verified
- Compare the current first-party statement with the previously stored observation, including the exact plan, model, runtime, endpoint, region, and account scope.
- Separate a true product change from documentation clarification, temporary capacity, configurable account state, or a limit that applies to a different execution path.
- Preserve the old and new values, official source, effective date when disclosed, detection date, and practical impact. If those elements cannot be supported, no historical event is published.
Official sources monitored
These first-party documents support the current Netlify baseline. HyperObserve links directly to them so you can confirm the live wording before making a production decision.
Synchronous, scheduled, background, memory, and payload limits
Code size, memory, CPU, and response-header limits