2a14:e05:8000::/33 - INLWW AP IOVZ Networks Limited (AS139803)
CIDR
2a14:e05:8000::/33
IP Version
IPv6
Addresses
39614Y
Mask
/33
Country
🇺🇦 Ukraine
City
Kyiv (Solomyansk)
RIR
RIPE NCC
Status
announced
Allocated
-
Announced BGP Routes
1 of 1 routeRPKI:
IRR:
Swipe sideways to see all columns →
| Prefix | Origin AS | RPKI | IRR | Last Seen |
|---|---|---|---|---|
| 2a14:e05:8000::/33 | AS139803 INLWW-AS-AP iOVZ Networks Limited | Valid | - | 2026-10-11 |
RPKI ROAs
| Prefix | Origin | Max Length | Trust Anchor |
|---|---|---|---|
| 2a14:e00::/29 | AS23532 | /48 | ripe |
| 2a14:e00::/29 | AS55201 | /48 | ripe |
| 2a14:e00::/29 | AS139803 | /48 | ripe |
| 2a14:e00::/29 | AS197537 | /48 | ripe |
| 2a14:e00::/29 | AS202736 | /48 | ripe |
| 2a14:e00::/29 | AS204936 | /48 | ripe |
| 2a14:e00::/29 | AS213507 | /48 | ripe |
| 2a14:e00::/29 | AS216138 | /48 | ripe |
| 2a14:e00::/29 | AS400342 | /48 | ripe |
| 2a14:e00::/29 | AS401163 | /48 | ripe |
Related Prefixes
Geolocation
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/2a14:e05:8000::/33Returns prefix allocation, BGP routes, and more-specific subnets.
curl -s "https://api.ipctl.io/v1/prefix/2a14:e05:8000::/33" | jq
External Links