Source-linked reports: Amounts and outcomes come from the original reports and linked replies.
A $2,457.90 Workers AI bill for Gemma led to a pricing dispute.
Community user sergiopietro says Workers AI charged $2,457.90 for gemma-4-26b-a4b-it usage: the model page advertises $0.10 per million input tokens, but the invoice bills 223.44 million Neurons at $0.011 per thousand. A billing dispute ticket opened April 10, 2026 had no response after 13 days and the account received a cancellation notice for April 27.
What happened
- Reported cause
- Inference volume
- Incident date
- Date not recorded
- First reported
- 2026-04-23
- Billing outcome
- Request submittedAuthor-reported
- Case progress
- Not established
- Public Cloudflare reply
- Not linked
Latest reported outcome
The author says a billing dispute ticket opened on April 10 had no response after 13 days and the account received a cancellation notice for April 27.
View this update in the timelineOriginal sources
Each entry links to the report or reply it describes.
Case timeline
Author disputes the bill
Open original sourceThe author reports $2,457.90 for Gemma inference and disputes the pricing.
More to read
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.
A simulation game, a reported $4,483.74 in Durable Object reads.
Jonathan Mann (@songadaymann) reports spending $4,483.74 on Durable Object reads while building a simulation game. Rita Kozlov replies, “let us see what we can do”; Mann thanks her, and she replies that she is DMing him for details.
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.