Nobody is signed in. You are looking at sample data as the Admin role would see it. In a connected deployment this menu shows your name, organisation, role, when your session ends, and Sign out.
#1423Peak season stress
Sample data recorded at 2026-09-20 14:20:53Z. Nothing on this page is live. Items marked demo only have no connected source yet.
Running, step 2 of 3Verdict so farDegradingdemo only
Verdict so far: Degrading. 31.4 k rps reached the origin.
Demo only: the verdict and the leak reading have no connected source yet.
Plain answers
Is the site still up?
No down event reported
Not proof of uptime: monitor coverage is not reported.
Sample (health monitor in a connected deployment) · first down event · whole run so far
What got past the protection?
31.4 krpsleaked to origin
Sample · p95 · last 60 s · 14,203 samples
demo only
How fast did protection react?
47stime to mitigate
Sample · first packet 14:02:11Z to first drop
demo only
Could customers still buy?
Not measuredNo business probe is connected, so this is unknown, not zero.
4 questions: 1 has a connected source in live deployments (sample here), 2 demo only (no connected source yet), 1 not measured.
Accountability
Started by
Not recorded by the platform yet
Target registration
Registered for Sample organisation by DDoSphere staff
Pacing
Steps wait for approval
Generators
6 of 6 generators fired
Evidence coverage
5 of 12 readings present. 2 of the 5 are demo only. Not measured: requests sent, responses received (generator-observed), blocked by protection, business probe success, time to detect, time to alert, time to divert. The plan figure (offered rate requested) is not counted.
Connected-capable source, sample here3
Demo only2
Not measured7
Readings (12)
Readings
Reading
Value
How it was measured
Source
Offered rate
265 krps
How it was measuredGenerators · mean · whole run so far
SourceSample (generators in a connected deployment)
Requests sent
Not measured
How it was measuredGenerators · sum · whole run so far
SourceNot reported
Responses received (generator-observed)
Not measured
How it was measuredGenerators observing the target · sum · whole run so far
SourceNot reported
Response time
486ms
How it was measuredGenerators observing the target · p95 · whole run so far
SourceSample (generators in a connected deployment)
First down event
No down event reportedNot proof of uptime: monitor coverage is not reported.
How it was measuredHealth monitor · whole run so far
SourceSample (health monitor in a connected deployment)
Leaked to origin
31.4 krps
How it was measuredTarget side · p95 · whole run so far
SourceSample (no connected source yet)
Time to mitigate
47s
How it was measuredProtection · first packet to first drop
SourceSample (no connected source yet)
Blocked by protection
Not measured
How it was measuredNo source measures it yet
SourceNo connected source yet
Business probe success
Not measured
How it was measuredNo business probe is connected
SourceNo connected source yet
Time to detect
Not measured
How it was measuredNot observable from the target
SourceNo connected source yet
Time to alert
Not measured
How it was measuredNot observable from the target
SourceNo connected source yet
Time to divert
Not measured
How it was measuredNot observable from the target
SourceNo connected source yet
Steps (3)
Step
Attack type
Duration
Verdictdemo only
1
TCP SYN Flood, L4 TCP port 443
10:00
Held
2
HTTP(S) GET Flood, L7 HTTPS port 443
20:00
Verdict so far:Degrading
3
UDP Flood, L4 UDP port 443
10:00
Not run yet
Mitigation clocks
How long until protection acted.
Time to mitigate
47 s
Time to detect
Not observable from the target
Time to alert
Not observable from the target
Time to divert
Not observable from the target
How this was measured
In a connected deployment, generator figures come from the generators' own counters and the first down event from the health monitor that watches each step; on this page they are sample data. Readings marked demo only have no connected source in this version. Windows and statistics are named on every reading; nothing that was not measured is shown as zero. The mitigation clocks start at the first packet: time to mitigate needs a protection layer that reports when it acted, and detect, alert and divert are not observable from the target.
