#1421DNS amplification rehearsal

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.

FinishedVerdictTarget downdemo only

Target: ns1.example.com
Started: 2026-09-19 22:40:03Z
Ran: 15:02
Generators: 6 of 6 fired

Run again Open evidence report

Map

Where the run is

1 UDP Flood 15:00Target down

Step verdicts are demo only.

15:02 elapsed of 15:00 planned, past the planned end.

How to read this track

The track is the plan and the clock, not a measurement of the target. Each step is sized by its planned duration; the filled part of the running step is the time elapsed; the word under a step is its verdict.

Plain answers

Is the site still up?

Sample: first down event at 22:47:15Z, in step 1.

Sample (health monitor in a connected deployment) · first down event · whole run, 15:02

What got past the protection?

188 krpsleaked to origin

Sample · p95 · whole run, 15:02

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.

How these are measured

Is the site still up?: First down event: The first time a health monitor reported the target as down. No report is not proof of uptime: the platform does not say whether a monitor watched each step.
What got past the protection?: Leaked to origin: Requests per second that passed the protection layer and reached the origin.
How fast did protection react?: Time to mitigate: Seconds from the start of the load until the protection layer acted.
Could customers still buy?: Business probe success: Share of the business probe's scripted purchases that completed during the run.

Each answer names its source, statistic and window under the value. Charts of the whole run are on the Timeline tab.

Readings this run

6 of 12 readings present. 6 not measured.

Show all 12 readings

Readings this run
Reading	Value	How it was measured	Source
Offered rate	299 krps	Generators · mean · whole run	Sample (generators in a connected deployment)
Requests sent	270 Mrequests	Generators · sum · whole run	Sample (generators in a connected deployment)
Responses received (generator-observed)	118 Mrequests	Generators observing the target · sum · whole run	Sample (generators in a connected deployment)
Response time	1.84 kms	Generators observing the target · p95 · whole run	Sample (generators in a connected deployment)
First down event	22:47:15ZFirst down event, step 1	Health monitor · whole run	Sample (health monitor in a connected deployment)
Leaked to origin	188 krps	Target side · p95 · whole run	Sample (no connected source yet)
Time to mitigate	Not measured	No clock was recorded for this run	No connected source yet
Blocked by protection	Not measured	No source measures it yet	No connected source yet
Business probe success	Not measured	No business probe is connected	No connected source yet
Time to detect	Not measured	Not observable from the target	No connected source yet
Time to alert	Not measured	Not observable from the target	No connected source yet
Time to divert	Not measured	Not observable from the target	No connected source yet

Run activity

Newest first, UTC

22:55:05ZRun finished after 15:02.
22:55:03ZStep 1 finished. Target down
22:47:15ZDown event for ns1.example.com in step 1.

Show 2 earlier events

22:40:03ZRun started with 6 generators.
22:40:03ZStep 1 UDP Flood started.

Generators

State

Where the run is

Plan steps

Plain answers

Answers

This is taking longer than usual. The server has not answered yet.

No answer after 20 seconds.

Run activity

Activity

This is taking longer than usual. The server has not answered yet.

No answer after 20 seconds.

Reading

Value

How it was measured

Source

Offered rate

299 krps

Generators · mean · whole run

Sample (generators in a connected deployment)

Requests sent

270 Mrequests

Generators · sum · whole run

Sample (generators in a connected deployment)

Responses received (generator-observed)

118 Mrequests

Generators observing the target · sum · whole run

Sample (generators in a connected deployment)

Response time

1.84 kms

Generators observing the target · p95 · whole run

Sample (generators in a connected deployment)

First down event

22:47:15ZFirst down event, step 1

Health monitor · whole run

Sample (health monitor in a connected deployment)

Leaked to origin

188 krps

Target side · p95 · whole run

Sample (no connected source yet)

Time to mitigate

Not measured

No clock was recorded for this run

No connected source yet

Blocked by protection

Not measured

No source measures it yet

No connected source yet

Business probe success

Not measured

No business probe is connected

No connected source yet

Time to detect

Not measured

Not observable from the target

No connected source yet

Time to alert

Not measured

Not observable from the target

No connected source yet

Time to divert

Not measured

Not observable from the target

No connected source yet

City	Region	State
Frankfurt	eu-central-1	Fired
Virginia	us-east-1	Fired
San Francisco	us-west-1	Fired
Singapore	ap-southeast-1	Fired
Tokyo	ap-northeast-1	Fired
Sao Paulo	sa-east-1	Fired

City

Region

State

Frankfurt

eu-central-1

Fired

Virginia

us-east-1

Fired

San Francisco

us-west-1

Fired

Singapore

ap-southeast-1

Fired

Tokyo

ap-northeast-1

Fired

Sao Paulo

sa-east-1

Fired