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

D1sven-guettner-d1-full-table-reads

Sven Guettner: a D1 bug produced a $1,868 bill from about 1.89 trillion row reads.

Sven Guettner says a wrong database setting on offercompass.app made every small update read the whole table in the background between Aug 28 and Sep 22, 2026, totaling about 1.89 trillion rows and a $1,868 D1 bill. He fixed the bug, shut the project down, opened ticket 02338870 asking for a courtesy credit, and reports only AI replies so far.

What happened

Reported cause: Read volume
Incident date: 2026-08-28
First reported: 2026-09-23
Billing outcome: Request submittedAuthor-reported
Case progress: Not established
Public Cloudflare reply: Not linked

Latest reported outcome

The author requests a courtesy credit via ticket 02338870 and says replies look automated; community members say to wait for a human on the ticket.

View this update in the timeline

Original sources

Original Cloudflare Community post

Each entry links to the report or reply it describes.

Case timeline

2026-09-23
Author reports $1,868 D1 bill and AI-only ticket replies
Open original source
The author reports about 1.89 trillion background row reads, a $1,868 bill, a fixed bug, and ticket 02338870 seeking a courtesy credit.

Author experienceAccount-wide usage-based products

A budget alert is a horn, not a brake

@GUYUE_LGY points to Cloudflare’s Budget alerts documentation: alerts send email when spend crosses a threshold but do not pause or cap usage. Before letting AI run unattended, the author checks what actually happens at the line.

Other

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.

Author experienceWorkers +7

Lanshu: an AI-assisted Cloudflare billing risk checklist

Lanshu (@LufzzLiz) shares a six-step prompt for checking account ownership, usage, runaway consumption and budget alerts. Replies add alarm logging, email delivery checks and separate notifications.

Author experienceWorkers +4

The Ultimate Cloudflare Guide: what each piece costs and where it bites

Elia (@eliakuratli), who runs several products on Cloudflare, walks through the developer platform with what each piece costs, what the Workers Paid plan includes, and a short prevention list for the one risk he says can actually hurt: no hard spend cap.

Author experienceWorkers +4

Cloudflare costs $5 a month, but the bill is not capped

不追高 (@Ariella1213) writes an X article explaining that Workers Paid’s $5 is a minimum, that per-product limits and budget alerts do not cap the account bill, and how denial-of-wallet requests, write amplification, delayed stops and background retries add cost.

mcwangcn reports $1,300 in D1 charges after a bot attack.

@mcwangcn says D1 writes previously cost over a thousand dollars and separately mentions Workers CPU charges without giving an amount. He later shares a Cloudflare bill and says $1,300 of its $3,600 came from D1 after a bot attack.