AS48408 LOCALITEL-AS Localitel bvba
🇧🇪Org handle: ORG-RB71-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
4total
3 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)2,304
Announced (BGP)2,304
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)6.3×10²⁹
Routing hygiene
Score 4/100 · Low riskRPKI ROA coverage
100%
no RPKI invalid prefixes
IRR route objects
100%
no origin mismatches
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
3
diversity 63/100
- All announced prefixes have a valid ROA and a matching IRR route object
Based on 4 announced prefixes, updated daily (2026-10-14). How the score works · RPKI explained
Announced Prefixes
(BGP)4|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-22 | |
| Valid | RIPE | 2026-10-22 | |
| Valid | RIPE | 2026-10-22 | |
| Valid | RIPE | 2026-10-22 |
Allocated Prefixes
(RIR)4Prefix | Country | RIR | Status |
|---|---|---|---|
| 91.209.133.0/24 | 🇧🇪 BE | RIPENCC | assigned |
| 109.233.104.0/22 | 🇧🇪 BE | RIPENCC | allocated |
| 185.142.224.0/22 | 🇧🇪 BE | RIPENCC | allocated |
| 2a07:3140::/29 | 🇧🇪 BE | RIPENCC | allocated |
All 4 announced prefixes of AS48408 →
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS48408 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (8)
Networks whose own prefixes AS48408 passes on: usually its customers.
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
- How to run an ASPA checkVerify the upstream providers listed above
- 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/48408Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/48408" | jq