Source-linked reports: Amounts and outcomes come from the original reports and linked replies.
3dot: $50 of credit bought instead of $5.
3dot (@3dot_champ) tells @Cloudflare that he accidentally purchased $50 of credit instead of $5 and has been unable to reach Cloudflare. The post is a reply in a thread that also tags two other accounts.
What happened
- Reported cause
- Unknown
- Incident date
- Date not recorded
- First reported
- 2026-09-19 00:04 UTC
- Billing outcome
- Not recorded
- Case progress
- Not established
- Public Cloudflare reply
- Not linked
Latest reported outcome
The author says he has been trying to reach Cloudflare without success; no request outcome is reported.
View this update in the timelineOriginal sources
Each entry links to the report or reply it describes.
Case timeline
Author reports the charge
Read on 𝕏Addressing @Cloudflare, the author writes that he accidentally purchased a credit of $50 instead of $5 and has not been able to reach Cloudflare.
3dot 「☄️G☄️」
@3dot_champ · Original 𝕏 post
@Cloudflare @CompleteSkeptic @typesafeai Good morning @Cloudflare I accidentally purchased a credit of $50 instead of $5 but since then I've been trying to find a way to reach you via Gmail and I couldn't
More to read
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.
Lion Brain: a Durable Object alarm loop from an AI-coding bug wrote about 250 million rows, roughly $210.
Replying in another user's Community thread, bennygoldstein says a bug written by an AI coding tool made a Durable Object alarm in their Lion Brain app re-index the same data every few seconds on October 10 and 11, 2026, writing about 250 million rows and costing roughly $210 in overage on Workers Paid. He says he only found out from the budget alert email, which never pauses anything, and that he opened a billing case asking for a one-time courtesy credit and a real hard spending cap.
Refunds are not a safety net: install your own brakes on cloud bills
SagaSu (@sujingshen) writes a loss-control guide for indie developers: usage-billed code can burn money with zero users, refunds should be planned as zero, and budget alerts are not brakes; it lists five things to set up beforehand and what to do once a bill has already spiked.