Workers limits
Cloudflare lists account and invocation limits for Workers.
- Products
- Workers
- Source
- Official docsCloudflare Docs
Key points
- CPU time measures Worker execution, not time waiting for fetch, KV, or database responses.
- For HTTP requests, the documented CPU limit is 10 ms on Free and 30 seconds by default on Paid, with a configurable maximum of five minutes.
- Paid CPU limits can be set with Wrangler's limits.cpu_ms or in Dashboard > Workers & Pages > a Worker > Settings. These per-invocation limits do not cap account spend.
Original sources
Undated
Original post
Open original source
More to read
Author experienceWorkers +4
Cloudflare billing pitfalls thread
The author organizes Cloudflare billing risks by product and shares experience with budget alert emails.
D1
D1: an author reports a $3,500 bill in 48 hours and a full waiver.
@darylginn reports about $3,500 in D1 charges over 48 hours. He says an AI-assisted Postgres migration omitted indexes and caused about 970 billion row reads daily, and that Cloudflare waived the bill.
Workers AI
Jason Silberman: an approximately $1,000 AI-billing dispute, later reported resolved.
@_jasonsilberman reports an invoice around $1,000 with AI usage rows he says were duplicated and already prepaid. Cloudflare personnel reply, including Matthew Prince, who says the case was escalated. The author later says the issue was resolved.