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

Otheruser22095-pro-charged-after-may-cancel

user22095: Pro billing every month after a May cancellation.

Community user user22095 says two support cases have been open since May with no response while the account is still billed each month for Pro after cancellation, and considers a credit card chargeback.

What happened

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

Latest reported outcome

The author says over ten emails were sent on the open cases and that a chargeback is the next step if Cloudflare does not resolve it.

View this update in the timeline

Original sources

Original author report

Each entry links to the report or reply it describes.

Case timeline

2026-08-16
Author reports the disputed charge
Open original source
A community MVP says billing issues need Support and suggests replying to the ticket email. The amount is not stated.

wickedev: a D1 ranking-update loop and about $10,846 across two billing periods.

wickedev reports about $10,846 from a repeated D1 ranking update: a paid $6,209 September bill plus $4,637 estimated for the October billing period. He later says a $5,704 refund was approved and is still being processed.

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.

Official docsAccount-wide usage-based products

Budget alerts

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

Other

sylwair: nearly $900 of usage in under two days after a project mistake.

@sylwair says a recent project mistake ran up nearly $900 in less than two days. He says he spotted it in Cloudflare's billable-usage view and stopped the abnormal service, and in a reply adds that the daily billing figures appeared with a delay, so the amount did not visibly drop after he stopped it.

mcwangcn reports $1,300 in D1 charges after a bot attack.

@mcwangcn says D1 writes previously cost over a thousand dollars and separately mentions Workers CPU charges without giving an amount. He later shares a Cloudflare bill and says $1,300 of its $3,600 came from D1 after a bot attack.

Durable Objects

Lion Brain: a Durable Object alarm loop from an AI-coding bug wrote about 250 million rows, roughly $210.

Replying in another user's Community thread, bennygoldstein says a bug written by an AI coding tool made a Durable Object alarm in their Lion Brain app re-index the same data every few seconds on October 10 and 11, 2026, writing about 250 million rows and costing roughly $210 in overage on Workers Paid. He says he only found out from the budget alert email, which never pauses anything, and that he opened a billing case asking for a one-time courtesy credit and a real hard spending cap.