Total Requests
0
This session
Free real-time DDoS Dstat — Layer4 & Layer7 Dstat graphs for bandwidth, connections and requests.
Connecting…
Cloudflare Rate Limit Dstat — Live Rate Limiting Test Graph
https://rate-limit-1.dstatbots.win/dstat
Live Dstat Overview
Live Requests
0
+0.0%Last 60s
Peak Requests
0
Last 60s
Avg Requests
0
Last 60s
Mitigation
- Protected
- No
- Protection Type
- —
Requests · Last 60s
0
Guide
The complete guide to live Dstat and FAQ
What is a Cloudflare Rate Limit Dstat?
This Dstat target has Cloudflare rate limiting rules enabled: when a single source IP exceeds the configured request threshold, subsequent requests from that IP are rejected with 429 responses at the edge. The graph therefore shows how much traffic survives per-IP throttling rather than the raw volume sent.
Rate limiting is the most common first line of Layer7 defense, and beating it is purely a question of IP distribution. A well-spread proxy pool keeps every IP under the threshold and the allowed line stays high; a concentrated source gets throttled within seconds. Compare this page with the plain Cloudflare Dstat to isolate the effect of the rate limit rule itself.
Cloudflare Rate Limit Dstat FAQ
How does Cloudflare rate limiting work on this target?
Cloudflare counts requests per source IP in a sliding window. Once an IP exceeds the threshold, its further requests get 429 responses at the edge until the window resets.
What does it take to keep a high request rate here?
IP distribution. Total rate is limited to roughly (number of unique IPs) × (per-IP threshold), so only a large, well-rotated proxy pool sustains high throughput on a rate-limited target.
How is this different from the plain Cloudflare Dstat?
Both sit behind Cloudflare's proxy, but this target adds an explicit rate limiting rule. Comparing the two pages shows exactly how much traffic the rate limit alone strips away.