2a01:620:2000::/35 - BGP Prefix
IPv6RIPEassigned RPKI Valid
CIDR
2a01:620:2000::/35
IP Version
IPv6
Addresses
9903.5Y
Mask
/35
Country
🇷🇺 Russia
City
Moscow
RIR
RIPE
Status
assigned
Allocated
-
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. | ||||
Related Announcements
1 less-specific, 5 more-specific announcements| Prefix | Origin AS | RPKI | IRR | Last Seen |
|---|---|---|---|---|
| 2a01:620::/32 | AS12389 ROSTELECOM-AS PJSC Rostelecom | Valid | - | 2026-10-12 |
| 2a01:620:2200::/39 | AS12389 ROSTELECOM-AS PJSC Rostelecom | Valid | - | 2026-10-12 |
| 2a01:620:2c00::/39 | AS12389 ROSTELECOM-AS PJSC Rostelecom | Valid | - | 2026-10-12 |
| 2a01:620:2e00::/39 | AS12389 ROSTELECOM-AS PJSC Rostelecom | Valid | - | 2026-10-12 |
| 2a01:620:3000::/39 | AS12389 ROSTELECOM-AS PJSC Rostelecom | Valid | - | 2026-10-12 |
| 2a01:620:3200::/39 | AS12389 ROSTELECOM-AS PJSC Rostelecom | Valid | - | 2026-10-12 |
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 transfer marketTransfers published by all five RIRs
API
Open https://api.ipctl.io/v1/prefix/2a01:620:2000::/35Returns prefix allocation, BGP routes, and more-specific subnets.
curl -s "https://api.ipctl.io/v1/prefix/2a01:620:2000::/35" | jq
External Links