Observed topology

AS5432 PROXIMUS-ISP-AS Proximus NV

Mobile RIPE Cable/DSL/ISP

Upstreams 8 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 9

Adjacent (IPv6) 8

Upstream graph Who carries AS5432, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS5432 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS6774	Belgacom International Carrier Services SA	Unclassified	IPv4 IPv6	2,921
AS3356	Level 3 Parent, LLC	Transit	IPv4 IPv6	982
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	628
AS3303	Swisscom (Schweiz) AG	Residential	IPv4	97
AS48185	team.blue NV	Unclassified	IPv4 IPv6	84
AS8218	Zayo Infrastructure France SA	Unclassified	IPv4	65
AS9002	RETN Limited	Unclassified	IPv4 IPv6	19
AS6696	VERIXI SA	Unclassified	IPv4	16

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS5488	Proximus NV	Unclassified	IPv4 IPv6	892

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS6774	Belgacom International Carrier Services SA	Unclassified	IPv4 IPv6	5,219
AS5488	Proximus NV	Unclassified	IPv4 IPv6	4,061
AS3356	Level 3 Parent, LLC	Transit	IPv4 IPv6	2,089
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	1,077
AS3303	Swisscom (Schweiz) AG	Residential	IPv4 IPv6	158
AS48185	team.blue NV	Unclassified	IPv4 IPv6	150
AS8218	Zayo Infrastructure France SA	Unclassified	IPv4	120
AS6696	VERIXI SA	Unclassified	IPv4 IPv6	37
AS9002	RETN Limited	Unclassified	IPv4 IPv6	23

Provenance

Where this comes from

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