billflare.

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

Workers AIhn-hung-workers-ai-neuron-charges

hung: Workers AI neuron charges billed despite expected free usage.

In a Hacker News comment, hung says that with paid Workers he was billed for confusing Workers AI neuron usage that should have been covered under usage limits, never got an answer on why, and that support ignored his ticket.

What happened

Reported cause
Inference volume
Incident date
Date not recorded
First reported
2026-10-10
Billing outcome
Not recorded
Case progress
Not established
Public Cloudflare reply
Not linked

Latest reported outcome

The author says his support ticket was ignored; no billing action is reported.

View this update in the timeline

Original sources

Each entry links to the report or reply it describes.

Case timeline

  1. Author describes the neuron charges

    Open original source

    The author says he was billed for neuron usage he expected to be covered and that his ticket was ignored.

Durable Objects

babynarc: a Durable Objects alarm loop and a surprise bill that grew from $300 to $500.

@babynarc says an alarm loop in an old Durable Object he thought was inactive left him badly burned: he watched a surprise $300 bill grow to $500 even after killing it. Replying to Cloudflare's Dane Knecht and Kenton Varda, he suggests prepending budget-alert details to every `cf` result by default.

Official docsAI Gateway +1

AI Gateway spend limits

Cloudflare documents cost-based budgets on an AI Gateway that block requests, or fall back to a cheaper model, once cumulative spend in a time window reaches the limit.

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.