Source-linked reports: Amounts and outcomes come from the original reports and linked replies.
A software defect drove a Durable Objects usage spike and a $3,800+ invoice; support declined a refund under standard policy.
Cloudflare Community user dev.in1 says a one-time software defect in their application sharply increased Durable Objects usage, mainly Storage Rows Written and Requests, producing an invoice of more than $3,800 for the September 2026 billing period. The author says the issue was identified, fixed and redeployed, with monitoring and alerts added. They report that support confirmed the usage was metered but said usage-based charges are not refundable under the standard policy, and they ask for escalation for a one-time courtesy adjustment.
What happened
- Reported cause
- Write volume
- Incident date
- Date not recorded
- First reported
- 2026-09-29
- Billing outcome
- Request declinedAuthor-reported
- Case progress
- Not established
- Public Cloudflare reply
- Not linked
Latest reported outcome
The author reports that Cloudflare Support said usage-based charges are not refundable under the standard policy; the author is still asking for escalation and a one-time courtesy adjustment.
View this update in the timelineOriginal sources
Each entry links to the report or reply it describes.
Case timeline
Author reports the spike and the support reply
Open original sourceThe author says a one-time defect raised Durable Objects Storage Rows Written and Requests, with an invoice of more than $3,800 for the September 2026 billing period, and that support declined a refund under the standard policy.
More to read
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.
babynarc: a Durable Objects alarm loop and a surprise bill that grew from $300 to $500.
@babynarc says an alarm loop in an old Durable Object he thought was inactive left him badly burned: he watched a surprise $300 bill grow to $500 even after killing it. Replying to Cloudflare's Dane Knecht and Kenton Varda, he suggests prepending budget-alert details to every `cf` result by default.
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.