Source-linked reports: Amounts and outcomes come from the original reports and linked replies.
Thunderbit: a browser-extension client loop drove about $38,772.92 in Workers charges.
Community user shuai of Thunderbit, a Chrome extension with about 200,000 users, says a bug in one extension build made every client repeatedly call their Worker, producing an anomalous charge of about $38,772.92 for the May 18 to June 17, 2026 cycle, with a second cycle accruing the same way. The bug was fixed and usage returned to baseline; they say a billing case with a full usage audit requested a refund and had no response.
What happened
- Reported cause
- Unbounded loop
- Incident date
- Date not recorded
- First reported
- 2026-06-29
- Billing outcome
- Request submittedAuthor-reported
- Case progress
- Not established
- Public Cloudflare reply
- Not linked
Latest reported outcome
The author says a billing case with a full usage audit requests a refund and had no response.
View this update in the timelineOriginal sources
Each entry links to the report or reply it describes.
Case timeline
Author asks for a refund
Open original sourceThe author reports about $38,772.92 from an extension client loop and says the billing case requesting a refund had no response.
More to read
How I keep Cloudflare under $5: where surprise bills come from
Ashish Sharma (@sarmaasis) runs several sites on the $5 Workers Paid plan and lists, product by product, the usage patterns he says quietly run up a Cloudflare bill, ending with a 12-item checklist.
A voting page polling every three seconds: the author revises a $1,000 report.
@keking99 first reports about $1,000 for a voting page polling /api/result every three seconds. A later post reports $816.52 in accumulated usage as of October 4 and cites another screenshot total of $817.14. He later says his support ticket keeps being refused.
A budget alert is a horn, not a brake
@GUYUE_LGY points to Cloudflare’s Budget alerts documentation: alerts send email when spend crosses a threshold but do not pause or cap usage. Before letting AI run unattended, the author checks what actually happens at the line.