AS208075 RSVO_Mirit_Sochi JSC Russian Broadcasting and Notification Networks
🇷🇺Org handle: ORG-OOTR1-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
1total
1 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)1,280
Announced (BGP)256
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)0
Announced Prefixes
(BGP)1|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)4Prefix | Country | RIR | Status |
|---|---|---|---|
| 91.230.182.0/23 | 🇷🇺 RU | RIPENCC | allocated |
| 91.230.182.0/24 | 🇷🇺 RU | RIPE | assigned |
| 91.230.228.0/23 | 🇷🇺 RU | RIPENCC | allocated |
| 2a0a:af40::/29 | 🇷🇺 RU | RIPENCC | allocated |
All 1 announced prefix of AS208075 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS208075 hands its own prefixes to: transit providers, or peers at an exchange.
- AS12389ROSTELECOM PJSC Rostelecom1
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 AS208075 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/208075Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/208075" | jq