asn.dev

Observed topology

AS5488 Belgacom Proximus NV

Unclassified RIPE

Upstreams 1 carry this network
Downstreams 33 this network carries
Adjacent (IPv4) 34
Adjacent (IPv6) 7
Upstream graph Who carries AS5488, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS5488 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS5488: 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.

ASNetworkTypeFamiliesPaths seen
AS5432Proximus NVMobileIPv4 IPv6907

Transit

Downstream networks

All 33

Networks for which AS5488 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS21373Banque Nationale de BelgiqueUnclassifiedIPv4312
AS8221ISABEL N.V.UnclassifiedIPv4299
AS205409Embuild VZWUnclassifiedIPv4236
AS207232CHIREC asblUnclassifiedIPv4205
AS201859Ministeries van de Vlaamse GemeenschapUnclassifiedIPv4 IPv6149
AS49333Roularta Media Group SAUnclassifiedIPv4118
AS201887SAVACO NVUnclassifiedIPv4118
AS28704Proximus NVUnclassifiedIPv4117
AS200133HUmani SocietyUnclassifiedIPv4 IPv6116
AS25428Colruyt Group NVUnclassifiedIPv4 IPv6107

All 33 downstreams →

Adjacency

Adjacent networks

All 35

Every AS seen directly next to AS5488 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS5432Proximus NVMobileIPv4 IPv64,142
AS201859Ministeries van de Vlaamse GemeenschapUnclassifiedIPv4 IPv6555
AS21373Banque Nationale de BelgiqueUnclassifiedIPv4312
AS8221ISABEL N.V.UnclassifiedIPv4299
AS205409Embuild VZWUnclassifiedIPv4236
AS207232CHIREC asblUnclassifiedIPv4205
AS49333Roularta Media Group SAUnclassifiedIPv4118
AS201887SAVACO NVUnclassifiedIPv4118
AS28704Proximus NVUnclassifiedIPv4117
AS200133HUmani SocietyUnclassifiedIPv4 IPv6116

All 35 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-07 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 72.97M 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.