Source-linked reports: Amounts and outcomes come from the original reports and linked replies.
brenden5: a Worker–Queue feedback loop ran about 27 days, with a $4,915 February invoice.
Community user brenden5 says a Worker bound to the same Queue as producer and consumer pushed messages back into that queue, creating a feedback loop that ran for about 27 days at roughly 14 million requests a day and generated billions of internal operations from only 139 external HTTP requests. The February invoice was $4,915 and already charged; the author estimates the March invoice at $16,000–$21,000 on what was a $5/month side-project account. The author killed the loop on March 2, deleted all Workers, KV namespaces, R2 buckets and Pages deployments, and opened ticket #01999404 in the Refunds area.
What happened
- Reported cause
- Unbounded loop
- Incident date
- Date not recorded
- First reported
- 2026-03-03
- Billing outcome
- Request submittedAuthor-reported
- Case progress
- Not established
- Public Cloudflare reply
- Not linked
Latest reported outcome
The author opened refund ticket #01999404; the March figure is the author's estimate, not a reported invoice. No outcome is reported in the thread.
View this update in the timelineOriginal sources
Each entry links to the report or reply it describes.
Case timeline
Author reports a $4,915 invoice from a Worker–Queue loop
Open original sourceThe author says a Queue feedback loop ran for about 27 days, the February invoice of $4,915 was already charged, March is estimated at $16,000–$21,000, and ticket #01999404 asks for a refund.
More to read
Cloudflare billing risk audit skill for coding agents
Kid (@singkid9527), who collects cases and guides for Billflare, open-sourced a skill that has a coding agent review a project's configuration and source in read-only mode for paths that can amplify Cloudflare costs.
mcwangcn reports $1,300 in D1 charges after a bot attack.
@mcwangcn says D1 writes previously cost over a thousand dollars and separately mentions Workers CPU charges without giving an amount. He later shares a Cloudflare bill and says $1,300 of its $3,600 came from D1 after a bot attack.
Lanshu: an AI-assisted Cloudflare billing risk checklist
Lanshu (@LufzzLiz) shares a six-step prompt for checking account ownership, usage, runaway consumption and budget alerts. Replies add alarm logging, email delivery checks and separate notifications.