Source-linked reports: Amounts and outcomes come from the original reports and linked replies.

Otherpooh10hoop10-duplicate-invoice-failed-payment

pooh10hoop10: a duplicate $10.46 domain invoice after checkout errors.

Community user pooh10hoop10 says checkout for ruamira.com repeatedly showed “A processing error occurred,” so they clicked Complete purchase several times, which generated two identical invoices. The author asks for the duplicate to be voided.

What happened

Reported cause: Unknown
Incident date: Date not recorded
First reported: 2026-07-30
Billing outcome: Request submittedAuthor-reported
Case progress: Not established
Public Cloudflare reply: Not linked

Latest reported outcome

The author asks for the duplicate invoice to be voided. A community MVP links the case page.

View this update in the timeline

Original sources

Original author report

Each entry links to the report or reply it describes.

Case timeline

2026-07-30
Author reports the disputed charge
Open original source
The author says no charge or bank SMS appeared during the errors.

Durable Objects

shmily7: a Durable Object alarm loop and a reported US$10,811.41 bill.

@shmily7 reports a Durable Object alarm loop in an unused test project, then says he paid the full US$10,811.41 bill to avoid service suspension. Cloudflare’s Ashley Peacock publicly says he is looking into it internally and will follow up. Cloudflare’s Dane Knecht later replies that he escalated it too. On October 9 the author declares the case closed: he reports that, with Ashley Peacock’s help, Cloudflare decided to refund the charges incurred during the bug in full, with the money still to arrive, and posts the support ticket reply he received.

Author experienceDurable Objects +2

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.

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.

Workers AI

mamun: disputed Workers AI charges and a downgrade during billing review.

Community user mamun says the team formally disputed unauthorized Workers AI charges, support confirmed a downgrade postponement during the review, and the account was downgraded to Free anyway. The author offers to pay the undisputed $330.46 but says partial payment is not supported.

Containers

forsalebypwner: an exorbitant Workers Containers charge with no usage visibility.

In a Hacker News comment, forsalebypwner says that one month they were charged exorbitantly for Workers Container usage and that there was no way to monitor or track usage until the invoice arrived.

bibhutipd: $9.01 for 644 R2 Infrequent Access operations; support says it will review a goodwill credit.

Community user bibhutipd (trailshorts.xyz) says a $9.01 charge came from 644 R2 Infrequent Access Class A operations rounded up to one million at $9.00 per million, after configuring IA through lifecycle rules without realising IA has no free tier. The author deleted the IA objects, switched to Standard and asks for a one-time goodwill credit. A community MVP replies that the policy is documented, then shares how to open a billing case. The author later says a ticket was created and the Cloudflare team confirmed it would review a one-time goodwill credit once the invoice is created.