Total Requests
0
This session
Free real-time DDoS Dstat — Layer4 & Layer7 Dstat graphs for bandwidth, connections and requests.
Connecting…
Cloudflare Dstat — Live Allowed / Bypassed / Blocked Graph
https://c1.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 Dstat?
A Cloudflare Dstat monitors a target sitting behind Cloudflare's standard proxy (no active challenge). Unlike a plain request counter, it classifies every request into three buckets: allowed 200 responses that reached the origin normally, requests that bypassed protection rules, and requests Cloudflare blocked at the edge.
That breakdown is what makes this Dstat useful: total request volume alone says nothing about effectiveness against a proxied target. The live panel on this page shows the three shares side by side, so you can see how much of the traffic actually penetrates Cloudflare's default filtering.
Cloudflare Dstat FAQ
What do Allowed, Bypassed and Blocked mean?
Allowed (200) are requests that passed Cloudflare and got a normal response from the origin. Bypassed are requests that slipped past protection rules. Blocked are requests Cloudflare stopped at the edge — they never reached the origin.
Is there a UAM or CAPTCHA challenge on this endpoint?
No. This endpoint runs Cloudflare's standard proxy without an active challenge. For challenge-protected targets, see the Cloudflare UAM and Cloudflare CAPTCHA Dstat pages.
Why is the blocked share important?
A high blocked share means Cloudflare's edge is filtering most of the traffic before it reaches the origin — the method generates volume but little real impact. Effective Layer7 traffic shows a high allowed/bypassed share instead.