Billing requests · Content tag
Browse cases and guides discussing billing requests.
11 matching items
Cases · 10
Containers: an author asks Cloudflare to void a $161.11 memory charge.
Hacker News user alexander2002 asks Cloudflare support to void a $161.11 Container Memory charge, saying he usually pays Cloudflare around $30 and this was a sudden jump. He later says he already tried the official support route and X.
Reported amount · USD
$161.11
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.
Reported amount · USD
$10,811.41
D1 status writes: an author reports a 150-dollar charge and refund.
@wofuhuola describes a generated tool writing Reddit post statuses globally every five minutes and deleting expired rows. The author says one month cost 150 dollars, went unnoticed for three months, and was later refunded after an appeal.
Reported amount · USD
$150
per month
Queues: a $248.09 invoice disputed after charges rose without a usage change.
Cloudflare Community user ValentinS disputes a $248.09 Cloudflare Queues invoice dated September 9, 2026. The author says usage stayed consistent while charges rose sharply from a previous $146.08 invoice, without notice of a pricing change, and requests a waiver or credit.
Reported amount · USD
$248.09
D1 migration: the author reports a $911.56 charge after stopping the job.
@m0xandrew says a hobby-project D1 migration reached 8,274% of a budget alert, so he stopped it and requested a one-time waiver. He later reports a $911.56 charge, closure of the old case and opening a new support case.
Reported amount · USD
$911.56
Mircea Trofimciuc: agent count(*) queries on D1 and a reported $700+ bill.
Mircea Trofimciuc (@MirceaTrofim) reports a $700+ bill after an AI agent ran a few count(*) queries on a large D1 table to get the number of records. He says support won't credit the account and that he was charged, and asks @CloudflareDev for help.
Reported amount · USD
$700
Little Bear Apps: a D1 write loop and a reported full US$4,586.64 invoice waiver.
Nathan Schram reports that two bugs wrote 4.83 billion D1 rows in January 2026 on an account that usually costs $5 a month, an overage he estimated at about $4,868. After a support ticket, a Community post, direct emails and a Reddit post, he says Cloudflare waived the full $4,586.64 invoice on February 19.
Reported amount · USD
$4,586.64
per month
Jovan Jester: a recursive image-processing Worker and about $2.2k in charges.
Jovan Jester (@JovanJester), a solo developer, asks CloudflareHelp and CloudflareDev for help with a surprise bill from an accidental recursive loop in an image-processing Worker. Weeks later he says the bug left about $2.2k in charges and asks for tips on getting a credit or a deferred payment plan, worried his domains and DNS could be shut down over the unpaid charges.
Reported amount · USD
$2,200
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.
Reported amount · USD
$302
Truong Dang: a $9 R2 Infrequent Access charge for 51 operations, disputed over rounding.
Truong Dang (@cosmodane) says Cloudflare charged him the full $9 for 51 Class A operations on R2 Infrequent Access, which he calculates should have cost $0.00046. He says his billing ticket went unanswered for 19 days and that a rule rounding usage up to the next million was added to the pricing docs after he was billed. He asks for a refund of the $9; CloudflareHelp publicly asks him to DM his ticket details.
Reported amount · USD
$9
Guides · 1
After a $10,000 loop bill: budget alerts and a cost-audit prompt for vibe-coded projects
铁柱AGI (@cgnot996) writes an X article that walks through creating a Cloudflare budget alert, explains why it is only a notice, lists cost-amplifying code patterns, and gives a read-only audit prompt and steps for when a bill has already spiked.