billflare.

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

D1matthieu-d1-llm-agent-writes

An LLM agent wrote about 5 billion rows to D1, a $5,864.11 invoice.

Community user matthieu.marielouise says that between mid-May and mid-June 2026 an LLM coding agent shipped a change that rewrote the same data every few minutes, producing about 5 billion D1 writes and a $5,864.11 invoice on an account with a baseline of about $5 a month. He says billing alerts and budget thresholds did not fire in time and the alert emails landed in spam, and that a billing ticket filed June 11 requests a courtesy credit. About two weeks later he reports no answer and says a lawyer told him the debit breached PSD2 Article 64 consent rules.

What happened

Reported cause
Write volume
Incident date
Date not recorded
First reported
2026-06-16
Billing outcome
Request submittedAuthor-reported
Case progress
Not established
Public Cloudflare reply
Not linked

Latest reported outcome

The author says a billing ticket filed on June 11 requests a courtesy credit and had no answer after almost a month.

View this update in the timeline

Original sources

Each entry links to the report or reply it describes.

Case timeline

  1. Author reports the D1 invoice

    Open original source

    The author reports about 5 billion writes from an LLM agent and a $5,864.11 invoice, and asks for a review.

  2. No answer; lawyer involved

    Open original source

    The author says there has been almost a month without an answer, argues for a spending cap and says a lawyer told him the debit breached PSD2 Article 64 consent rules.

Durable Objects

shmily7: a Durable Object alarm loop and a reported US$10,811.41 bill.

@shmily7 reports a Durable Object alarm loop in an unused test project, then says he paid the full US$10,811.41 bill to avoid service suspension. Cloudflare’s Ashley Peacock publicly says he is looking into it internally and will follow up. Cloudflare’s Dane Knecht later replies that he escalated it too. On October 9 the author declares the case closed: he reports that, with Ashley Peacock’s help, Cloudflare decided to refund the charges incurred during the bug in full, with the money still to arrive, and posts the support ticket reply he received.

Community resourceWorkers +3

Cloudflare Cost Guard: a read-only agent skill for runaway-billing audits

Layer Cache’s open-source agent skill, announced by Domenico (@purposelyblnk), audits a Cloudflare codebase from source alone for paths that can run up uncontrolled billable usage, and reports findings without changing code or calling Cloudflare.

Author experienceAccount-wide usage-based products +1

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.