Verified history
This means HyperObserve has not found sufficient first-party evidence for a dated before-and-after event. It does not mean Cloudflare Workers 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 Cloudflare Workers. The baseline covers maximum request body, CPU time per HTTP request, Configurable CPU time per HTTP request, Memory per isolate, Worker requests. 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 |
|---|---|---|---|
| maximum request bodyWorkers plan CPU and Cloudflare account request-body limits are separate products scopes. | Plan dependent | Cloudflare account plan | CloudflareAug 22, 2026 |
| CPU time per HTTP requestCPU time excludes waiting on network requests and other I/O. | 10 ms | Workers Free | CloudflareAug 22, 2026 |
| Configurable CPU time per HTTP requestThe maximum is configurable with limits.cpu_ms; wall-clock duration is a separate concept. | 30 seconds default; up to 5 minutes | Workers Paid | CloudflareAug 22, 2026 |
| Memory per isolateIncludes the JavaScript heap and WebAssembly allocations; one isolate can serve concurrent requests. | 128 MB | Free and Paid | CloudflareAug 22, 2026 |
| Worker requestsAccount plan limit shown in Cloudflare's Workers limits table. | 100,000 per day | Workers Free | CloudflareAug 22, 2026 |
Tracked constraints and impact
CPU, memory, request, bundle, duration, and account plan 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.
Cloudflare Request Body Limits
Cloudflare Request Body Limits, verified against Cloudflare Workers's official documentation with scope, implementation impact, caveats, and a direct check.
Cloudflare Workers CPU time
Current Workers Free and Paid CPU-time limits, wall-time distinction, configuration, and exceeded-resource behavior.
Cloudflare Workers memory
The current Cloudflare Workers isolate memory limit, what it includes, concurrency caveats, and practical diagnostics.
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 Cloudflare Workers baseline. HyperObserve links directly to them so you can confirm the live wording before making a production decision.
Account, CPU, memory, and duration limits