Source-linked reports: Amounts and outcomes come from the original reports and linked replies.
fa3: an accidental Business plan purchase and a $2,653.20 charge.
fa3 says a colleague accidentally added a domain with a Business plan. He reports a $2,653.20 charge, deleting the unused domain within about an hour, and requesting a refund through support.
What happened
- Reported cause
- Unknown
- Incident date
- 2026-02-09
- First reported
- Date not recorded
- Billing outcome
- Request submittedAuthor-reported
- Case progress
- Not established
- Public Cloudflare reply
- Not linked
Latest reported outcome
The author requests a refund through support and says he is waiting for a response.
View this update in the timelineOriginal sources
Each entry links to the report or reply it describes.
Case timeline
Undated
Author reports the disputed charge
Open original sourceThe author dates the accidental purchase to February 9, 2026 and says the domain was never activated. He says he requested help the same day and still awaited a refund response. A reply from a user labelled Former Cloudflare routes the case to the appropriate team.
More to read
babynarc: a Durable Objects alarm loop and a surprise bill that grew from $300 to $500.
@babynarc says an alarm loop in an old Durable Object he thought was inactive left him badly burned: he watched a surprise $300 bill grow to $500 even after killing it. Replying to Cloudflare's Dane Knecht and Kenton Varda, he suggests prepending budget-alert details to every `cf` result by default.
Moving a blog to EmDash on the D1 free tier: row reads ran out and the author rolled back twice
tozai (@ccietry_tozai) tried moving a WordPress blog with about 800 daily unique visitors and 7,000 page views to EmDash on Cloudflare, exceeded D1’s 5 million daily rows-read free limit, and went back to WordPress rather than move to a paid plan without a hard cap.
Budget alerts
Cloudflare documents account-wide spend alerts and their notification limits.