Threat Bulletin 0696: HTTP POST flood against a online casino platform in Southeast Asia
HTTP POST flood against a online casino platform in Southeast Asia, peaking at 408.0 million requests per second. Mitigated in 0.497 seconds.
HTTP POST flood against a online casino platform in Southeast Asia, peaking at 408.0 million requests per second. Mitigated in 0.497 seconds.
login endpoint flood against a online casino platform in Central Europe, peaking at 594.9 million requests per second. Mitigated in 0.932 seconds.
credential stuffing against a news publisher platform in Central Europe, peaking at 522.2 million requests per second. Mitigated in 0.090 seconds.
Here is a question we could not answer well a year ago: what really happens with eU-only processing is now available on every plan? We can answer it now.Challenges beat blocksBlocking lists…
Over the last few months we have spent a lot of time on running a DDoS tabletop exercise with your team. This is what we learned.Latency budgetOur budget for the whole filtering…
This post is about scraper bots are getting better at pretending to be Chrome. It started, as most of our posts do, with an incident that did not go the way we…
Over the last few months we have spent a lot of time on introducing adaptive proof-of-work difficulty. This is what we learned.What we changedWe moved the decision from a single threshold to…
Over the last few months we have spent a lot of time on what a 3.8 Tbps UDP flood looks like from the inside. This is what we learned.What actually happens during…
We get asked about tail latency is the only latency that matters more than almost anything else, so here is the long answer.Observability firstEvery mitigation decision is logged with its reasons, and…
Over the last few months we have spent a lot of time on challenge instead of block: fewer false positives, same protection. This is what we learned.The numbersAcross the last quarter, 71%…
We get asked about measuring the real cost of a TLS handshake under attack more than almost anything else, so here is the long answer.Latency budgetOur budget for the whole filtering pipeline…
credential stuffing against a B2B SaaS platform in the Nordics, peaking at 367.3 million requests per second. Mitigated in 0.560 seconds.