Vibe-Coded Infinite Loop in Cloudflare Durable Object Triggers $10k Bill with No Refund
A developer's 'vibe-coded' logic caused a Cloudflare Durable Object to enter an infinite self-rescheduling loop, generating 6 trillion read/write operations and a $10,811.41 bill. Due to the lack of hard spending caps and rigid support processes, the user paid in full and is migrating to self-hosted VPS. This incident highlights the financial risks of serverless architectures without strict quota protections and the quality pitfalls of AI-assisted coding.
Related Entities
Full Report
Hit by a Cloudflare bill assassin: a $10k bill. The cause was a Durable Object alarm in an infinite loop in one project, which did 6 trillion reads and writes. Vibe coding failed me.
Update from the author:
- Paid the full Cloudflare bill (US$10,811.41) — “the second most expensive lesson of my life”.
- The support ticket for a reduction only got bot replies in a loop.
- Cloudflare staff contacted on X and other channels said they could only “take a look”, nothing more.
- All projects will move off Cloudflare to self-hosted VPS.
Conclusion: One vibe-coded Durable Object alarm kept rescheduling itself forever. Cloudflare has no hard spending limit, so the loop ran until the invoice came. Not refunded — the author paid in full.
tldr: An infinite loop in a Durable Object alarm did 6 trillion reads/writes and caused a $10,811.41 Cloudflare bill that was not refunded.