Skip to content

Update simulate-ddos-attack.mdx #25057

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 10, 2025
Merged

Update simulate-ddos-attack.mdx #25057

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 1 addition & 23 deletions src/content/docs/ddos-protection/reference/simulate-ddos-attack.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,28 +17,6 @@ You can only launch DDoS attacks against your own Internet properties — your z

## Before you start

You do not have to obtain permission from Cloudflare to launch a DDoS attack simulation against your own Internet properties. However, before launching the simulated attack, you must [open a Support ticket](/support/contacting-cloudflare-support/) and provide the information below. All fields are mandatory.
You do not have to obtain permission from Cloudflare to launch a DDoS attack simulation against your own Internet properties.

It is recommended that you choose the right service and enable the correct features to test against the corresponding DDoS attacks. For example, if you want to test Cloudflare against an HTTP DDoS attack and you are only using Magic Transit, the test is going to fail because you need to onboard your HTTP application to Cloudflare's reverse proxy service to test our HTTP DDoS Protection.

### **For WAF/CDN customers:**

* Attack origin region
* Attack duration
* Attack window (UTC)
* Attack method
* Traffic estimate in both requests per second (rps) and bandwidth (Gbps/Mbps/MBps)
* Target IPs, ports, ranges, zones, hostnames, full URLs
* Contact in case of emergency

### For Magic Transit and Spectrum customers:

* Attack origin region
* Attack duration
* Attack date & timeframe
* Attack method
* Target IPs, ports, ranges, zones, hostnames, full URLs
* Protocol
* Traffic estimate in both requests per second (rps) and bandwidth (Gbps/Mbps/MBps)
* Max packet/bit rate
* Contact in case of emergency
Loading