Skip to content

Commit 15d4c8a

Browse files
patriciasantaananevikashah
authored andcommitted
clarify automatic thresholds (#24809)
1 parent a6b73f4 commit 15d4c8a

File tree

1 file changed

+2
-2
lines changed
  • src/content/docs/ddos-protection/advanced-ddos-systems/overview

1 file changed

+2
-2
lines changed

src/content/docs/ddos-protection/advanced-ddos-systems/overview/index.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -46,9 +46,9 @@ The automatic threshold system calculates thresholds every 10 minutes for both n
4646

4747
These checks are performed independently for SYN Flood Protection, Out-of-State TCP Flood Protection, and Advanced DNS Protection. The criteria does not require the presence of any rules to be configured. Accounts initially provisioned by the automatic system will have default thresholds. Otherwise, thresholds may be unconfigured if they are not set by Cloudflare.
4848

49-
After seven days, the system calculates a rate and burst threshold for each of the protection components. The burst threshold is calculated as five times the rate threshold.
49+
After seven days, the system calculates a rate and burst threshold for each of the protection components. However, they are not applied. Cloudflare must review the draft thresholds produced by the automatic calculation system before creating real thresholds for your traffic.
5050

51-
Thresholds are applied globally per account and there is no minimum packets-per-second (pps) requirement for threshold calculation.
51+
Thresholds are applied globally per account. There is no minimum packets-per-second (pps) requirement for threshold calculation, but for those under 100 pps, the system will default to a reasonable non-zero rate and burst.
5252

5353
Thresholds are derived using the 95th percentile (P95) of observed traffic over the preceding seven days:
5454

0 commit comments

Comments
 (0)