171.22.36.0/22 - (AS48074)
CIDR
171.22.36.0/22
IP Version
IPv4
Addresses
1K
Mask
/22 (255.255.252.0)
Country
🇬🇧 United Kingdom
City
London
RIR
RIPE NCC
Status
allocated
Allocated
2019-01-30
AS0 discard ROA - upstream RPKI inconsistency
The only ROA covering this prefix names AS0, which means the issuing RIR has published the prefix as “not routable by any AS” (RFC 6483). If the RIR’s allocation records still point to a live operator, the ROA and the RDAP registration disagree - this is an upstream inconsistency in the issuing RIR’s own publications, not necessarily a hijack.
Announced BGP Routes
0 of 0 routesRPKI:
IRR:
Swipe sideways to see all columns →
| Prefix | Origin AS | RPKI | IRR | Last Seen |
|---|---|---|---|---|
| This prefix is not announced as a whole. Parts of it are announced as more-specific prefixes, see below. | ||||
More-Specific Announcements
2 more-specific announcements| Prefix | Origin AS | RPKI | IRR | Last Seen |
|---|---|---|---|---|
| 171.22.36.0/23 | AS48095 XTGLOBAL XT GLOBAL NETWORKS LTD. | Invalid | - | 2026-10-11 |
| 171.22.38.0/23 | AS48095 XTGLOBAL XT GLOBAL NETWORKS LTD. | Invalid | - | 2026-10-11 |
RPKI ROAs
| Prefix | Origin | Max Length | Trust Anchor |
|---|---|---|---|
| 171.22.36.0/22 | AS0 | /22 | ripe |
Transfer History
Registry transfers of 171.22.36.0/22, blocks inside it, or blocks containing it.
- 171.22.36.0/22Transfer ·
Origin ASN
AS48074
Geolocation
Abuse Contact
Learn more
- RPKI and ROAs explainedWhat RPKI valid, invalid and no ROA mean
- RPKI validatorCheck ROA coverage for any prefix or ASN
- What is BGP?How prefixes are announced and routed
- More-specific prefixesGlossary: covering and more-specific routes
- IPv4 transfers in the RIPE NCC regionWho bought and sold address space recently
API
Open https://api.ipctl.io/v1/prefix/171.22.36.0/22Returns prefix allocation, BGP routes, and more-specific subnets.
curl -s "https://api.ipctl.io/v1/prefix/171.22.36.0/22" | jq
External Links