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.
Held. No attack traffic reached the origin (measured zero), and no down event was reported (not proof of uptime).
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, 30:00
What got past the protection?
0rpsmeasured zeroleaked to origin
Sample · p95 · whole run, 30:00
demo only
How fast did protection react?
Not measuredNo clock was recorded for this run.
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), 1 demo only (no connected source yet), 2 not measured.
Accountability
Started by
Not recorded by the platform yet
Target registration
Registered for Sample organisation by DDoSphere staff
Pacing
Steps start automatically
Generators
4 of 4 generators fired
Evidence coverage
6 of 12 readings present. 1 of the 6 is demo only. Not measured: time to mitigate, 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 here5
Demo only1
Not measured6
Readings (12)
Readings
Reading
Value
How it was measured
Source
Offered rate
241 krps
How it was measuredGenerators · mean · whole run
SourceSample (generators in a connected deployment)
Requests sent
434 Mrequests
How it was measuredGenerators · sum · whole run
SourceSample (generators in a connected deployment)
Responses received (generator-observed)
431 Mrequests
How it was measuredGenerators observing the target · sum · whole run
SourceSample (generators in a connected deployment)
Response time
212ms
How it was measuredGenerators observing the target · p95 · whole run
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
SourceSample (health monitor in a connected deployment)
Leaked to origin
0rpsmeasured zero
How it was measuredTarget side · p95 · whole run
SourceSample (no connected source yet)
Time to mitigate
Not measured
How it was measuredNo clock was recorded for this run
SourceNo 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 (2)
Step
Attack type
Duration
Verdictdemo only
1
HTTP(S) GET Flood, L7 HTTPS port 443
15:00
Held
2
HTTP(S) GET Flood, L7 HTTPS port 443
15:00
Held
Mitigation clocks
How long until protection acted.
Time to mitigate
Not measured
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.
