Find out why an address is blocked
IP control โ Address lookup answers a report such as "I can't reach the app from 203.0.113.7". Enter the visitor's IPv4 or IPv6 address, or a CIDR range of at most /16 for IPv4 or /48 for IPv6, with no host bits set. An IPv4-mapped IPv6 address is looked up as IPv4. Optionally pick the route the visitor tried to reach, and how far back to look at blocked requests: the last 24 hours (the default), 7 days or 30 days. The page URL carries the address, route and range, so you can share or bookmark a lookup.
The page requires the Bans.Read and IpFilters.Read permissions. The blocked-requests section also needs Logs.Read, and the WAF section WafDetections.Read; without them those sections are not shown.
Verdict
The banner at the top sums up the result:
- Blocked names the active bans and Block-mode IP filter sources that stop the address, or some address in the range.
- Not blocked, but observed names the Observe-mode sources that would block it after a switch to Block.
- Not banned or blocked by an IP filter means neither bans nor IP filters stop it. When you can read logs, the banner lists the recent blocked requests by reason, such as rate limits or the WAF.
The verdict follows Edge's rules: an allowlisted address is neither banned nor blocked by the IP filter sources its entry covers. With a route selected, only global entries and those for that route count.
Sections
- Bans lists the active bans that cover the address, with their reason, route, expiry and whether an allowlist entry overrides them.
- IP filter sources lists the enabled sources whose current list contains the address or part of the range, with their mode, scope and the matching list entries.
- Allowlist entries lists the entries that cover the address or part of the range.
- Recorded IP filter matches lists the addresses that sources recorded while blocking or observing, within the matched-address retention.
- Blocked requests groups the requests from the address that were blocked in the chosen range by reason (ban, IP filter, WAF, rate limit, access control or challenge) and route. View requests opens Logs filtered to that address, reason and route. Rate limit, access control and challenge blocks appear only here, because they are decided per request and leave no stored state.
- WAF detections shows the latest detections for the address in the chosen range. Open in WAF Detections opens the full list filtered to it.
Each section lists a limited number of entries. When the page says it shortened a list, narrow the range or pick a route to see the rest.
Resolve
Resolve on a ban, a blocking source or a recorded block opens the same dialog as the Blocked IPs report: lift the ban, allowlist the address or range, switch the source to Observe, or disable it. Allowlist on an observed match opens an allowlist entry for that address and source. The lookup refreshes after a change.
The lookup does not evaluate access control policies against the address. To see whether a country or IP rule blocks a visitor, check the access-control rows under Blocked requests or the route's access control policy.
REST API
GET api/address-lookup?address=<ip-or-cidr>&proxyRouteId=<id> returns the bans, sources, allowlist entries and recorded matches. GET api/logs/blocked-requests/summary?clientAddress=<ip-or-cidr> returns the blocked-request groups and accepts the other Logs filters. See the REST API reference for authentication.