workerfuse blog
Notes on runaway Cloudflare bills
How Workers, Durable Objects, D1, KV, R2, Queues and Workers AI run up a bill, and how to stop them before they do.
- Spend limits
- Case studies
- Durable Objects
- D1
- KV
- R2
- Workers AI
- Queues
- Incident response
- How workerfuse works
Cloudflare spending limits vs pausing one Worker
Cloudflare now has spending limits for Workers and Durable Objects. They're account-wide and block the whole product. Here's how that compares to pausing only the runaway Worker.
Read the post →Cloudflare billing horror stories: four runaway bills from 2026
A $34,895 alarm loop, a $10,811 bill from an abandoned side project, a ~$36,000 queue loop, and $4,586 of D1 writes. What broke, how long it ran, and what Cloudflare did about it.
How a Durable Objects alarm loop runs up your Cloudflare bill
A Durable Object alarm that keeps rescheduling itself racks up requests, storage writes and duration. What that costs at list price, and how to stop it.
How to build a per-Worker spending limit on Cloudflare
Read usage from GraphQL, price it, and deploy a stub version when one script goes over. The rough design, with the parts that bit me.
How a missing index can burn your Cloudflare D1 read quota
D1 bills and limits by rows read, not queries. A full table scan on every request adds up fast. Some math, and how to catch it.
Workers KV write pricing: what a write on every request costs
KV writes cost $5 per million. A write on every request is easy to ship by accident and adds up to real money.
R2 ListObjects pricing: what listing on every request costs
R2 egress is free, so people stop thinking about R2 cost. ListObjects is a Class A operation at $4.50 per million.
Workers AI runaway bills: how agent loops and retries add up
Workers AI bills in neurons. An agent loop or a retry that re-runs inference can spend more in an hour than your traffic does in a month.
Cloudflare Queues retry costs: the work your consumer repeats
Queues bill $0.40 per million operations. The real cost of a retry storm is the work your consumer redoes on every attempt.
How to stop a Cloudflare Worker fast without deleting it
Deleting a Worker with Durable Objects can delete their data. Deploy a stub to stop new work and keep the storage. Rollback restores the code, not consumed alarms or terminated Workflows.
Why workerfuse ignores Cloudflare's included usage
We use list prices and ignore included allowances so a runaway trips earlier. The estimate isn't your invoice, and here's why it's built that way.
We measured a Durable Object alarm loop. The analytics undercounted it by ~4x
On a test DO with a 1-second alarm loop, analytics reported about a quarter of the real alarm runs and row writes, and the loop took 5 minutes to stop.
Pause the runaway Worker. Keep the rest running.
workerfuse checks your Cloudflare spend every five minutes and pauses any Worker over its limit.