Source-linked reports: Amounts and outcomes come from the original reports and linked replies.
kim999: a sudden R2 Infrequent Access charge with no IA bucket.
Community user kim999 says an R2 Infrequent Access charge suddenly appeared that month although no bucket used the Infrequent default storage class, no R2 bucket was created that month, and the only new projects were five Cloudflare Pages sites that do not touch R2. The post does not state the amount. A former Cloudflare community member replies that billing questions must go through a support request.
What happened
- Reported cause
- Unknown
- Incident date
- Date not recorded
- First reported
- 2026-03-10
- Billing outcome
- Not recorded
- Case progress
- Not established
- Public Cloudflare reply
- Not linked
Latest reported outcome
The author asks where the charge came from; no billing request 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 reports an unexplained R2 IA charge
Open original sourceThe author says an Infrequent Access charge appeared although no bucket uses that storage class and no R2 bucket was created that month.
More to read
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.
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.
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.