Source-linked reports: Amounts and outcomes come from the original reports and linked replies.
zenuos.official: a double charge credited, and a request for a card refund.
Community user zenuos.official says a double charge was answered with a full credit note (IN-71807614-CN-01) and asks for the money to be refunded to the card instead, citing invoice IN-71807753 and $50.85.
What happened
- Reported cause
- Unknown
- Incident date
- Date not recorded
- First reported
- 2026-07-16
- Billing outcome
- Credit issuedAuthor-reported
- Case progress
- Not established
- Public Cloudflare reply
- Not linked
Latest reported outcome
The author reports a full credit note for the double charge and asks for a refund to the card; no reply is recorded.
View this update in the timelineOriginal sources
Each entry links to the report or reply it describes.
Case timeline
Author reports the disputed charge
Open original sourceThe author says a ticket for the refund could not be created.
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.
sylwair: nearly $900 of usage in under two days after a project mistake.
@sylwair says a recent project mistake ran up nearly $900 in less than two days. He says he spotted it in Cloudflare's billable-usage view and stopped the abnormal service, and in a reply adds that the daily billing figures appeared with a delay, so the amount did not visibly drop after he stopped it.
OpenCils: a $231 D1 charge reported waived after a three-month ticket.
@OpenCils reports emailing Cloudflare on June 24 about a D1 charge. He says billing support forwarded the ticket to billing engineering on August 27, and that Cloudflare later waived the $231 D1 charge as a one-time courtesy and lifted account restrictions.