AS43312 I-LAN-AS LLC IRPIN LOCAL NETWORKS
🇺🇦Org handle: ORG-LILN2-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
4total
3 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)2,560
Announced (BGP)2,560
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)7.9×10²⁸
Announced Prefixes
(BGP)4|
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 |
Allocated Prefixes
(RIR)4Prefix | Country | RIR | Status |
|---|---|---|---|
| 91.200.124.0/22 | 🇺🇦 UA | RIPENCC | assigned |
| 193.201.216.0/22 | 🇺🇦 UA | RIPENCC | assigned |
| 195.38.8.0/23 | 🇺🇦 UA | RIPE | assigned |
| 2a0e:3304::/32 | 🇺🇦 UA | RIPE | assigned |
All 4 announced prefixes of AS43312 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS43312 hands its own prefixes to: transit providers, or peers at an exchange.
- AS48641SYNTEGRA Telecom4
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 AS43312 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/43312Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/43312" | jq