Source-linked reports: Amounts and outcomes come from the original reports and linked replies.
pandaword: $4.50 R2 charge with Class A usage under the free 1M, then an account downgrade.
Community user pandaword says R2 Class A usage for January 29 to February 27 was 194,759 operations, under the 1 million free limit, yet the account was charged $4.50. The author says ticket #01999798 had no human response for three days and the account was then blocked and downgraded; two days later the author says there is still no reply.
What happened
- Reported cause
- Unknown
- Incident date
- Date not recorded
- First reported
- 2026-03-06
- Billing outcome
- Request submittedAuthor-reported
- Case progress
- Not established
- Public Cloudflare reply
- Not linked
Latest reported outcome
The author disputes the charge through ticket #01999798; no reply or outcome is reported in the thread.
View this update in the timelineOriginal sources
Each entry links to the report or reply it describes.
Case timeline
Author disputes a $4.50 R2 charge
Open original sourceThe author reports 194,759 Class A operations, below the free limit, billed at $4.50, a ticket with no reply, and an account downgrade.
Author says the ticket is still unanswered
Open original sourceThe author says there is still no reply on the ticket and asks for escalation.
More to read
Cloudflare Medivh: a self-hosted near-real-time bill estimator
An open-source, self-hosted monitor that adds today’s estimated usage cost to Cloudflare’s daily-updated billable usage, sends summaries, and calls a webhook when the current cycle crosses a budget.
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.
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.