billflare.

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

Othermatteo5-unwanted-service-charged-three-times

matteo5: a mistaken activation charged three times before a reply.

Community user matteo5 says a service was activated by mistake, a ticket asking what to do was opened right away, and two months later there was still no reply while the card had been charged a third time. The author asks for a refund.

What happened

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

Latest reported outcome

The author asks for a refund and says a second ticket was opened. Another user replies that support is hard to reach.

View this update in the timeline

Original sources

Each entry links to the report or reply it describes.

Case timeline

  1. Author reports the disputed charge

    Open original source

    The post does not name the service or the amounts.

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.

Workers

RetainDB: a reported $36k bill from a queue loop with 81 users.

Reddit user alameenswe, building RetainDB on Workers, KV, Durable Objects and Queues, reports a Cloudflare bill of about $36k for one month with 81 users; the post body says $35,000. He attributes it to a queue consumer that re-queued async writes, 12 unbatched Durable Object writes per memory write and a kv.list() authentication fallback.