Source-linked reports: Amounts and outcomes come from the original reports and linked replies.
zmuleyu (yourchars.com): a $1,481.11 invoice from 1.476 trillion D1 rows read, with a $976.11 account credit.
Community user zmuleyu (yourchars.com) says an unintended query pattern repeatedly ran high-volume D1 scans during the July 17–August 16 billing period, reading about 1.476 trillion rows and producing a US$1,481.11 invoice (US$1,476.11 for D1 plus US$5 for Workers Paid). The author restricted public access, fixed the query path and added controls and alerts. Cloudflare granted a US$976.11 account credit on August 19, leaving US$500 of the D1 charge uncredited. The author asks how the credit was calculated, why US$500 was left, and how the balance can be used; support said the amount came from a case-specific review by a Finance team, the balance applies automatically to future eligible invoices, and closed the case again. The author notes budget alerts on Workers Paid are informational, not a hard limit.
What happened
- Reported cause
- Read volume
- Incident date
- Date not recorded
- First reported
- 2026-09-01
- Billing outcome
- Credit issuedAuthor-reported
- Case progress
- Not established
- Public Cloudflare reply
- Not linked
Latest reported outcome
The author reports a US$976.11 account credit issued on August 19, covering part of the D1 charge and leaving US$500 uncredited; the author is still seeking an explanation of the calculation.
View this update in the timelineOriginal sources
Each entry links to the report or reply it describes.
Case timeline
Author reports a $1,481.11 D1 invoice and a partial credit
Open original sourceThe author says about 1.476 trillion rows read produced a US$1,481.11 invoice and Cloudflare granted a US$976.11 account credit, leaving US$500 uncredited.
Author says support gave no calculation
Open original sourceThe author says support only stated a dedicated Finance team set the credit amount.
Author says the case was closed again
Open original sourceThe author says support replied that the adjustment came from a case-specific billing review and the balance applies to future eligible invoices, then closed the case.
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.
An LLM agent wrote about 5 billion rows to D1, a $5,864.11 invoice.
Community user matthieu.marielouise says that between mid-May and mid-June 2026 an LLM coding agent shipped a change that rewrote the same data every few minutes, producing about 5 billion D1 writes and a $5,864.11 invoice on an account with a baseline of about $5 a month. He says billing alerts and budget thresholds did not fire in time and the alert emails landed in spam, and that a billing ticket filed June 11 requests a courtesy credit. About two weeks later he reports no answer and says a lawyer told him the debit breached PSD2 Article 64 consent rules.
Budget alerts
Cloudflare documents account-wide spend alerts and their notification limits.