billflare.

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

D1mircea-trofimciuc-d1-agent-count-queries

Mircea Trofimciuc: agent count(*) queries on D1 and a reported $700+ bill.

Mircea Trofimciuc (@MirceaTrofim) reports a $700+ bill after an AI agent ran a few count(*) queries on a large D1 table to get the number of records. He says support won't credit the account and that he was charged, and asks @CloudflareDev for help.

What happened

Reported cause
Read volume
Incident date
Date not recorded
First reported
2026-05-06 15:14 UTC
Billing outcome
Request declinedAuthor-reported
Case progress
Not established
Public Cloudflare reply
Not linked

Latest reported outcome

The author reports that support won't credit the account and that he was charged; he asks @CloudflareDev to help.

View this update in the timeline

Original sources

Each entry links to the report or reply it describes.

Case timeline

  1. Agent queries lead to a $700+ D1 bill

    Read on 𝕏

    Replying to @CloudflareDev, the author says D1 billing is “insane” with agents: an agent ran a few count(*) queries on a big table and he got a $700+ bill. He says support won't credit the account, that he was charged, and that @levelsio had been credited in a similar situation.

    Mircea Trofimciuc

    @MirceaTrofim · Original 𝕏 post

    I don't know about that @Cloudflare (I love the company btw) but the D1 billing is INSANE when using Agents I got hit with $700+ bill because the agent did few count(*) queries on a big table to get the number of records. Now support won't credit that account and I got charged.… pic.twitter.com/aFY3F9Vysg
Workers

A voting page polling every three seconds: the author revises a $1,000 report.

@keking99 first reports about $1,000 for a voting page polling /api/result every three seconds. A later post reports $816.52 in accumulated usage as of October 4 and cites another screenshot total of $817.14. He later says his support ticket keeps being refused.

Author experienceWorkers +1

Removing unneeded Durable Objects from MCP servers on Workers

Justin (@interjc) describes moving read-only MCP servers from McpAgent, which starts a Durable Object per session, to stateless createMcpHandler, and shares a prompt for auditing Workers bindings and runaway usage patterns.

Other

hfcorriez: $100+ of AI-driven extra usage over two months, reported cancelled after emails.

@hfcorriez says AI caused over $100 of extra consumption over two months. He says that after two rounds of email explaining the situation to Cloudflare, the charges were cancelled, and posts a screenshot of two negative line items (-$31.92 and -$75.42) marked Fully Applied.