Source-linked reports: Amounts and outcomes come from the original reports and linked replies.
lieft: 51.1M D1 rows written billed $52 where the author expected $2.
Community user lieft says D1 rows written for the billing cycle were 51,129,049, only 1,129,049 above the 50 million free allowance, so the charge should have been $2 instead of the $52 on the invoice. The author asks for a refund, reposts when no one replies, and later says a support request was filed but still had not been handled.
What happened
- Reported cause
- Write volume
- Incident date
- Date not recorded
- First reported
- 2025-10-18
- Billing outcome
- Request submittedAuthor-reported
- Case progress
- Not established
- Public Cloudflare reply
- Not linked
Latest reported outcome
The author asks for a refund of the difference and says the support request is unhandled; no outcome is reported.
View this update in the timelineOriginal sources
Each entry links to the report or reply it describes.
Case timeline
Author disputes a $52 D1 rows-written charge
Open original sourceThe author says 1,129,049 rows above the free allowance should cost $2, not $52, and asks for a refund.
Author says the support request is unhandled
Open original sourceThe author says a support request was filed but no one has dealt with it.
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.
shmily7: a Durable Object alarm loop and a reported US$10,811.41 bill.
@shmily7 reports a Durable Object alarm loop in an unused test project, then says he paid the full US$10,811.41 bill to avoid service suspension. Cloudflare’s Ashley Peacock publicly says he is looking into it internally and will follow up. Cloudflare’s Dane Knecht later replies that he escalated it too. On October 9 the author declares the case closed: he reports that, with Ashley Peacock’s help, Cloudflare decided to refund the charges incurred during the bug in full, with the money still to arrive, and posts the support ticket reply he received.
Budget alerts
Cloudflare documents account-wide spend alerts and their notification limits.