billflare.

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

D1daniel207-d1-dashboard-row-reads

daniel207: a dashboard left open overnight drove D1 row reads into a very large bill.

Community user daniel207 says that while getting D1 working, a dashboard generated a large number of row-read calls and was left open overnight, causing a very large bill on a Pro plan; the product is now offline. The author sent a billing request (case 02075425), escalated it, and has had no acknowledgement. The author has since set budget warnings, says they would not have helped here, and asks Cloudflare for rate limiting or a hard pause limit. No amount is stated.

What happened

Reported cause
Read volume
Incident date
Date not recorded
First reported
2026-04-20
Billing outcome
Request submittedAuthor-reported
Case progress
Not established
Public Cloudflare reply
Not linked

Latest reported outcome

The author's billing request (case 02075425) has had no acknowledgement; no outcome is reported.

View this update in the timeline

Original sources

Each entry links to the report or reply it describes.

Case timeline

  1. Author reports a large D1 row-reads bill

    Open original source

    The author says a dashboard left open overnight caused heavy D1 row reads, the product is offline, and case 02075425 has no reply.

Community resourceWorkers +3

Appflare spend protection: per-app usage alerts and automatic pausing in your own account

Appflare, an open-source (Apache-2.0) app manager that runs as a Worker in your own Cloudflare account, added spend protection: it reads each installed app’s usage every 5 minutes, alerts on unusual usage, and can pause an app that runs away.

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.

Official docsAccount-wide usage-based products

Budget alerts

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