Skip to content
Traffic Quality

Separate people from machines

The attacks you never saw still moved your traffic chart.

Requests stopped at the edge never reach your application, but they are still requests, and a single block event can multiply an hour of raw traffic. This report carries the volume, shape and timing that explain that hour. Rule tuning, signatures and per-request forensics stay in the edge console.

Blocked Attacks

  • Blocked volume in the traffic split
  • Category, timing and targeted paths
  • Origin impact during block events
  • Deep investigation in the edge console

How it helps

What Blocked Attacks gives you

1

So the chart adds up

Blocked volume sits in the traffic split beside human visits and every bot class. An hour where total requests rose tenfold then reads as a block event with a start and an end, rather than an anomaly nobody can account for.

2

Analytics depth, not security depth

Category, timing, targeted paths and the volume absorbed — enough to explain a number. Payload inspection, rule history and per-request investigation live one link away in the edge console, because a second security console inside an analytics tool would be worse than both.

3

What the origin actually felt

Because blocked requests were absorbed at the edge, origin latency and error rates are measured on the traffic that arrived. When an attack overlaps a slow hour, this shows whether the origin ever saw any of it.

Connect a site today. Read tomorrow's brief instead of building it.

Connect a site and the first brief arrives with the day's changes already explained — traffic separated from bots, conversions attached to revenue, and the evidence behind every sentence one click away.

Real people separated from bots Every answer shows its evidence Reveliqo runs on Reveliqo