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

R2cjy-r2-infrequent-access-config

One-time R2 Infrequent Access configuration error produced a $9.91 bill.

cjy reports billable usage of $9.00 for 17 R2 Infrequent Access Class A operations, $0.90 for 6 Class B operations, and $0.01 storage, totaling $9.91 after a one-time configure error, and asks for a one-time courtesy refund.

What happened

Reported cause: Unknown
Incident date: Date not recorded
First reported: 2026-05-19
Billing outcome: Request submittedAuthor-reported
Case progress: Not established
Public Cloudflare reply: Not linked

Latest reported outcome

The author requests a one-time courtesy refund; community replies point to billing support.

View this update in the timeline

Original sources

Original Cloudflare Community post

Each entry links to the report or reply it describes.

Case timeline

2026-05-19
Author reports R2 Infrequent Access $9.91 charge
Open original source
The author reports a $9.91 Infrequent Access bill from a one-time configure error and asks for a courtesy refund.

Author experienceWorkers +10

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.

Other

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.

Author experienceAccount-wide usage-based products +1

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.

Durable Objects

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.

Official docsAccount-wide usage-based products

Billable Usage API

Cloudflare introduces an API that returns a self-serve account’s usage and cost by product and service period, currently updated daily.

CloudPrinters.sa: an auth refresh-token bug drove about 2 billion D1 writes and a ~$2,078 charge.

Community user salman1 says D1 normally costs CloudPrinters.sa nothing, but over the August 16 to September 15, 2026 cycle an auth bug rewrote one account's entire refresh-token history every time a stale token was retried, generating roughly 2 billion D1 writes. He says the revoke logic and retry loop were fixed and that a billing ticket requests a courtesy credit for the D1 write overage of about $2,078.