AS8249 TOTCOM-AS PJSC Rostelecom
🇷🇺Org handle: ORG-JR8-RIPE
OJSC "VolgaTelecom"
RIPE NCCallocated
Announced Prefixes (BGP)
7total
7 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)1,024
Announced (BGP)8,448
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Announced Prefixes
(BGP)7|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)1Prefix | Country | RIR | Status |
|---|---|---|---|
| 185.35.120.0/22 | 🇷🇺 RU | RIPENCC | allocated |
All 7 announced prefixes of AS8249 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS8249 hands its own prefixes to: transit providers, or peers at an exchange.
- AS12389ROSTELECOM PJSC Rostelecom7
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 AS8249 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/8249Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/8249" | jq