Source-linked reports: Amounts and outcomes come from the original reports and linked replies.

Otheranon69-accidental-domain-renewal

anon69: an accidental renewal of the wrong domain.

Community user anon69 says they accidentally renewed the wrong domain under invoice IN-78475360 and asks for a refund. A community MVP says domain renewals are final; the author later submits a support case.

What happened

Reported cause: Unknown
Incident date: Date not recorded
First reported: 2026-09-09
Billing outcome: Request submittedAuthor-reported
Case progress: Not established
Public Cloudflare reply: Not linked

Latest reported outcome

The author requests a refund and later reports submitting a support case. No outcome is reported.

View this update in the timeline

Original sources

Original author report

Each entry links to the report or reply it describes.

Case timeline

2026-09-09
Author reports the disputed charge
Open original source
The author says the renewal was made minutes earlier and the intended domain was renewed separately. The amount is not stated.

Official docsAccount-wide usage-based products

Budget alerts

Cloudflare documents account-wide spend alerts and their notification limits.

Durable Objects

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.

Author experienceDurable Objects +2

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.

Durable Objects

A software defect drove a Durable Objects usage spike and a $3,800+ invoice; support declined a refund under standard policy.

Cloudflare Community user dev.in1 says a one-time software defect in their application sharply increased Durable Objects usage, mainly Storage Rows Written and Requests, producing an invoice of more than $3,800 for the September 2026 billing period. The author says the issue was identified, fixed and redeployed, with monitoring and alerts added. They report that support confirmed the usage was metered but said usage-based charges are not refundable under the standard policy, and they ask for escalation for a one-time courtesy adjustment.

Author experienceD1 +1

D1 scheduled updates: count runs, not empty queues

wickedev explains how a once-daily full-table update ran hundreds of times a day, and shares the checks he would add after an unexpected D1 bill.

Sagor Hossen: R2 setup mistake produced an unexpected bill that support refunded.

Sagor Hossen (@SagorHossen3d) says an R2 setup mistake entirely on his side caused an unexpected bill, and that Cloudflare support resolved the billing dispute and issued a refund within hours. He does not state the dollar amount.