My VPN App Traffic is Being Flagged as DDoS - Need Help

Enter the TLD

Hi everyone, I’m facing an issue with my VPN application, and I hope someone here can help me out. My app, which has over 5 million installations, uses domains managed in my Cloudflare account to connect users to servers. Unfortunately, Cloudflare is misidentifying the app’s traffic as a DDoS attack, and this is causing serious problems for my users. The Problem My app relies on a single IP and DNS record per domain to create secure connections between the client and the server. Recently, Cloudflare started blocking this traffic, assuming it’s part of a DDoS attack. As a result, the connection between the app and the server is being cut off, and users can’t use the app at all. Impact This is a critical issue for my app, as it directly affects millions of users who are unable to connect. The app itself generates legitimate traffic, and I’m sure there’s no malicious activity involved. What I’ve Tried I’ve reviewed the Cloudflare dashboard, but I’m not entirely sure which settings might be causing this misclassification. I’ve also considered adjusting WAF rules, rate limiting, or bot management, but I’m not sure what changes would work best for this situation. What I Need Help With I’d greatly appreciate advice on how to: Allow legitimate traffic from my app to pass through without being flagged as DDoS. Adjust settings to reduce false positives while maintaining security. Understand if there’s a way to allowlist this type of traffic or specific patterns that Cloudflare might be misidentifying. If anyone has faced a similar issue or has insights on how to resolve this, I’d be very grateful for your guidance. Please let me know if you need more details about my setup or traffic patterns. Thank you in advance for your help!

Hi @game.logic.acc,

I’ve sent you a DM so we can create a Support ticket for this.

I have the same Problem, My entire domain, along with all the subdomains has been marked somehow, now I can’t even open my other panels which is configured with other subdomains

And this problem started from two days ago, I think there is a new changes on Cloudflare’s side in last three days

1 Like

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.