---
title: Abuse Protection
description: We absorb floods, bad bots, and abuse aimed at your services — with a human on it when things escalate. Honest about scale — within the bounds of your infrastructure.
---

A significant proportion of the traffic directed at a set of services does not originate with legitimate users: it consists of floods, automated scrapers, credential-testing attempts, and probing for weaknesses. This service filters, rate-limits, and blocks such traffic at the routing layer, with human intervention at the point where automated defenses prove insufficient.

The scope of the service is stated precisely, as this is a domain in which imprecision is common. The protection operates at the core of an organization's own infrastructure, within its bounds — it is not a globally distributed absorption network. For application-layer abuse directed at specific services, that is the appropriate location at which to address it. A large-scale volumetric attack belongs to a different category of defense, one founded on globally distributed capacity; where such an attack is the concern, the appropriate response is to say so directly rather than to represent this service as its equivalent.

The service applies to the application-level abuse that most organizations actually encounter: scraping, credential stuffing, automated traffic, and floods directed specifically at them. Its boundary is the edge of the organization's own infrastructure, identified as such.