AS34168 ELCOM-ISP-AS PJSC Rostelecom
🇷🇺Org handle: ORG-JR8-RIPE
PJSC "Rostelecom". Vladimir branch
RIPE NCCallocated
Announced Prefixes (BGP)
3total
1 IPv42 IPv6
IPv4 Addresses
Allocated (RIR)16,384
Announced (BGP)16,384
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)7.9×10²⁸
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 | |
| Valid | - | 2026-10-09 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 84.53.192.0/18 | 🇷🇺 RU | RIPENCC | allocated |
| 2a02:960::/32 | 🇷🇺 RU | RIPENCC | allocated |
All 3 announced prefixes of AS34168 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS34168 hands its own prefixes to: transit providers, or peers at an exchange.
- AS12389ROSTELECOM PJSC Rostelecom3
ASPA
No ASPA
Abuse Contact
External Links
Learn more
- What is an ASN?Autonomous systems, ASN ranges and how they are assigned
- RPKI and route origin validationWhat the RPKI badges on the prefix list mean
- ASPA explainedWhy AS34168 should publish an ASPA object
- IPv4 transfers in the RIPE NCC regionMonthly volume and the latest registry transfers
- ASN data in AI agents and SIEMMCP server and API integrations
API
Open https://api.ipctl.io/v1/asn/34168Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/34168" | jq