Source-linked reports: Amounts and outcomes come from the original reports and linked replies.
A loop in a staging environment produced a $383.12 Durable Objects charge.
Community user cyjun003, a small self-funded startup, says an infinite loop in their staging environment ran up more than 700 million Durable Object reads and a $383.12 bill. They patched it, added usage alerts and ask for a one-time courtesy credit through an existing support ticket.
What happened
- Reported cause
- Unbounded loop
- Incident date
- Date not recorded
- First reported
- 2026-02-27
- Billing outcome
- Request submittedAuthor-reported
- Case progress
- Not established
- Public Cloudflare reply
- Not linked
Latest reported outcome
The author asks for a one-time courtesy credit through an existing support ticket.
View this update in the timelineOriginal sources
Each entry links to the report or reply it describes.
Case timeline
Author asks for a credit
Open original sourceThe author reports $383.12 from a staging loop and asks for a courtesy credit.
More to read
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.
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.
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.