2a0b:b500::/31 - TK Telecom Samara (AS60764)
CIDR
2a0b:b500::/31
IP Version
IPv6
Addresses
158456.3Y
Mask
/31
Country
🇷🇺 Russia
City
Samara
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 |
|---|---|---|---|---|
| 2a0b:b500::/31 | AS60764 TK-Telecom Telecom Samara LLC | Valid | RIPE | 2026-10-12 |
More-Specific Announcements
1 more-specific announcement| Prefix | Origin AS | RPKI | IRR | Last Seen |
|---|---|---|---|---|
| 2a0b:b500::/32 | AS60764 TK-Telecom Telecom Samara LLC | Valid | - | 2026-10-12 |
RPKI ROAs
IRR Route Objects
| Origin | Registry | Maintainer | Modified |
|---|---|---|---|
| AS60764 | RIPE | mnt-ru-telecomsamara-1 | 2018-12-15 |
More Specific Prefixes
| Prefix | AS | Country | Status |
|---|---|---|---|
| 2a0b:b500::/32 | AS60764 | 🇷🇺RU | assigned |
Transfer History
Registry transfers of 2a0b:b500::/31, blocks inside it, or blocks containing it.
- 2a0b:b500::/30Transfer ·
| Date | Resource | From | To | Type |
|---|---|---|---|---|
| 2a0b:b500::/30 | TK-Telecom, OOO | Telecom Samara LLC | Transfer |
Origin ASN
AS60764
TK-Telecom Telecom Samara LLC
Related Prefixes
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/2a0b:b500::/31Returns prefix allocation, BGP routes, and more-specific subnets.
curl -s "https://api.ipctl.io/v1/prefix/2a0b:b500::/31" | jq
External Links