billflare.

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

Otheruser80918-workers-yearly-charge-cancel-blocked

user80918: a yearly Workers charge while cancellation was blocked.

Community user user80918 says a dashboard error about a billing profile discrepancy blocked cancellation of an unused Workers subscription, and a yearly charge went through. The account then dropped to Workers Free. The author asks for a full reimbursement.

What happened

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

Latest reported outcome

The author asks for a full reimbursement of the yearly charge. After following a community guide, the author says opening a ticket worked.

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 quotes the error “There’s a discrepancy between your Billing Profile and the information in our billing system.” The amount is not stated.

Author experienceWorkers +10

How I keep Cloudflare under $5: where surprise bills come from

Ashish Sharma (@sarmaasis) runs several sites on the $5 Workers Paid plan and lists, product by product, the usage patterns he says quietly run up a Cloudflare bill, ending with a 12-item checklist.

Other

sylwair: nearly $900 of usage in under two days after a project mistake.

@sylwair says a recent project mistake ran up nearly $900 in less than two days. He says he spotted it in Cloudflare's billable-usage view and stopped the abnormal service, and in a reply adds that the daily billing figures appeared with a delay, so the amount did not visibly drop after he stopped it.

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.