billflare.

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

Otheramadzay-domain-charged-twice

amadzay: charged twice for the same domain.

Community user amadzay says change2coin.com was charged twice under invoice IN72161524 and a case could not be opened.

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
Not linked

Latest reported outcome

The author files the post under Invoice to get the duplicate reviewed. A community MVP links the case page.

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 amount is not stated.

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.

D1

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.

Official docsAccount-wide usage-based products

Budget alerts

Cloudflare documents account-wide spend alerts and their notification limits.