Source-linked reports: Amounts and outcomes come from the original reports and linked replies.
Indie game studio: R2 Class B re-fetches from a short cache TTL drove a $262.18 cycle.
teambrickstream reports a Jul 27–Aug 26 cycle totaling $262.18, of which $259.20 was R2 Class B operations (about 729.61M operations). Game images on a custom domain inherited a 4-hour origin Cache-Control as edge TTL, so unchanged files were re-read from R2 after each expiry. A $10 default budget alert fired on Aug 1 at $38.87 with subject “spending limit reached,” then spending continued for 26 more days. The author asks whether any portion can be credited and how to open a Billing case on the Free plan.
What happened
- Reported cause
- Read volume
- Incident date
- Date not recorded
- First reported
- 2026-08-27
- Billing outcome
- Request submittedAuthor-reported
- Case progress
- Not established
- Public Cloudflare reply
- Not linked
Latest reported outcome
The author asks for a credit review of the R2 Class B spike and help opening a Billing case on the Free plan; no staff outcome is posted.
View this update in the timelineOriginal sources
Each entry links to the report or reply it describes.
Case timeline
Author reports R2 Class B cache-TTL spike
Open original sourceThe author reports $262.18 with $259.20 from R2 Class B re-fetches after a 4-hour inherited cache TTL, and a misleading default budget alert.
More to read
How I keep Cloudflare under $5: where surprise bills come from
Ashish Sharma (@sarmaasis) runs several sites on the $5 Workers Paid plan and lists, product by product, the usage patterns he says quietly run up a Cloudflare bill, ending with a 12-item checklist.
babynarc: a Durable Objects alarm loop and a surprise bill that grew from $300 to $500.
@babynarc says an alarm loop in an old Durable Object he thought was inactive left him badly burned: he watched a surprise $300 bill grow to $500 even after killing it. Replying to Cloudflare's Dane Knecht and Kenton Varda, he suggests prepending budget-alert details to every `cf` result by default.
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.