From 820efd20c2b7034e6af79e9a9ff27063bdffd1f3 Mon Sep 17 00:00:00 2001 From: Tim Veluwenkamp Date: Fri, 15 May 2026 11:10:09 +0200 Subject: [PATCH] Update known plugins for rate limiting documentation Added Cloudflare Healthchecks to the list of known plugins that 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 3e2f116d..04e42fe6 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 @@ -116,6 +116,7 @@ There are a couple of plugins and service providers that tend to hit the blackli - MailPlus - `Jersey/2.23.1` - Mollie - `Mollie.nl HTTP client/1.0` - Screaming - `Screaming Frog SEO Spider` +- Cloudflare Healthchecks - `Cloudflare-Healthchecks` 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).