AS208416 LCL-AS LCL BELGIUM NV
🇧🇪Org handle: ORG-LBN2-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
4total
4 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)1,024
Announced (BGP)1,024
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)0
Announced Prefixes
(BGP)4|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 45.138.120.0/22 | 🇧🇪 BE | RIPENCC | allocated |
| 2a0e:ad40::/29 | 🇧🇪 BE | RIPENCC | allocated |
All 4 announced prefixes of AS208416 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS208416 hands its own prefixes to: transit providers, or peers at an exchange.
- AS3257GTT BACKBONE GTT Communications4
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 AS208416 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/208416Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/208416" | jq