Cloudflare: Pay Me 120k Or We Shut You Down

A long-time Cloudflare customer says the company escalated a dispute over “domain rotation” and gambling-related IP reputation concerns into a forced move to Cloudflare Enterprise—backed by a 24-hour deadline, a $120,000 upfront demand, and, ultimately, deletion and suspension of the customer’s domains that triggered major downtime.

The account begins with a business-plan setup costing about $250/month, used for CDN caching of static content and DDoS protection. In April 2024, Cloudflare allegedly sent an urgent email claiming “serious issues” with account settings that could affect the network, followed by a call that turned out to be sales-focused. A second email two weeks later accused the customer of “domain rotation activities” intended to evade or circumvent blocks by third parties, warning that the account could be terminated if information wasn’t provided within 48 hours. The customer says it used multiple mirror domains for regulatory and operational reasons—such as country-specific game availability, feature segmentation, and affiliate/conversion tracking—and offered to remove secondary domains from Cloudflare if needed.

Cloudflare, according to the customer, refused to provide specifics about what domains were implicated or what would satisfy the alleged ToS issue. Instead, the customer was pushed toward Enterprise pricing. The proposed contract reportedly started at $10,000/month with a requirement to sign a yearly commitment and pay the full year upfront, and later escalated to a demand of $120,000 within 24 hours or Cloudflare would purge the domains. The customer describes the messaging as effectively extortion-like: Enterprise would “magically resolve” the problem, while alternative fixes were dismissed and the deadline left little room for negotiation.

After the dispute escalated, the customer claims Cloudflare deleted DNS records, caching configuration, rate limits/whitelists, email routing, authentication settings, and access configuration—blocking even internal infrastructure—while also suspending the account. An email from Cloudflare technical support allegedly redirected the matter to “trusted safety,” which the customer equated with sales. During migration to Fastly, the customer reports additional downtime due to DNS propagation delays.

The narrative also ties the dispute to the realities of online gambling compliance and IP blocking. The customer argues that Cloudflare may have been concerned about the use of IPs associated with gambling traffic in the U.S., where blocks and reputation scoring can ripple across other customers. In that framing, Cloudflare’s Enterprise requirement (including use of BYOIP) is presented as a way to prevent gambling-related IP reputation from affecting Cloudflare’s broader customer base. Even so, the customer criticizes the lack of clear explanation, the refusal to discuss targeted remediation, and the decision to remove services before a resolution.

In the broader discussion around the account, commenters debate whether the customer’s “domain rotation” practices truly violated policy, but the most consistent takeaway is operational risk: when a critical edge/CDN provider applies account-level enforcement, customers can lose DNS and configuration quickly, leaving little leverage beyond rapid migration and reputational fallout. The account ends with practical advice—back up Cloudflare configuration, avoid deep reliance on proprietary features, and plan for fast exit—because the pricing and enforcement mechanisms appear opaque until pressure hits.