billflare.

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

R2z-calloway-r2-litestream-listobjects

z.calloway43: Litestream R2 loop produced a $25.19 Class A overage.

Community user z.calloway43 requests a one-time courtesy waiver for unpaid invoice IN-75481816 ($25.19) after an unintended Litestream SQLite backup loop on R2 generated about 9.74 million Class A ListObjects operations from a 10-second sync interval and prefix accumulation. The author stopped Litestream, switched to daily Restic snapshots, and added a fail-closed usage guard.

What happened

Reported cause
Unbounded loop
Incident date
Date not recorded
First reported
2026-08-19
Billing outcome
Request submittedAuthor-reported
Case progress
Not established
Public Cloudflare reply
Not linked

Latest reported outcome

The author requests a one-time courtesy credit and reports difficulty opening a billing ticket; community points to the support case form path.

View this update in the timeline

Original sources

Each entry links to the report or reply it describes.

Case timeline

  1. Author requests courtesy credit for $25.19 Litestream loop

    Open original source

    The author reports about 9.74M R2 Class A ListObjects from a Litestream loop and asks for a courtesy waiver of invoice IN-75481816.

Author experienceWorkers +5

Four layers of cost protection for small Cloudflare projects

David Z (@davezfr) writes an X article for vibe coders on budget alerts, stop conditions for paid paths, automatic pausing, and letting a personal agent verify and pause.

D1

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.

Official docsAccount-wide usage-based products

Budget alerts

Cloudflare documents account-wide spend alerts and their notification limits.