Observed topology
AS48408 LOCALITEL-AS Localitel bvba
Unclassified RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS48408: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.
Transit
Downstream networks
Networks for which AS48408 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS59943 | Level 27 BVBA | Hosting | IPv4 IPv6 | 1,335 |
| AS57948 | Cobalt Group BV | Unclassified | IPv4 IPv6 | 622 |
| AS203148 | Xenius BVBA | Unclassified | IPv4 IPv6 | 450 |
| AS209725 | Localitel bvba | Unclassified | IPv4 IPv6 | 386 |
| AS47688 | Localitel bvba | Residential | IPv4 IPv6 | 327 |
| AS207750 | Erbacom bvba | Unclassified | IPv4 IPv6 | 91 |
| AS47630 | TeleVoIP bv | Unclassified | IPv4 IPv6 | 66 |
| AS214327 | neXat SA | Unclassified | IPv4 | 59 |
| AS208725 | Devrandom.be BV | Hosting | IPv4 | 23 |
| AS199670 | DNS-Belgium VZW | Unclassified | IPv4 | 6 |
Adjacency
Adjacent networks
Every AS seen directly next to AS48408 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS59943 | Level 27 BVBA | Hosting | IPv4 IPv6 | 1,335 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 1,073 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 715 |
| AS57948 | Cobalt Group BV | Unclassified | IPv4 IPv6 | 654 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 649 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 631 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 540 |
| AS203148 | Xenius BVBA | Unclassified | IPv4 IPv6 | 450 |
| AS209725 | Localitel bvba | Unclassified | IPv4 IPv6 | 386 |
| AS47688 | Localitel bvba | Residential | IPv4 IPv6 | 327 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-02 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.44M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.
Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.
Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.