billflare.

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

D1user1234567-d1-bot-traffic-row-reads

user1234567 (colorlabs.net): a bot attack and 1.9 trillion D1 row reads led to a huge bill.

Community user user1234567 (colorlabs.net) says a bot attack, with no-referrer requests, fake user agents and over 100,000 visits from Singapore, got through the Cloudflare proxy despite Bot Fight Mode and produced a huge D1 bill: about 500,000 requests reportedly generated 1.9 trillion D1 row reads. The author contacted support on January 8 when the bill was generated, disputes it under case 01919383, deleted the database, Worker and Pages site, and says the R2 and Workers subscriptions were then cancelled, taking the sites down. No amount is stated.

What happened

Reported cause
Traffic spike
Incident date
Date not recorded
First reported
2026-01-13
Billing outcome
Request submittedAuthor-reported
Case progress
Not established
Public Cloudflare reply
Not linked

Latest reported outcome

The author disputes the bill under case 01919383 and says support has not replied; no outcome is reported.

View this update in the timeline

Original sources

Each entry links to the report or reply it describes.

Case timeline

  1. Author disputes a huge D1 bill after a bot attack

    Open original source

    The author says about 500,000 bot requests produced 1.9 trillion D1 row reads, the dispute under case 01919383 has no reply, and subscriptions were cancelled.

Author experienceD1 +1

Moving a blog to EmDash on the D1 free tier: row reads ran out and the author rolled back twice

tozai (@ccietry_tozai) tried moving a WordPress blog with about 800 daily unique visitors and 7,000 page views to EmDash on Cloudflare, exceeded D1’s 5 million daily rows-read free limit, and went back to WordPress rather than move to a paid plan without a hard cap.

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.

Author experienceWorkers +10

How I keep Cloudflare under $5: where surprise bills come from

Ashish Sharma (@sarmaasis) runs several sites on the $5 Workers Paid plan and lists, product by product, the usage patterns he says quietly run up a Cloudflare bill, ending with a 12-item checklist.