Source-linked reports: Amounts and outcomes come from the original reports and linked replies.
Breathy Wind: two failed purchases, charged twice, service not active.
Breathy Wind (@NeedoneApp) says two attempts on May 15 to buy a paid service failed with errors, yet the account was charged twice and the service is not active. The support case had no response yet.
What happened
- Reported cause
- Unknown
- Incident date
- 2026-05-15
- First reported
- 2026-05-22 21:21 UTC
- Billing outcome
- Request submittedAuthor-reported
- Case progress
- Not established
- Public Cloudflare reply
- Not linked
Latest reported outcome
The author asks for urgent review of case 500Nv00000deD50IAE; no 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 𝕏The author says both purchase attempts on May 15 failed with errors but he was charged twice and the service is not active, and asks for an urgent review.
Breathy Wind
@NeedoneApp · Original 𝕏 post
Hi @Cloudflare, I tried to purchase your paid service on May 15, but both attempts failed with errors. I was still charged twice and the service is not active. My support ticket has not received a response yet. Could someone please review this urgently? Case: 500Nv00000deD50IAE
More to read
Jiuhong: a vibe-coded Durable Objects bug, a $600+ overnight bill and a reported 80% account credit.
Replying on X in the shmily7 thread, Jiuhong (@indiehacker9527) says a bug from vibe coding in Durable Objects produced a bill of more than $600 overnight a few months earlier. After several rounds of negotiation stressing system defects, he says 80% was returned as account credit for future charges rather than to his card, that Cloudflare promised product improvements, and that he also received a startup credit package.
Budget alerts
Cloudflare documents account-wide spend alerts and their notification limits.
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.