Source-linked reports: Amounts and outcomes come from the original reports and linked replies.
Registrar, September 6, 2026: users charged, some twice, for domains that did not appear.
On September 5–7, 2026, many Community users reported paid Registrar invoices for domains that did not appear in their accounts; several retried and were charged twice. A community MVP quoted a Cloudflare Status notice about delays in provisioning newly purchased domains. Later posts report domains appearing and one refund received.
What happened
- Reported cause
- Unknown
- Incident date
- 2026-09-06
- First reported
- 2026-09-05
- Billing outcome
- Request submittedAuthor-reported
- Case progress
- Not established
- Public Cloudflare reply
- Not linked
Latest reported outcome
Several users ask for duplicate charges to be refunded. One user later says the refund for a duplicate two-year purchase was received; others report the domains appeared after the delay.
View this update in the timelineOriginal sources
- Grouped Community thread
- Merged duplicate-charge report
- Merged double-billing report
- Merged paid-twice report
Each entry links to the report or reply it describes.
Case timeline
First report: charged, no domain
Open original sourceiyimide.adekile says a tevernit.com purchase produced an invoice and a card charge but the domain is not in the dashboard. A community MVP says it is most likely an authorization rather than an actual charge.
A user asks for the money back
Open original sourcedenissanturyan says a domain was charged but never registered, the paid Registrar Registration Fee invoice is visible, and asks for the money back; after following an MVP’s steps the support form appears.
Thread opens
Open original sourcesbuxreg reports a paid invoice for sbuxreg.com without the domain and says a ticket cannot be filed. Other users post the same issue in the thread.
Two invoices for two attempts
Open original sourcepeter.schittenhelm says two registration attempts for evox-cloud.com produced two invoices and no domain.
Paid twice before the domain registered
Open original source0xpufferfish says the first purchase of remorarent.com was charged but not registered, a second purchase registered it, and asks for the first payment to be refunded.
Partial refund requested for a duplicate term
Open original sourcejichuo209117 says two consecutive two-year payments for bilibili.date left only two years on the renewal date and asks for the duplicate to be partly refunded.
Double billed, invoices listed
Open original sourcem.woeppel reports being double billed for frontdesk918.com with invoices IN-78174929 and IN-78175132 and no registration.
One user reports a refund
Open original sourcejichuo209117 writes: “The refund has also been received. Thank you for your support.”
Domains appear for another user
Open original sourcebradleystephenson33, who listed case 02315151 and invoices IN-78174669 and IN-78174762, says both domains now appear in the dashboard.
Cloudflare Status notice quoted
Open original sourceCommunity MVP Laudian quotes a Cloudflare Status incident: “We are investigating reports of delays in the provisioning of newly purchased domains.”
Resolved shortly after the request
Open original sources.chudjak, charged $10.46 under IN-78175799, says the issue was solved shortly after the request.
More to read
A budget alert is a horn, not a brake
@GUYUE_LGY points to Cloudflare’s Budget alerts documentation: alerts send email when spend crosses a threshold but do not pause or cap usage. Before letting AI run unattended, the author checks what actually happens at the line.
Lion Brain: a Durable Object alarm loop from an AI-coding bug wrote about 250 million rows, roughly $210.
Replying in another user's Community thread, bennygoldstein says a bug written by an AI coding tool made a Durable Object alarm in their Lion Brain app re-index the same data every few seconds on October 10 and 11, 2026, writing about 250 million rows and costing roughly $210 in overage on Workers Paid. He says he only found out from the budget alert email, which never pauses anything, and that he opened a billing case asking for a one-time courtesy credit and a real hard spending cap.
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.