Usage monitoring · Content tag
Browse cases and guides discussing usage monitoring.
27 matching items
Cases · 6
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.
Reported amount · USD
$900
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.
Reported amount · USD
$1,300
Will Moss: an alarm loop, 20 trillion Durable Object reads and a reported $34,895 invoice.
@itswillmoss reports 20,213,871,155,804 Durable Object reads, a dashboard mismatch and lost project access. He attributes the loop to health checks waking onStart and repeatedly setting an alarm. The X thread estimates the cost above $30,000; a same-day Hacker News post by thewillmoss describing the same alarm loop reports a $34,895 invoice and a support case awaiting a billing response.
Reported amount · USD
$34,895
Steven Menke: an Agents SDK bug and a reported $1,700 Durable Objects invoice.
Steven Menke (@Galorious_) reports that runaway Durable Objects caused by an Agents SDK bug produced a $1,700 invoice in three days, citing one trillion SQLite reads (a later post says writes). He says his support ticket, even after a maintainer escalated it, received no reply for months.
Reported amount · USD
$1,700
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 · 21
Layered defenses after a Durable Object alarm loop
星星之火可以燎原 (@fireandstart) reads a public Durable Object alarm-loop recap and argues for layered defenses rather than relying on being more careful next time.
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.
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.
Why hard spending caps take time: Ashley Peacock on billing latency
Ashley Peacock (@ashleypeacock), who works on Durable Objects at Cloudflare, explains from experience why near-real-time spending caps are hard to build, says hard billing caps are coming soon, and suggests budget alerts plus issue alerts in the meantime.
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.
Billable Usage API
Cloudflare introduces an API that returns a self-serve account’s usage and cost by product and service period, currently updated daily.
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.
D1 pricing and free daily row limits
Cloudflare explains D1 read/write billing, free daily limits, and usage tracking.
Optimize costs
Cloudflare lists ways to find and reduce usage-based charges by product.
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.