AS208838 DOMSET DomSet OOO
🇷🇺Org handle: ORG-DO58-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
2total
2 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)1,536
Announced (BGP)1,536
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)0
Announced Prefixes
(BGP)2|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 45.83.92.0/22 | 🇷🇺 RU | RIPENCC | allocated |
| 91.221.246.0/23 | 🇷🇺 RU | RIPENCC | allocated |
| 2a0e:7e80::/29 | 🇷🇺 RU | RIPENCC | allocated |
All 2 announced prefixes of AS208838 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS208838 hands its own prefixes to: transit providers, or peers at an exchange.
- AS3216SOVAM PJSC "Vimpelcom"2
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 AS208838 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/208838Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/208838" | jq