Add CrowdSec IP reputation documentation (#698)

This commit is contained in:
Viktor Liu
2026-04-16 18:06:43 +02:00
committed by GitHub
parent 6f88f3fea8
commit b2602add87
7 changed files with 229 additions and 9 deletions
@@ -66,6 +66,14 @@ The following deny reasons can appear for both HTTP and L4 services:
| `ip_restricted` | The client IP was blocked by a CIDR access restriction |
| `country_restricted` | The client's country was blocked by a country access restriction |
| `geo_unavailable` | Country restrictions are configured but the GeoIP database is unavailable (fail-closed) |
| `crowdsec_ban` | The client IP has a CrowdSec ban decision |
| `crowdsec_captcha` | The client IP has a CrowdSec captcha decision |
| `crowdsec_throttle` | The client IP has a CrowdSec throttle decision |
| `crowdsec_unavailable` | CrowdSec enforce mode is active but the bouncer has not completed its initial sync (fail-closed) |
All CrowdSec decision types (ban, captcha, throttle) result in a connection denial in enforce mode. The proxy does not serve captcha challenges or apply rate limiting: the decision type is recorded for informational purposes only.
When CrowdSec is in **observe** mode, the verdict appears in the log metadata but the deny reason field is empty (the connection is allowed). This lets you audit what CrowdSec would block without affecting traffic.
## Use cases