billflare.

Source-linked reports: Amounts and outcomes come from the original reports and linked replies.

R2omar-aaaa402-r2-ia-class-a

omar.aaaa402: disputes R2 Infrequent Access Class A invoices of $9.01 and $10.46.

Community user omar.aaaa402 disputes invoice IN-72245851 for $9.01 (about 1M R2 Infrequent Access Class A ops, Jun 21–Jul 19, 2026) and a prior $10.46 charge on a pre-launch sadarat.com project with effectively no traffic. GraphQL analytics for the period returned zero operations. A community reply explains IA has no free allowance and rounds up to the next million.

What happened

Reported cause
Unknown
Incident date
2026-06-21
First reported
2026-07-25
Billing outcome
Request submittedAuthor-reported
Case progress
Not established
Public Cloudflare reply
Not linked

Latest reported outcome

The author disputes $9.01 and prior $10.46 IA charges; community explains IA rounding. Reported amount records the named $9.01 invoice, not a sum.

View this update in the timeline

Original sources

Each entry links to the report or reply it describes.

Case timeline

  1. Author disputes $9.01 R2 IA Class A invoice

    Open original source

    The author disputes IN-72245851 ($9.01) and a prior $10.46 IA charge despite zero GraphQL-reported operations in the period.

Author experienceWorkers +5

How to cap your Cloudflare Workers bill, and what you cannot cap

CostHex concludes there is no dollar cap that stops a Worker, and lays out what can contain a bill instead: per-invocation limits, keeping abusive traffic away, and earlier warnings.

Workers AI

hung: Workers AI neuron charges billed despite expected free usage.

In a Hacker News comment, hung says that with paid Workers he was billed for confusing Workers AI neuron usage that should have been covered under usage limits, never got an answer on why, and that support ignored his ticket.

Author experienceAccount-wide usage-based products

A budget alert is a horn, not a brake

@GUYUE_LGY points to Cloudflare’s Budget alerts documentation: alerts send email when spend crosses a threshold but do not pause or cap usage. Before letting AI run unattended, the author checks what actually happens at the line.