billflare.

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

Othermatthew61-io-registration-stuck-duplicate

matthew61: a .io registration stuck after payment, with an accidental duplicate order.

Community user matthew61 says moyeo.io stayed on “Domain will be ready soon” after payment, the order status showed payment SETTLED and provisioning QUEUED, and an accidental duplicate order was also placed. A community MVP says the registration failed and the payment is likely a hold.

What happened

Reported cause
Unknown
Incident date
Date not recorded
First reported
2026-08-06
Billing outcome
Request submittedAuthor-reported
Case progress
Not established
Public Cloudflare reply
Not linked

Latest reported outcome

The author files the post under Refunds. A community MVP suggests a Billing ticket to check the payment.

View this update in the timeline

Original sources

Each entry links to the report or reply it describes.

Case timeline

  1. Author reports the disputed charge

    Open original source

    The author disputes that this is only a failed purchase and quotes the order-status fields. Amounts in the post are not tied to a single disputed charge.

Author experienceAccount-wide usage-based products

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.

Other

Dawei Ma: RealtimeKit billed during Beta, about $295 disputed, later refunded.

Dawei Ma (@madawei2699) says RealtimeKit was documented as free during Beta, yet he was billed $147.62 at GA prices with voice traffic counted as audio/video, then charged about $30 more as stale sessions kept 10 participants live. He says disputed charges reached about $295 under an engineering investigation, and later that the charges were refunded without an explanation.

Author experienceD1 +1

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.