Workers · Product category
Browse cases and guides explicitly labeled Workers.
29 matching items
Cases · 7
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. He later says his support ticket keeps being refused.
Reported amount · USD
$816.52
Queues: a $248.09 invoice disputed after charges rose without a usage change.
Cloudflare Community user ValentinS disputes a $248.09 Cloudflare Queues invoice dated September 9, 2026. The author says usage stayed consistent while charges rose sharply from a previous $146.08 invoice, without notice of a pricing change, and requests a waiver or credit.
Reported amount · USD
$248.09
Jovan Jester: a recursive image-processing Worker and about $2.2k in charges.
Jovan Jester (@JovanJester), a solo developer, asks CloudflareHelp and CloudflareDev for help with a surprise bill from an accidental recursive loop in an image-processing Worker. Weeks later he says the bug left about $2.2k in charges and asks for tips on getting a credit or a deferred payment plan, worried his domains and DNS could be shut down over the unpaid charges.
Reported amount · USD
$2,200
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
Paweł Mioduszewski: an R2-event queue loop, a $302 charge and a reported $284 account credit.
Paweł Mioduszewski (@mioduszewsky) says buggy Worker code created an infinite loop on an "R2-object-created" queue, with the consumer saving files back into the same bucket. He first estimated at least $343 across Workers, Image Transformations and Queues, then says Cloudflare charged him $302 while his support case waited. About three weeks after contacting support, he reports no cash refund but a $284 account credit that basically wiped the Image Transformations charges.
Reported amount · USD
$302
RetainDB: a reported $36k bill from a queue loop with 81 users.
Reddit user alameenswe, building RetainDB on Workers, KV, Durable Objects and Queues, reports a Cloudflare bill of about $36k for one month with 81 users; the post body says $35,000. He attributes it to a queue consumer that re-queued async writes, 12 unbatched Durable Object writes per memory write and a kv.list() authentication fallback.
Reported amount · USD
$36,000
per month
Guides · 22
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.
Put the spending ceiling into AI-generated code
Prasenjit Sarkar (@stretchcloud) uses the Durable Objects alarm loop to argue that alarms bill without traffic, that a single console cap cannot cover multi-vendor agent work, and that generated code needs execution quotas, idempotency checks and a kill switch.
Idle projects can still bill: check background tasks and storage
@An_yhl reads @shmily7’s follow-up as a reason to audit abandoned AI projects: check scheduled background work and storage reads and writes, stop what is unused instead of just closing the page, and turn on alerts knowing they will not stop anything.
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.
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.
Introducing on-demand profiling: Cloudflare production examples
Dominik Picheta introduces on-demand CPU and memory profiling for Workers and Durable Objects, sharing Cloudflare examples of removing duplicate work and unnecessary allocation paths.
A prompt to set up Cloudflare budget and usage alerts
Merill Fernando (@merill) shares a prompt that asks a coding agent to install Cloudflare’s CLI, check for a billing budget alert and add usage alerts based on last month’s usage, and lists what it set up for him.
Lanshu: an AI-assisted Cloudflare billing risk checklist
Lanshu (@LufzzLiz) shares a six-step prompt for checking account ownership, usage, runaway consumption and budget alerts. Replies add alarm logging, email delivery checks and separate notifications.
After a $10,000 loop bill: budget alerts and a cost-audit prompt for vibe-coded projects
铁柱AGI (@cgnot996) writes an X article that walks through creating a Cloudflare budget alert, explains why it is only a notice, lists cost-amplifying code patterns, and gives a read-only audit prompt and steps for when a bill has already spiked.
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.
Cloudflare billing pitfalls thread
The author organizes Cloudflare billing risks by product and shares experience with budget alert emails.
Watch D1’s daily row quotas while testing
Michal Raczka (@michalraczka) warns that D1’s daily row read and write quotas can stop all D1 queries until midnight UTC, notes that indexes trade reads for extra writes, and moves heavy tests to local Miniflare.
cf-usage-guard
An open-source library that reads account usage from the Cloudflare GraphQL API and circuit-breaks individual Worker bindings before overages.
cloudflare-cost-guard
Louis Cai’s open-source rules and TypeScript base class for keeping Durable Object alarms and Worker schedulers from runaway loops.
Cloudflare cost playbook
A community playbook for Cloudflare cost retrospectives, cost models, and code review.
Optimize costs
Cloudflare lists ways to find and reduce usage-based charges by product.
Production profiling for Workers and Durable Objects: operation guide
Cloudflare explains how to locate expensive functions and memory allocations in deployed Workers and Durable Objects using on-demand profiles and flamegraphs.
D1 billing incident and circuit breakers
Nathan Schram describes D1 write risks and circuit-breaker approaches.
Cloudflare Medivh: a self-hosted near-real-time bill estimator
An open-source, self-hosted monitor that adds today’s estimated usage cost to Cloudflare’s daily-updated billable usage, sends summaries, and calls a webhook when the current cycle crosses a budget.
Overmind: a macOS menu bar meter for Cloudflare usage and bill
An open-source macOS menu bar app that reads a Cloudflare account’s Workers and D1 usage and bill with a read-only token and warns before a free-tier limit runs out.
A usage circuit breaker for Cloudflare Workers
Yingjie Zhao describes a self-facing circuit breaker that pauses cron jobs on his Workers-based news aggregator as monthly usage nears plan allowances.