AS49516 IP-OVCHINNIKOV-AS IP Ovchinnikov Vasiliy Fedorovich
๐ท๐บOrg handle: ORG-IOVF1-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
3total
3 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)3,584
Announced (BGP)3,584
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Prefix Limit (IPv4)
10
Prefix Limit (IPv6)
5
Country
๐ท๐บ RURIR
RIPE NCCStatus
allocated
Allocated
2009-06-23
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 91.214.196.0/22 | ๐ท๐บ RU | RIPENCC | assigned |
| 91.221.30.0/23 | ๐ท๐บ RU | RIPENCC | assigned |
| 176.107.0.0/21 | ๐ท๐บ RU | RIPENCC | assigned |
All 3 announced prefixes of AS49516 โ
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS49516 hands its own prefixes to: transit providers, or peers at an exchange.
- AS31133MF MGSM PJSC MegaFon3
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 AS49516 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/49516Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/49516" | jq