Source-linked reports: Amounts and outcomes come from the original reports and linked replies.
chiveslee1987: an R2 Infrequent Access charge for a service never used.
Community user chiveslee1987 reports an erroneous charge for R2 Infrequent Access, which the author says was never used or subscribed to and does not appear under subscriptions, and asks for the service to be stopped and a full refund processed. The author later says ticket 02196536 has had no response. The amount is not stated.
What happened
- Reported cause
- Unknown
- Incident date
- Date not recorded
- First reported
- 2026-06-22
- Billing outcome
- Request submittedAuthor-reported
- Case progress
- Not established
- Public Cloudflare reply
- Not linked
Latest reported outcome
The author requests a full refund via ticket 02196536; no reply is reported.
View this update in the timelineOriginal sources
Each entry links to the report or reply it describes.
Case timeline
Author requests a refund of R2 IA charges
Open original sourceThe author says the account was charged for R2 Infrequent Access without usage and asks for a full refund.
Author says the ticket has no reply
Open original sourceThe author says ticket 02196536 was submitted but no one has responded.
More to read
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.
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.
Designing a poker game on Durable Objects so idle time costs nothing
Philip Atkinson describes the architecture of his multiplayer poker game on the Cloudflare Developer Platform and the cost rules he follows: archive finished games out of Durable Object storage, hibernate WebSockets, wake with alarms and treat logging as a cost decision.