Source-linked reports: Amounts and outcomes come from the original reports and linked replies.
ahmedibrahimhablas20: a script misconfiguration put about 980 GB in R2, a $15.66 invoice and a frozen account.
Community user ahmedibrahimhablas20, an independent developer archiving vintage heritage audio for a non-profit project, says an automated script misconfiguration caused an unintended storage spike of nearly 980 GB in an R2 bucket. Usual billing is under $3, but the spike produced a $15.66 invoice. The author deleted the bucket, opened case 02057449 on April 5 asking for a waiver, and says the account has been downgraded to Free with R2 deactivated for more than 10 days without human contact.
What happened
- Reported cause
- Write volume
- Incident date
- Date not recorded
- First reported
- 2026-04-13
- Billing outcome
- Request submittedAuthor-reported
- Case progress
- Not established
- Public Cloudflare reply
- Not linked
Latest reported outcome
The author asks Cloudflare to waive the $15.66 invoice via case 02057449; no reply 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 asks to waive a $15.66 R2 spike invoice
Open original sourceThe author reports a 980 GB accidental storage spike, a $15.66 invoice against usual bills under $3, a downgraded account, and case 02057449 with no reply.
More to read
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.
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.
Designing a poker game on Durable Objects so idle time costs nothing
Philip Atkinson describes the architecture of his multiplayer poker game on the Cloudflare Developer Platform and the cost rules he follows: archive finished games out of Durable Object storage, hibernate WebSockets, wake with alarms and treat logging as a cost decision.