Source-linked reports: Amounts and outcomes come from the original reports and linked replies.
bibhutipd: $9.01 for 644 R2 Infrequent Access operations; support says it will review a goodwill credit.
Community user bibhutipd (trailshorts.xyz) says a $9.01 charge came from 644 R2 Infrequent Access Class A operations rounded up to one million at $9.00 per million, after configuring IA through lifecycle rules without realising IA has no free tier. The author deleted the IA objects, switched to Standard and asks for a one-time goodwill credit. A community MVP replies that the policy is documented, then shares how to open a billing case. The author later says a ticket was created and the Cloudflare team confirmed it would review a one-time goodwill credit once the invoice is created.
What happened
- Reported cause
- Unknown
- Incident date
- Date not recorded
- First reported
- 2026-09-18
- Billing outcome
- Review promisedAuthor-reported
- Case progress
- Not established
- Public Cloudflare reply
- Not linked
Latest reported outcome
The author reports that Cloudflare confirmed it will review a one-time goodwill credit once the invoice is created; no credit is reported yet.
View this update in the timelineOriginal sources
Each entry links to the report or reply it describes.
Case timeline
Author asks for a goodwill credit on $9.01
Open original sourceThe author says 644 IA Class A operations were rounded to one million and billed $9.01, and asks for a one-time goodwill credit.
Author reports Cloudflare will review a goodwill credit
Open original sourceThe author says a ticket was created and the Cloudflare team confirmed it will review a one-time goodwill credit once the invoice is created.
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.
hfcorriez: $100+ of AI-driven extra usage over two months, reported cancelled after emails.
@hfcorriez says AI caused over $100 of extra consumption over two months. He says that after two rounds of email explaining the situation to Cloudflare, the charges were cancelled, and posts a screenshot of two negative line items (-$31.92 and -$75.42) marked Fully Applied.
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.