QuayHealth runs a municipal services serving customers across the Benelux. Before Deflecto, attacks meant diverting traffic to a scrubbing provider and waiting.
The challenge
Repeated layer 7 floods against login and checkout.
The result
- 175 attacks mitigated in the first year
- Median time to mitigation 338 ms
- 46% lower origin infrastructure cost
- Zero customer-visible outages
Our engineers get a notification, not a phone call.
Head of Infrastructure, QuayHealth
Solid runbook advice. The DNS-at-2am point hit home.
Would love a follow-up on how you handle HTTP/3 fingerprinting.
Great to hear, thanks for sharing your experience.
Thanks — sharing this with our on-call team.
Verified good bots and allow-listed partners bypass challenges entirely.
Nice to read a vendor blog that admits what went wrong.
Nice to read a vendor blog that admits what went wrong.
Thanks! Yes — the risk score and its components are included in every log record.
Solid runbook advice. The DNS-at-2am point hit home.
We had the exact false-positive issue with CGNAT carriers. The weighting change makes sense.
Verified good bots and allow-listed partners bypass challenges entirely.
Could you share the dataset behind the percentages?