> For the complete documentation index, see [llms.txt](https://help.aikido.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aikido.dev/zen-firewall/zen-features/why-is-this-ip-blocked.md).

# Why is this IP blocked?

The **Why is this IP blocked?** tool lets you look up any IP address and see exactly which Zen Firewall rules are responsible for blocking it. It checks all active blocking features at once, so you can quickly diagnose unexpected blocks or verify that a rule is working as expected.

## How to use it

1. Go to the **Events** feed in a Zen Firewall service.
2. Click **Why is this IP blocked?** in the top right above the table.
3. Enter an IP address in the input field.
4. Click **Check**.

Zen will show you which blocking rules match that IP, such as country blocks, known threat actor lists, user blocks, or a [playbook](/zen-firewall/zen-features/playbooks.md).

<figure><img src="https://3149773201-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyKbzcQGrx7UtrG0nPZZ7%2Fuploads%2Fgit-blob-8b9ec2a681b00af6b23458acdfa916c63d7679c5%2FScreenshot%202026-06-02%20at%2013.59.45.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

{% hint style="info" %}
This tool checks the current state of your blocking rules. If a rule was recently changed, allow up to a minute for it to take effect before checking.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.aikido.dev/zen-firewall/zen-features/why-is-this-ip-blocked.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
