Source-linked reports: Amounts and outcomes come from the original reports and linked replies.
serakib: a USD 9.01 R2 invoice while believing usage stayed in the free tier.
Community user serakib (aicart.store) says an R2 invoice for USD 9.01 arrived although monitoring suggested usage stayed within the free tier, asks for a breakdown and for the charge to be waived or corrected if it was an error, and says a ticket got no response. Community MVPs reply that the charge comes from Infrequent Access, which has no free allowance, and that objects can be written to IA even when bucket defaults are Standard.
What happened
- Reported cause
- Unknown
- Incident date
- Date not recorded
- First reported
- 2026-06-14
- Billing outcome
- Request submittedAuthor-reported
- Case progress
- Not established
- Public Cloudflare reply
- Not linked
Latest reported outcome
The author asks for the charge to be waived or corrected; the ticket has no reply 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 USD 9.01 R2 invoice
Open original sourceThe author says usage stayed in the free tier, asks for a breakdown and a waiver or correction.
Author says the ticket has no response
Open original sourceThe author says a ticket was created but got no response, and an overdue account cannot see ticket details.
More to read
Cloudflare billing risk audit skill for coding agents
Kid (@singkid9527), who collects cases and guides for Billflare, open-sourced a skill that has a coding agent review a project's configuration and source in read-only mode for paths that can amplify Cloudflare costs.
A software defect drove a Durable Objects usage spike and a $3,800+ invoice; support declined a refund under standard policy.
Cloudflare Community user dev.in1 says a one-time software defect in their application sharply increased Durable Objects usage, mainly Storage Rows Written and Requests, producing an invoice of more than $3,800 for the September 2026 billing period. The author says the issue was identified, fixed and redeployed, with monitoring and alerts added. They report that support confirmed the usage was metered but said usage-based charges are not refundable under the standard policy, and they ask for escalation for a one-time courtesy adjustment.
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.