billflare.

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

Otheruser78215-https-prefix-domain

user78215: a domain registered with the “https” prefix by mistake.

Community user user78215 says the https:// prefix from the browser was included in a search and httpsfincaeljardindelhuila.com was registered by mistake; the intended domain was registered separately. The author asks for a refund within the ICANN grace period.

What happened

Reported cause
Unknown
Incident date
2026-08-18
First reported
2026-08-20
Billing outcome
Request submittedAuthor-reported
Case progress
Not established
Public Cloudflare reply
Not linked

Latest reported outcome

The author requests a refund. A community MVP says Cloudflare does not refund domains and tickets usually take weeks.

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 dates the mistaken registration to August 18, 2026 and the correct one to August 20. The amount is not stated.

Author experienceAccount-wide usage-based products +1

Why hard spending caps take time: Ashley Peacock on billing latency

Ashley Peacock (@ashleypeacock), who works on Durable Objects at Cloudflare, explains from experience why near-real-time spending caps are hard to build, says hard billing caps are coming soon, and suggests budget alerts plus issue alerts in the meantime.

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 experienceDurable Objects +2

Packing always-awake Durable Objects into Containers to cut duration cost

Robert Chandler (@bertie_ai) says keeping 1,000 Durable Objects awake costs $4,050 a month, and that he ran the same 1,000 for $22 a month by pooling them inside Containers with workerd; the thread covers why, the durability trade-off and when real Durable Objects are still cheaper. The figures are the author’s calculations, not a bill.