Source-linked reports: Amounts and outcomes come from the original reports and linked replies.
Truong Dang: a $9 R2 Infrequent Access charge for 51 operations, disputed over rounding.
Truong Dang (@cosmodane) says Cloudflare charged him the full $9 for 51 Class A operations on R2 Infrequent Access, which he calculates should have cost $0.00046. He says his billing ticket went unanswered for 19 days and that a rule rounding usage up to the next million was added to the pricing docs after he was billed. He asks for a refund of the $9; CloudflareHelp publicly asks him to DM his ticket details.
What happened
- Reported cause
- Unknown
- Incident date
- Date not recorded
- First reported
- 2025-07-26 02:30 UTC
- Billing outcome
- Request submittedAuthor-reported
- Case progress
- Not established
- Public Cloudflare reply
- Response recorded
Latest reported outcome
The author says he opened a billing ticket and asks Cloudflare to refund the $9 charge. CloudflareHelp replied publicly asking him to DM the ticket number, account email or domain so someone could take a look.
View this update in the timelineOriginal sources
- Original thread: $9 for 51 requests
- Author's cost calculation
- Ticket wait and pricing-doc change
- Author's refund request
- CloudflareHelp public reply
Each entry links to the report or reply it describes.
Case timeline
$9 charged for 51 API requests
Read on 𝕏The author says Cloudflare charged him $9 for just 51 API requests, that his billing ticket had gone 19 days without a response, and that the pricing docs were changed after he was billed.
Truong Dang
@cosmodane · Original 𝕏 post
Cloudflare charged me $9 for just 51 API requests. I opened a billing ticket 19 days ago — no response. Now they silently changed their pricing docs after billing me. This is dishonest. (Thread 👇) pic.twitter.com/QXkxZ0qdIq
Author's cost calculation
Read on 𝕏He says R2 Infrequent Access charges $9 per million Class A operations; at 51 operations that should cost $0.00046, but he was charged the full $9.
Truong Dang
@cosmodane · Original 𝕏 post
I used R2 Infrequent Access, which charges: $9 per 1 million Class A operations I only made 51 operations That should cost: 51 ÷ 1,000,000 × $9 = $0.00046 But Cloudflare charged me the full $9
Ticket wait and a pricing-doc edit
Read on 𝕏He says the official pricing page did not mention rounding when he was billed, that his ticket with full proof went unanswered for 19 days, and then links a change in Cloudflare's GitHub docs repository.
Truong Dang
@cosmodane · Original 𝕏 post
Their official pricing page never mentioned rounding at the time I was billed. I filed a support ticket with full proof. They didn’t respond for 19 days. Then suddenly, this shows up in their GitHub repo: 👇https://t.co/sYDGJpW0c5 pic.twitter.com/ZQ7ByxmNNs
Rounding rule added after billing
Read on 𝕏He says a section stating usage is rounded up to the next million was added after he was billed, with no notice, support or refund.
Truong Dang
@cosmodane · Original 𝕏 post
They added a section saying usage will be rounded up to the next million. That change happened after they billed me, not before. No notice. No support. No refund. Just a silent edit.
Author calls the change a breach of trust
Read on 𝕏He says changing documentation after the fact to justify the charge is a breach of trust.
Truong Dang
@cosmodane · Original 𝕏 post
This is not just a billing issue — it’s a breach of trust. Changing documentation after the fact to justify a questionable charge is dishonest. If you made a mistake, own it. Don’t rewrite history.
Refund of the $9 requested
Read on 𝕏He asks Cloudflare to refund the $9 charge, acknowledge the change was made after his billing, and respond to support tickets in a timely way.
Truong Dang
@cosmodane · Original 𝕏 post
I’m asking Cloudflare to: Refund the incorrect $9 charge Acknowledge the change was made after my billing Respond to support tickets in a timely, transparent way@Cloudflare — we deserve better.
Author asks R2 users to check invoices
Read on 𝕏He asks other R2 developers to check their invoices.
Truong Dang
@cosmodane · Original 𝕏 post
If you're a developer using Cloudflare R2, check your invoices. They may be charging you more than you owe — and fixing the rules after. This shouldn't be acceptable from a company at this scale.#Cloudflare #BillingIssue #R2Storage #Transparency #DeveloperRights
CloudflareHelp asks for ticket details
Read on 𝕏CloudflareHelp replies to the refund request, apologizes for the frustration and asks him to DM his ticket number, account email or domain so it can try to get someone to take a look.
Cloudflare Help
@CloudflareHelp · Original 𝕏 post
Hey @cosmodane, Sorry to hear about the frustration. Please DM me with your ticket number, account email, or domain so I can try and get someone to take a look.
More to read
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.
Layered defenses after a Durable Object alarm loop
星星之火可以燎原 (@fireandstart) reads a public Durable Object alarm-loop recap and argues for layered defenses rather than relying on being more careful next time.
Cloudflare costs $5 a month, but the bill is not capped
不追高 (@Ariella1213) writes an X article explaining that Workers Paid’s $5 is a minimum, that per-product limits and budget alerts do not cap the account bill, and how denial-of-wallet requests, write amplification, delayed stops and background retries add cost.