Workers, Browser Rendering, and Workers AI billing cases
Browse public reports labeled Workers, Browser Rendering, or Workers AI. Each case page preserves the reported details and source context.
Reported cases
Sitemap polling: the author reports a $100 Cloudflare bill alongside AWS costs.
@enzyme_dev says a refactor made Workers fetch a sitemap every five seconds. In an October 6 reply, he reports a $100 Cloudflare bill and an AWS bill above $800 for the previous week.
Reported amount · USD
$100
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.
Reported amount · USD
$816.52
Jason Silberman: an approximately $1,000 AI-billing dispute, later reported resolved.
@_jasonsilberman reports an invoice around $1,000 with AI usage rows he says were duplicated and already prepaid. Cloudflare personnel reply, including Matthew Prince, who says the case was escalated. The author later says the issue was resolved.
Reported amount · USD
$1,000
Workers and Queues: an author reports a jump from $5 to $2,145.
@goteap reports that a code loop generated over two billion internal requests and raised an invoice from $5 to $2,145. The author says a refund was not possible.
Reported amount · USD
$2,145
Browser Rendering: an $80 report and a later correction about usage.
@loftwah initially says Browser Rendering charged $80 for services he never used, then clarifies that he had not realized he was using them. A later post says the billing issue remained unresolved.
Reported amount · USD
$80
Related billing guides
Cloudflare billing pitfalls thread
The author organizes Cloudflare billing risks by product and shares experience with budget alert emails.
Budget alerts
Cloudflare documents account-wide spend alerts and their notification limits.
Cloudflare cost playbook
A community playbook for Cloudflare cost retrospectives, cost models, and code review.
D1 billing incident and circuit breakers
Nathan Schram describes D1 write risks and circuit-breaker approaches.