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

Smart Shield Argocommunity-argo-r2-3000

Unexpected Argo and R2 charges of more than $3,000.

Community user lin229676791 (Adspult Media) says that with Argo and R2 configured together, the account was charged more than 3,000 US dollars; Argo bills by traffic while R2 advertises free egress, and they say the documentation did not state that the two affect each other. They disabled Argo and say three work orders asking for a one-time reduction or refund had no human reply after a week.

What happened

Reported cause: Traffic spike
Incident date: Date not recorded
First reported: 2026-03-18
Billing outcome: Request submittedAuthor-reported
Case progress: Not established
Public Cloudflare reply: Not linked

Latest reported outcome

The author says three work orders ask for a one-time reduction or refund and had no human reply after a week.

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-03-18
Author reports the charges
Open original source
The author reports Argo and R2 charges of more than $3,000 and asks for a reduction or refund.

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.

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.

Author experienceWorkers +4

Cloudflare billing pitfalls thread

The author organizes Cloudflare billing risks by product and shares experience with budget alert emails.

Other

sylwair: nearly $900 of usage in under two days after a project mistake.

@sylwair says a recent project mistake ran up nearly $900 in less than two days. He says he spotted it in Cloudflare's billable-usage view and stopped the abnormal service, and in a reply adds that the daily billing figures appeared with a delay, so the amount did not visibly drop after he stopped it.

Workers

RetainDB: a reported $36k bill from a queue loop with 81 users.

Reddit user alameenswe, building RetainDB on Workers, KV, Durable Objects and Queues, reports a Cloudflare bill of about $36k for one month with 81 users; the post body says $35,000. He attributes it to a queue consumer that re-queued async writes, 12 unbatched Durable Object writes per memory write and a kv.list() authentication fallback.