Source-linked reports: Amounts and outcomes come from the original reports and linked replies.
apexyue: two charges for failed registrations of one domain.
Community user apexyue says two orders for xhpep.com were charged although the registration failed, and asks for a full refund. The author has also contacted the bank.
What happened
- Reported cause
- Unknown
- Incident date
- Date not recorded
- First reported
- 2026-08-26
- Billing outcome
- Request submittedAuthor-reported
- Case progress
- Not established
- Public Cloudflare reply
- Not linked
Latest reported outcome
The author requests a full refund and later says the card was charged and the bank has been contacted. A community MVP suggests it may be an authorization hold.
View this update in the timelineOriginal sources
Each entry links to the report or reply it describes.
Case timeline
Author reports the disputed charge
Open original sourceThe author writes in Chinese and English that payments succeeded but the domain registration failed. A community MVP says the funds may never have settled.
More to read
wickedev: a D1 ranking-update loop and about $10,846 across two billing periods.
wickedev reports about $10,846 from a repeated D1 ranking update: a paid $6,209 September bill plus $4,637 estimated for the October billing period. He later says a $5,704 refund was approved and is still being processed.
Budget alerts
Cloudflare documents account-wide spend alerts and their notification limits.
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.