Source-linked reports: Amounts and outcomes come from the original reports and linked replies.
Paweł Mioduszewski: an R2-event queue loop, a $302 charge and a reported $284 account credit.
Paweł Mioduszewski (@mioduszewsky) says buggy Worker code created an infinite loop on an "R2-object-created" queue, with the consumer saving files back into the same bucket. He first estimated at least $343 across Workers, Image Transformations and Queues, then says Cloudflare charged him $302 while his support case waited. About three weeks after contacting support, he reports no cash refund but a $284 account credit that basically wiped the Image Transformations charges.
What happened
- Reported cause
- Unbounded loop
- Incident date
- Date not recorded
- First reported
- 2025-11-12 20:43 UTC
- Billing outcome
- Credit issuedAuthor-reported
- Case progress
- Not established
- Public Cloudflare reply
- Not linked
Latest reported outcome
The author reports that Cloudflare support replied after about three weeks with no cash refund but a $284 account credit that basically wiped the Image Transformations charges. He had been charged $302.
View this update in the timelineOriginal sources
- Original runaway-loop report
- Author's follow-up on usage checks
- Author reports the $302 charge
- Author reports a $284 account credit
Each entry links to the report or reply it describes.
Case timeline
Queue loop and a bill estimate of at least $343
Read on 𝕏The author says he deployed buggy Worker code and woke up to millions of unintended executions from an infinite loop on an "R2-object-created" queue whose consumer saved files to the same bucket. He estimates at least $343 from Workers, Image Transformations and Queues, and says he asked Cloudflare support to cancel or reduce the incident costs.
Paweł Mioduszewski
@mioduszewsky · Original 𝕏 post
Fckd up my Cloudflare Worker last Friday, deployed buggy code and go to sleep. Woke up to millions of unintended executions—classic nightmare I always feared. Infinity loop of "R2-object-created" queue - consumer was saving files to the same R2 bucket processing same files over… pic.twitter.com/fDVlExOzno
Author builds a usage monitor
Read on 𝕏Calling the runaway his own mistake, the author says he now checks usage repeatedly and is building a tool to alert him and trigger a kill switch. He says the Billable Usage page shows partial metrics without prices.
Paweł Mioduszewski
@mioduszewsky · Original 𝕏 post
After that runaway on @Cloudflare last week, (totally my stupid mistake, deployed buggy code and went to sleep) I've got straight-up PTSD before every night -checking usage like 20x. Can't live like this forever. So I'm building "Parachute" : it'll alert me and even flip the… pic.twitter.com/V1QvOjAhZA
$302 charged while support waits
Read on 𝕏The author says support had not replied for 15 days and Cloudflare charged him $302 anyway, below the $343 he had estimated. He gives support case 01827556 and says he will update if they respond.
Paweł Mioduszewski
@mioduszewsky · Original 𝕏 post
So that's what I thought. @Cloudflare support is like sending message into the void—15 days waiting, crickets. They charged me $302 anyway, now my bank account is negative, my perfect end-of-year achievement 👏👏👏 /s. Screwed in debt rn but hey, could be worse, at least it's not… https://t.co/nZ6dkpI2v0 pic.twitter.com/H8S0rr2Mos
Author reports a $284 account credit
Read on 𝕏The author says Cloudflare replied after about three weeks: no cash refund, but a $284 account credit that basically wiped the Image Transformations charges. He calls it a huge relief and thanks Cloudflare, adding that support was slow.
Paweł Mioduszewski
@mioduszewsky · Original 𝕏 post
UPDATE:@Cloudflare finally replied after ~3 weeks 😅 No cash refund, but they gave me $284 account credit - basically wiped the Image Transformations charges. Huge relief. Support is slow as hell, but they came through (to be fair my case was low priority). Thank you! CF… https://t.co/lPotmo1pHH
More to read
Put the spending ceiling into AI-generated code
Prasenjit Sarkar (@stretchcloud) uses the Durable Objects alarm loop to argue that alarms bill without traffic, that a single console cap cannot cover multi-vendor agent work, and that generated code needs execution quotas, idempotency checks and a kill switch.
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.
hfcorriez: $100+ of AI-driven extra usage over two months, reported cancelled after emails.
@hfcorriez says AI caused over $100 of extra consumption over two months. He says that after two rounds of email explaining the situation to Cloudflare, the charges were cancelled, and posts a screenshot of two negative line items (-$31.92 and -$75.42) marked Fully Applied.