billflare.

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

Othercyfitnessapp-three-domains-agp-refund

cyfitnessapp: three domains deleted the same day and a refund request.

Community user cyfitnessapp says three domains were registered by accident and deleted the same day within the Add Grace Period on the advice of Cloudflare’s AI support agent, then a portal error prevented opening a case. A Cloudflare staff member later posts that case #02250227 was created.

What happened

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

Latest reported outcome

The author asks for a refund or reinstatement of the domains. Cloudflare Customer Reliability Engineer cf-scott posts “Case #02250227 Created”; no outcome is reported.

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 says the case form disappears after a 403 from an access/organizations API call. A community MVP says domain purchases are final even within AGP.

  2. Author restates the request

    Open original source

    The author asks for a refund or reinstatement of the three domains and cites EU consumer rights.

  3. Staff creates a case

    Open original source

    Cloudflare staff member cf-scott, titled Customer Reliability Engineer, replies: “Case #02250227 Created.”

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.

Workers

A voting page polling every three seconds: the author revises a $1,000 report.

@keking99 first reports about $1,000 for a voting page polling /api/result every three seconds. A later post reports $816.52 in accumulated usage as of October 4 and cites another screenshot total of $817.14. He later says his support ticket keeps being refused.

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.