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

Otherserial-founder-downgraded-then-charged-again

serial_founder: a whole account downgraded, then a zone charged a second time.

Community user serial_founder says support was asked to move two zones from Business to Pro, but the entire account was downgraded to Free, including a third zone paid two days earlier, which was then charged a second time. The ticket form is removed because the support entitlement reads “self-serve free.”

What happened

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

Latest reported outcome

The author asks for the billing case to be opened and the double charge reviewed. Another user replies in sympathy; 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-07-27
Author reports the disputed charge
Open original source
The author quotes API responses showing an active $250 monthly Business plan alongside “create_tickets”: false. The amount of the second charge is not stated.

Author experienceAccount-wide usage-based products +1

Why hard spending caps take time: Ashley Peacock on billing latency

Ashley Peacock (@ashleypeacock), who works on Durable Objects at Cloudflare, explains from experience why near-real-time spending caps are hard to build, says hard billing caps are coming soon, and suggests budget alerts plus issue alerts in the meantime.

Other

hfcorriez: $100+ of AI-driven extra usage over two months, reported cancelled after emails.

@hfcorriez says AI caused over $100 of extra consumption over two months. He says that after two rounds of email explaining the situation to Cloudflare, the charges were cancelled, and posts a screenshot of two negative line items (-$31.92 and -$75.42) marked Fully Applied.

Official docsAccount-wide usage-based products

Budget alerts

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

Other

Meathill: OpenNext KV ISR cache left unpaid TTL work and ballooned storage.

Meathill reports that an OpenNext Cloudflare KV incremental-cache path for Next.js ISR left a TODO for KV TTL, so versioned page snapshots accumulated. Dashboard billable storage showed 3.59 GB-month over the 1 GB free allowance with ongoing extra charges, and historical zombie data reached about 24 GB before he moved to a new namespace. He does not state a dollar invoice total.

zmuleyu (yourchars.com): a $1,481.11 invoice from 1.476 trillion D1 rows read, with a $976.11 account credit.

Community user zmuleyu (yourchars.com) says an unintended query pattern repeatedly ran high-volume D1 scans during the July 17–August 16 billing period, reading about 1.476 trillion rows and producing a US$1,481.11 invoice (US$1,476.11 for D1 plus US$5 for Workers Paid). The author restricted public access, fixed the query path and added controls and alerts. Cloudflare granted a US$976.11 account credit on August 19, leaving US$500 of the D1 charge uncredited. The author asks how the credit was calculated, why US$500 was left, and how the balance can be used; support said the amount came from a case-specific review by a Finance team, the balance applies automatically to future eligible invoices, and closed the case again. The author notes budget alerts on Workers Paid are informational, not a hard limit.

Community resourceWorkers +3

Cloudflare Recognizer

An open-source Workers + KV tool that polls Cloudflare analytics on a cron, tracks usage against a contract commit on a custom billing cycle, and alerts on surges, aimed at Enterprise accounts.