From a9c30b6aac92dbbe30163ea3a13470c6d58e5de2 Mon Sep 17 00:00:00 2001 From: Tim Veluwenkamp Date: Mon, 14 Sep 2026 09:18:47 +0200 Subject: [PATCH] Update rate limiting documentation with Sansec Security Monitor Added Sansec Security Monitor to the list of known plugins that may trigger rate limiting. --- ...how-to-resolve-rate-limited-requests-429-too-many-requests.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/hypernode-platform/nginx/how-to-resolve-rate-limited-requests-429-too-many-requests.md b/docs/hypernode-platform/nginx/how-to-resolve-rate-limited-requests-429-too-many-requests.md index c380a6e5..1da7cec7 100644 --- a/docs/hypernode-platform/nginx/how-to-resolve-rate-limited-requests-429-too-many-requests.md +++ b/docs/hypernode-platform/nginx/how-to-resolve-rate-limited-requests-429-too-many-requests.md @@ -117,6 +117,7 @@ There are a couple of plugins and service providers that tend to hit the blackli - Mollie - `Mollie.nl HTTP client/1.0` - Screaming - `Screaming Frog SEO Spider` - Cloudflare Healthchecks - `Cloudflare-Healthchecks` +- Sansec Security Monitor - `Sansec Security Monitor` Besides the above-known plugins that will hit the blacklisted keyword, `http.ratelimit` we know that Picqer will also hit the rate limiter because of being blocked by "**zoneperip**". Please find [here](https://picqer.com/files/ip-addresses.txt) the IP addresses of Picqer. You can exclude those IP addresses from hitting the rate limiter if you follow the [instructions](#known-rate-limited-plugins-and-service-providers).