billflare.

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

D1contact-freeicon-d1-full-scan

contact.freeicon: inefficient D1 queries produced about $748 in four days.

Community user contact.freeicon, running a non-profit free icon library on cloudflare-icon.pages.dev, reports unexpected D1 charges of about $748 from April 13–17, 2026 after a LEFT JOIN GROUP BY query scanned about 6.4 million rows on every page request and bot crawling drove about 200 billion reads. The author replaced the query with a pre-computed indexed column and 72-hour KV caching.

What happened

Reported cause
Read volume
Incident date
2026-04-13
First reported
2026-04-20
Billing outcome
Not recorded
Case progress
Not established
Public Cloudflare reply
Not linked

Latest reported outcome

The author reports deploying query and cache fixes; no refund or credit is stated.

View this update in the timeline

Original sources

Each entry links to the report or reply it describes.

Case timeline

  1. Author reports ~$748 D1 full-scan spike

    Open original source

    The author reports about $748 of D1 charges over April 13–17 from full-table scans amplified by bot crawls, and describes index plus KV fixes.

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.

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.

Other

sylwair: nearly $900 of usage in under two days after a project mistake.

@sylwair says a recent project mistake ran up nearly $900 in less than two days. He says he spotted it in Cloudflare's billable-usage view and stopped the abnormal service, and in a reply adds that the daily billing figures appeared with a delay, so the amount did not visibly drop after he stopped it.