Total Requests
0
This session
Free real-time DDoS Dstat — Layer4 & Layer7 Dstat graphs for bandwidth, connections and requests.
Connecting…
Cloudflare UAM Dstat — Live Under Attack Mode Test Graph
https://uam.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
- Yes
- Protection Type
- UAM
Requests · Last 60s
0
Guide
The complete guide to live Dstat and FAQ
What is a Cloudflare UAM Dstat?
This Dstat target runs Cloudflare's Under Attack Mode (UAM): every new visitor is served an interstitial JavaScript challenge that the client must execute correctly before any request reaches the origin. Plain HTTP floods score zero here — the requests die at the challenge page and never count.
That makes a UAM Dstat the standard benchmark for challenge-solving capability. The allowed/bypassed share of the graph reflects requests from clients that actually executed the JS challenge (headless browsers or solver-equipped tools), while the blocked share is traffic that failed it. If a method shows strong numbers on the plain Cloudflare page but flatlines here, it cannot handle UAM.
Cloudflare UAM Dstat FAQ
What is Cloudflare Under Attack Mode (UAM)?
UAM is Cloudflare's highest security level: every new visitor gets a ~5 second JavaScript challenge page. Only clients that execute the challenge correctly receive a clearance cookie and reach the origin.
Why do normal HTTP floods show zero on a UAM Dstat?
Because raw HTTP requests never pass the challenge — they receive the interstitial page and are dropped. Only traffic from JS-capable clients (real browsers, headless browsers, or solver tools) gets counted as allowed.
What does a high allowed share on this page indicate?
It indicates the traffic source can solve the UAM challenge at scale — typically meaning headless-browser-based or clearance-cookie-reusing methods, which are far more resource-intensive than plain floods.