billflare.

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

Othermeathill-kv-opennext-isr-bloat

Meathill: OpenNext KV ISR cache left unpaid TTL work and ballooned storage.

Meathill reports that an OpenNext Cloudflare KV incremental-cache path for Next.js ISR left a TODO for KV TTL, so versioned page snapshots accumulated. Dashboard billable storage showed 3.59 GB-month over the 1 GB free allowance with ongoing extra charges, and historical zombie data reached about 24 GB before he moved to a new namespace. He does not state a dollar invoice total.

What happened

Reported cause
Write volume
Incident date
Date not recorded
First reported
2026-10-13 09:20 UTC
Billing outcome
Not recorded
Case progress
Not established
Public Cloudflare reply
Not linked

Latest reported outcome

The author deletes the old KV namespace and redesigns incremental caching; no refund or credit is reported. Dollar amount remains unknown.

View this update in the timeline

Original sources

Each entry links to the report or reply it describes.

Case timeline

  1. Author publishes KV ISR storage leak write-up

    Open original source

    The author reports 3.59 GB-month billable KV storage over the free 1 GB tier, about 24 GB of historical zombie data from OpenNext ISR writes without TTL, and a move to a new namespace.

R2

lojabelastock: $22.50 for about 4.07 million R2 Class A ops during development.

Community user lojabelastock reports invoice IN-83391537 for $22.50 covering 4,070,034 R2 Storage Class A Operations during automated development/testing of Bela Stock, asks to cancel the invoice or issue a one-time courtesy credit, and says an autorun routine was removed afterward.

Author experienceDurable Objects +1

Put the spending ceiling into AI-generated code

Prasenjit Sarkar (@stretchcloud) uses the Durable Objects alarm loop to argue that alarms bill without traffic, that a single console cap cannot cover multi-vendor agent work, and that generated code needs execution quotas, idempotency checks and a kill switch.

D1

A 12 MB D1 database, a reported USD 1,966.35 invoice.

@imselmon reports a USD $1,966.35 D1 invoice for a roughly 12 MB database with over two billion row writes. The author says the activity is abnormal and is investigating the database usage.