Cloudflare helps protect sites, and accelerate them. We do not attack sites, and our network can’t be used to generate attack traffic.
There are two circumstances where it might appear that Cloudflare is attacking your site.
You’re a Cloudflare customer for your website(s). Since Cloudflare is a reverse proxy for our customers’ sites, Cloudflare IPs are going to show in your server logs until you install something on your server to restore original visitor IP, such as ngx_http_realip_module for NGINX servers.
You’re getting attacks from Cloudflare’s IPs because they are being spoofed. Cloudflare does not send traffic over anything other than http:// (ports 80 and 443), so getting attacked by UDP requests means you are likely seeing a DNS amplification attack, see this article for more information.
If your situation does not fit any of the circumstances listed above, please provide the information requested below via ticket and we can provide solutions for handling an issue that looks like an attack from us.
Required information to investigate:
source IP(s) you are seeing the traffic from
destination IP(s) on your side
IP packet contents
(if possible) tcpdump output in -vvv -s0 -n format
I understand the above, the problem wasn’t us getting attacked.
Just wanted to communicatie that the cloudflare front-end proxy ip was listed on the abuse list which caused Fortiproxy/Fortinet to block it.
Didn’t see any other contact info unless you have a business account to inform you. (Is there another way to contact in case of a similar problem?)
But I see it isn’t listed anymore in the abuse list, so should be ok.