🔒 Paid
Bot Traffic Surge
Automated traffic against the public API has risen sharply. It carries realistic user-agents, is spread across many source IPs, and its request patterns look close enough to ordinary customer usage that a coarse, uniform defense will not cleanly separate the two. Backend services are under growing load, and the platform needs that load brought back to a sustainable level — but every real customer who gets wrongly challenged or blocked along the way is a real, measurable cost, not an acceptable side effect to wave away. Bring suspicious traffic and backend load back under control while keeping that cost to genuine customers as low as you can justify.
- Difficulty
- Staff
- Expected Time
- ~18 min
- Category
- API & Traffic
Skills
- Distinguishing targeted, signal-driven defenses from coarse, uniform ones
- Reasoning about false-positive cost as a first-class metric, not a side effect
- Recognizing when a 'protected-looking' backend hides real customer harm
- Evaluating identity-scoped versus traffic-wide mitigations
System Architecture
- Internet Traffic
- Edge / Gateway
- API
- Core Services
This is a Pro scenario. Upgrade to Pro to unlock it.
Upgrade to ProBack to Incidents