AS16350 ECHELON-AS Root Holding B.V.
🇳🇱Org handle: ORG-EA36-RIPE
Institutenweg 38
RIPE NCCallocated
Announced Prefixes (BGP)
3total
2 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)5,120
Announced (BGP)5,120
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)7.9×10²⁸
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 185.6.160.0/22 | 🇳🇱 NL | RIPENCC | allocated |
| 217.119.224.0/20 | 🇳🇱 NL | RIPENCC | allocated |
| 2a02:1398::/32 | 🇳🇱 NL | RIPENCC | allocated |
All 3 announced prefixes of AS16350 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS16350 hands its own prefixes to: transit providers, or peers at an exchange.
- AS20847PREVIDER B.V3
ASPA
No ASPA
Abuse Contact
+31205354444
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 AS16350 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/16350Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/16350" | jq