$2.5M saved

Your Network Under Attack

Attack blocked before servers went down — $2.5M saved

Requests per secondPeak 2,360 req/s · Baseline 118 req/s

Edge spike from single ASN

2,360 req/s · 19× over baseline within 240 ms

Secondary burst suppressed

2,200 req/s · Blocked before saturating uplink

Detection time

42 ms

from first anomalous packet

Attacks stopped

7 / 7

past 60 minutes

Downtime avoided

$2.5M

projected revenue loss prevented

●Baseline traffic restored in under 4 seconds.
●Edge firewall policy auto-pushed to 12 POPs.
●Incident team received a single, human-readable report.

Instant detection timeline

Red rows triggered the response playbook
Baseline steady at 118–125 req/s across clusters.
#1
Adaptive baseline learned from last 15 minutes.
2,360 req/s from a single ASN — blocked in 42 ms.
Anomaly#2
Spike exceeded adaptive threshold ×19 and fingerprint matched known botnet.

Spike exceeded adaptive threshold ×19 and fingerprint matched known botnet. (score: 0.97)

Edge firewall rule synced to all POPs automatically.
#3
Driftlock Edge executed the playbook without operator input.
Commerce API stayed online — $2.5M downtime avoided.
#4
Instant containment kept checkout SLAs in the green.

Try your own data

Paste raw numbers, JSON lines, or upload a CSV. Driftlock figures out the best detector instantly.

Results

Run the detector to see what Driftlock flags. Red rows mark anomalies and explain why they were blocked.