Source-linked reports: Amounts and outcomes come from the original reports and linked replies.
burak emre: an agent loop on sandboxes, a $1,000 bill, and support said to pay.
burak emre (@bu7emba) says his agent got into an infinite loop using the AI binding with sandboxes, and within an hour the bill reached about a thousand dollars because new sandboxes spin up fast with no way to rate limit. He says support called it his fault, and later that they had to pay the bill.
What happened
- Reported cause
- Unbounded loop
- Incident date
- Date not recorded
- First reported
- 2026-01-29 18:26 UTC
- Billing outcome
- Request declinedAuthor-reported
- Case progress
- ResolvedAuthor-reported
- Public Cloudflare reply
- Not linked
Latest reported outcome
The author says support said it was his fault for using an agent, and in August that Cloudflare made them pay the bill while telling them spending limits were coming.
View this update in the timelineOriginal sources
Each entry links to the report or reply it describes.
Case timeline
Author warns about agent bills
Read on 𝕏Replying to Cloudflare, the author writes: “Wait until you have thousand dollar bill because you can’t rate limit your agent with Cloudflare.”
burak emre
@bu7emba · Original 𝕏 post
@Cloudflare Wait until you have thousand dollar bill because you can’t rate limit your agent with Cloudflare
Author describes the loop
Read on 𝕏The author says his agent got into an infinite loop using the AI binding with sandboxes; he stopped after an hour with about a thousand dollars billed, and support said it was his fault to use an agent.
burak emre
@bu7emba · Original 𝕏 post
I had this first hand experience. My agent got in an infinite loop to use AI binding with sandbox. I stopped after an hour and got a thousand dollar bill already because Cloudflare is very scalable an fast to spin up new sandboxes but have no way to apply rate limiting. Support said it was my fault to use agent, hope that doesn’t happen to you!
Author says they had to pay
Read on 𝕏Replying to Justin Schroeder’s $8,846 report, the author says they were in the same situation, argued there were no spending limits, and were told limits were coming but they had to pay because it was their fault.
burak emre
@bu7emba · Original 𝕏 post
@jpschroeder I hope they resolve your issue and cancel the bill! We were exactly in the same situation and they made us pay the bill. I argued that there is no spending limits but they told it's coming but we have to pay the bill because it's our fault.
Author moves off Cloudflare
Read on 𝕏The author writes that it was their fault but it made him stop using Cloudflare products and move to Kubernetes, keeping Cloudflare only as a CDN.
burak emre
@bu7emba · Original 𝕏 post
@jpschroeder Yeah it’s our fault but that made me stop using all the Cloudflare products and move out to Kubernetes. It’s just my CDN now :(
More to read
mcwangcn reports $1,300 in D1 charges after a bot attack.
@mcwangcn says D1 writes previously cost over a thousand dollars and separately mentions Workers CPU charges without giving an amount. He later shares a Cloudflare bill and says $1,300 of its $3,600 came from D1 after a bot attack.
Cloudflare Medivh: a self-hosted near-real-time bill estimator
An open-source, self-hosted monitor that adds today’s estimated usage cost to Cloudflare’s daily-updated billable usage, sends summaries, and calls a webhook when the current cycle crosses a budget.
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.