Source-linked reports: Amounts and outcomes come from the original reports and linked replies.
stefanosalexandrou1: a disputed renewal charge on a domain without auto-renew.
Community user stefanosalexandrou1 says a domain was renewed and charged although auto-renewal was not enabled, opened urgent case 02220667 on July 3, 2026 and requests a full refund. After six days only an automated reply had arrived.
What happened
- Reported cause
- Unknown
- Incident date
- 2026-07-03
- First reported
- 2026-07-13
- Billing outcome
- Request submittedAuthor-reported
- Case progress
- Not established
- Public Cloudflare reply
- Not linked
Latest reported outcome
The author requests a full refund in case 02220667 and says the bot misread it as a cancellation request.
View this update in the timelineOriginal sources
Each entry links to the report or reply it describes.
Case timeline
Author reports the disputed charge
Open original sourceA community MVP says automatic renewal before expiry is authorized by the terms; the author replies that auto-renewal was not enabled on this domain. The amount is not stated.
More to read
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.
Refunds are not a safety net: install your own brakes on cloud bills
SagaSu (@sujingshen) writes a loss-control guide for indie developers: usage-billed code can burn money with zero users, refunds should be planned as zero, and budget alerts are not brakes; it lists five things to set up beforehand and what to do once a bill has already spiked.
Sven Guettner: a D1 bug produced a $1,868 bill from about 1.89 trillion row reads.
Sven Guettner says a wrong database setting on offercompass.app made every small update read the whole table in the background between Aug 28 and Sep 22, 2026, totaling about 1.89 trillion rows and a $1,868 D1 bill. He fixed the bug, shut the project down, opened ticket 02338870 asking for a courtesy credit, and reports only AI replies so far.