AS56766 BAHILOV Bahilov Ilya Vitalievich PE
🇷🇺Org handle: ORG-BIV2-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
5total
5 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)1,024
Announced (BGP)1,536
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Announced Prefixes
(BGP)5|
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 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 31.133.38.0/23 | 🇷🇺 RU | RIPE | assigned |
| 31.133.43.0/24 | 🇷🇺 RU | RIPE | assigned |
| 176.124.20.0/24 | 🇷🇺 RU | RIPE | assigned |
All 5 announced prefixes of AS56766 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS56766 hands its own prefixes to: transit providers, or peers at an exchange.
- AS41039DON FTTH Timer5
Downstreams (1)
Networks whose own prefixes AS56766 passes on: usually its customers.
- AS8274ONLNK Maksym Naumenko4
Other adjacent networks (1)
Adjacent to AS56766 in the transit part of AS paths: peers, providers or customers.
- AS206810UGLETELECOM GUP DNR "UGLETELECOM"3
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 AS56766 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/56766Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/56766" | jq