Separate people from machines
Suspicious traffic, reported as a measurement problem.
Requests that failed a challenge, arrived from networks with poor reputation or probed for paths that do not exist are held apart from human traffic and shown with the context that made them suspicious. The question answered here is not whether you are under attack. It is how much of last week was real.
Security Traffic
- Challenge issued, passed and abandoned
- Network reputation and ASN context
- Suspicious volume by path and region
- Challenge waves beside human trends
How it helps
What Security Traffic gives you
The outcome, not just the trigger
A challenge that is solved and a challenge that is abandoned mean different things. Classification uses what happened after the challenge, which keeps a cautious rule from writing off traffic that turned out to be people.
Network context, not single requests
Autonomous system, address range history and prior behaviour turn one odd request into a pattern worth naming. Thirty thousand requests from a single network inside an hour is a different finding from thirty thousand spread across a continent.
Where the friction landed
Challenges are reported by path, country and device, next to human visits for the same slice. If human traffic falls in one country while challenges there rise, that correlation is the first thing to check before the drop is read as demand.
Traffic Quality
The rest of Traffic Quality
Classify every request as human, crawler, AI agent, bot or attack before it is counted.
Real People
The human-only view every other module counts and divides by.
Learn moreSearch Crawlers
Crawler activity from verified operators — volume, coverage and the status codes they were served.
Learn moreAI Crawlers
AI-agent crawl volume and the content areas being read — not the same as a referral.
Learn moreBots
Monitors, scrapers, feed readers, link previews and your own tooling, classified by behaviour.
Learn moreBlocked Attacks
Attack volume summarised for analytics, with the forensics handed to the edge console.
Learn moreConnect 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