Cloudflare shock bills: refunds are a lottery, developers must install their own brakes
sujingshen · x · 2026-10-19
A deep-dive by Sagasu on runaway cloud bills, sparked by developer shmily7's $10,811.41 Cloudflare bill: an unused AI-written test project whose Durable Objects alarm callback re-scheduled itself 600 times per second.
Key findings
- Bills without users: per-call pricing only cares how often code runs. Billflare's Durable Objects collection logs 13 incidents totaling $66,897.60, the largest at $34,895 (20 trillion reads)
- Refunds are a lottery: outcomes range from near-full refunds to flat rejections; successful cases almost always went viral on X. Refunds often come as account credit, bills keep accruing after shutdown, and platforms can demand payment under threat of suspension
- Budget alerts don't stop anything: alerts only email you — one Google Cloud user with a $10 alert got billed $1,300. Cloudflare still lacks a hard spend cap as of Oct 2026; mitigate via lower per-invocation CPU limits and separate AI Gateway spend caps
Conclusion: assume refunds are $0 in your risk planning; only pre-configured brakes protect you.
More from coding & agent
- Monid ranks agent tools by real usage: TinyFish leads with 754K weekly transactions — HeyAmit_ · 2026-10-23
- Claude cut a 2.6-hour video export to 20 minutes — but only after being told to rebuild the server — byhewar · 2026-10-23
- OpenJet claims Qwen3.8-27B coding runs 1.9x faster than llama.cpp on one RTX 3090 — JeremyCMorgan · 2026-10-23
- Building an autonomous SEO agent in Hermes with three skills: programmatic pages, Keywords Everywhere, DataForSEO — EXM7777 · 2026-10-23
- Building a sports betting AI agent with onchain execution and human approval by default: architecture and lessons — Dry-Comfortable-2678 · 2026-10-23
- Capy 0.5.0 lets Claude Pro/Max subscribers reuse their plan quota, adds OIDC cloud access — garrytan · 2026-10-23