AS8416 INFOLINE-AS InfoLada Ltd
🇷🇺Org handle: ORG-IL921-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
5total
4 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)41,984
Announced (BGP)41,984
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)6.3×10²⁹
Announced Prefixes
(BGP)5|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)5Prefix | Country | RIR | Status |
|---|---|---|---|
| 81.23.176.0/20 | 🇷🇺 RU | RIPENCC | allocated |
| 178.163.0.0/17 | 🇷🇺 RU | RIPENCC | allocated |
| 185.134.36.0/22 | 🇷🇺 RU | RIPENCC | allocated |
| 217.113.112.0/20 | 🇷🇺 RU | RIPENCC | allocated |
| 2a0a:5900::/29 | 🇷🇺 RU | RIPENCC | allocated |
All 5 announced prefixes of AS8416 →
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS8416 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (3)
Networks whose own prefixes AS8416 passes on: usually its customers.
Other adjacent networks (1)
Adjacent to AS8416 in the transit part of AS paths: peers, providers or customers.
- AS31133MF MGSM PJSC MegaFon1
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 AS8416 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/8416Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/8416" | jq