# Cloudflare billing horror stories: four runaway bills from 2026 · workerfuse

These are four public reports of runaway Cloudflare bills from 2026. The amounts are what the authors posted. I have not seen their invoices. Each story links to the original post.

## $34,895 in 8 days, zero users

A [pre-launch founder posted on Hacker News](https://news.ycombinator.com/item?id=47787042) in April. A Durable Object agent called `setAlarm()` in `onStart()` on every wake-up. It never checked for an alarm that was already set. More than 60 preview deployments each made their own objects, and each one ran the loop.

The loop started on April 3. It peaked at about 930 billion rows read per day. The author found it on April 11. The invoice was $34,895, and billing had not replied when the author posted. The fix was to call `getAlarm()` first and set a new alarm only if none exists.

## $10,811 from a project nobody used

[A developer on X](https://x.com/shmily7/status/2107481028726251762) had stopped work on an experiment, but it was still deployed. A bug from an AI coding session sat quiet for 23 days. Then a checkpoint entered its refresh window, and `alarm()` started to reschedule itself to `Date.now()`. Cloudflare support later put that at about 600 runs per second. Most of the cost was SQLite rows read and written, not duration.

The bill was $10,811.41. The only alert was the default $10 budget alert. Support first refused a credit because the usage came from the customer's code. The author paid in full with a temporary credit-limit increase. After a Cloudflare employee stepped in, [support refunded $10,701.41](https://x.com/shmily7/status/2108493941003972778). Their advice: never pass `Date.now()` or a past time to `setAlarm()`, and keep a retry budget in storage. Our [alarm loop post](/blog/durable-objects-alarm-loop) covers the same guards.

## ~$36,000 for 81 users

The founder of RetainDB, a memory service for AI agents, [posted on r/CloudFlare](https://www.reddit.com/r/CloudFlare/comments/1t1e8nh/i_accidentally_generated_16_billion_durable/) about a one-month bill of about $36,000. The itemized lines were 3.13 billion KV writes ($15,635), 16.62 billion KV reads ($8,306), 4.01 billion Durable Object rows written ($3,962) and 574 million KV list calls ($2,870).

The post named three bugs that multiplied each other:

*   The queue consumer called the API with the original async flag. So the API queued the same job again, five to ten times per write.
*   Each memory write did twelve unbatched `storage.put()` calls.
*   Old API keys had no index, so 95% of requests fell back to a full `kv.list()` scan.

In a later update, the author said most of the traffic was bots. A rate limiter had been written but never wired in. The figures in the post do not fully add up, and it does not say whether Cloudflare gave a credit. See our [KV write](/blog/workers-kv-write-cost) and [Queues retry](/blog/cloudflare-queues-retry-cost) posts for the math.

## $4,586 of D1 writes on a $5 plan

[A solo developer at Little Bear Apps](https://littlebearapps.com/blog/d1-billing-disaster-circuit-breakers/) had two D1 bugs in January. A data harvester re-inserted rows with no `ON CONFLICT` clause. An embedding Worker on a cron processed the same batch on every run because it did not track an offset. Together they wrote 4.83 billion rows. The peak was 1.42 billion in one day. Normal use was about 200 writes per hour.

The invoice was $4,586.64. Cloudflare waived all of it, but it took 18 days and four channels: a ticket, the community forum, an email to the head of billing and a Reddit post. While the case was on hold, the automated billing system sent a suspension warning, and R2 and Analytics Engine were turned off.

## What they have in common

*   None came from real user growth. Each came from a loop in the app's own code, from bots, or from an app nobody used.
*   The loops ran for days. No alert stopped any of them.
*   The fix was small every time: an alarm check, a minimum delay, an upsert, an offset, a sync flag.
*   Refunds happen, but by escalation, not by policy. Two of the four got money back after public posts and help from Cloudflare staff.

Cloudflare has since shipped [spending limits](/blog/cloudflare-spending-limit) for Workers and Durable Objects. They are monthly and account-wide, and they do not cover KV or D1, which drove two of these bills.

workerfuse checks spend every five minutes. When one Worker goes over its hourly or daily limit, it pauses that Worker and leaves the rest running. It prices Durable Objects, D1, KV, R2, Queues and Workers AI. It is a safety net, not a billing cap: a pause takes minutes, and those minutes still cost money. But minutes is a lot less than eight days. [Start a free trial](/signup).

## Pause the runaway Worker. Keep the rest running.

workerfuse checks your Cloudflare spend every five minutes and pauses any Worker over its limit.

[Start free trial](/signup)

## Keep reading

[

Spend limitsNovember 13, 2026

### 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.

](/blog/cloudflare-spending-limit)[

Durable ObjectsNovember 13, 2026

### 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.

](/blog/durable-objects-alarm-loop)[

Spend limitsNovember 13, 2026

### 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.

](/blog/per-worker-spending-limit)
