2a07:e380::/29 - KTK TELECOM KTK TELECOM (AS203561)
CIDR
2a07:e380::/29
IP Version
IPv6
Addresses
633825.3Y
Mask
/29
Country
🇷🇺 Russia
City
Moscow (Tsentralnyy administrativnyy okrug)
RIR
RIPE NCC
Status
allocated
Allocated
2018-05-29
Announced BGP Routes
1 of 1 routeRPKI:
IRR:
Swipe sideways to see all columns →
| Prefix | Origin AS | RPKI | IRR | Last Seen |
|---|---|---|---|---|
| 2a07:e380::/29 | AS203561 KTK-TELECOM KTK TELECOM LLC | No ROA | RIPE | 2026-10-11 |
IRR Route Objects
| Origin | Registry | Maintainer | Modified |
|---|---|---|---|
| AS203561 | RIPE | ru-volna-2-mnt | 2018-06-06 |
More Specific Prefixes
| Prefix | AS | Country | Status |
|---|---|---|---|
| 2a07:e380::/48 | 🇷🇺RU | assigned | |
| 2a07:e380:1::/48 | 🇷🇺RU | assigned |
Origin ASN
AS203561
KTK-TELECOM KTK TELECOM LLC
Related Prefixes
Geolocation
Country🇷🇺RussiaRU
RegionMoscow
CityMoscow (Tsentralnyy administrativnyy okrug)
Coordinates55.7365, 37.6238 ↗
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/2a07:e380::/29Returns prefix allocation, BGP routes, and more-specific subnets.
curl -s "https://api.ipctl.io/v1/prefix/2a07:e380::/29" | jq
External Links