Source-linked reports: Amounts and outcomes come from the original reports and linked replies.
private12: double subscription charges and chargebacks after cancelling.
Community user private12 says a plan bought on July 3 was charged as two subscriptions, and one charge continued after cancelling. Unable to reach a human, the author initiated chargebacks for three charges.
What happened
- Reported cause
- Unknown
- Incident date
- Date not recorded
- First reported
- 2026-09-03
- Billing outcome
- Request submittedAuthor-reported
- Case progress
- Not established
- Public Cloudflare reply
- Not linked
Latest reported outcome
The author reports initiating chargebacks with the bank for the July 3 and August 3 double charges and a September 3 charge after cancellation.
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 the AI support bot would not hand off to a human, billing@ and ar@ emails returned automatic replies, and payment methods cannot be removed. A community MVP links the ticket guide. Amounts are not stated.
More to read
lojabelastock: $22.50 for about 4.07 million R2 Class A ops during development.
Community user lojabelastock reports invoice IN-83391537 for $22.50 covering 4,070,034 R2 Storage Class A Operations during automated development/testing of Bela Stock, asks to cancel the invoice or issue a one-time courtesy credit, and says an autorun routine was removed afterward.
Designing a poker game on Durable Objects so idle time costs nothing
Philip Atkinson describes the architecture of his multiplayer poker game on the Cloudflare Developer Platform and the cost rules he follows: archive finished games out of Durable Object storage, hibernate WebSockets, wake with alarms and treat logging as a cost decision.
A missing index on a D1 DELETE read about 4 trillion rows, a $4,114.97 charge.
Community user user11226 says a missing database index made a DELETE operation repeatedly scan the table, generating about 4.03 trillion D1 rows read in the billing period and an unexpected $4,114.97 bill on what they understood to be a $5-a-month subscription. In follow-ups they accept they should have configured billing alerts, say Cloudflare successfully challenged their chargeback while the urgent billing case took more than three weeks to get a response, and ask for someone to review the circumstances.