Observed topology

AS42160 LCPDCO DC STAR nv

Unclassified RIPE

Upstreams 2 carry this network

Downstreams 7 this network carries

Adjacent (IPv4) 9

Adjacent (IPv6) 2

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS42160: 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
AS50309	Arcadiz Telecom NV	Unclassified	IPv4 IPv6	1,390
AS51696	Arcadiz Telecom NV	Unclassified	IPv4 IPv6	77

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS216471	Devout BV	Unclassified	IPv4	83
AS206254	GIG.tech N.V.	Unclassified	IPv4	61
AS199095	Citymesh Integrator NV	Residential	IPv4	60
AS201984	E-Solutions BV	Unclassified	IPv4	60
AS204951	Ubicum BVBA	Unclassified	IPv4	59
AS205583	PC Yellow bv	Unclassified	IPv4	59
AS206665	BOLT BVBA	Unclassified	IPv4	59

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS50309	Arcadiz Telecom NV	Unclassified	IPv4 IPv6	1,807
AS51696	Arcadiz Telecom NV	Unclassified	IPv4 IPv6	101
AS216471	Devout BV	Unclassified	IPv4	83
AS206254	GIG.tech N.V.	Unclassified	IPv4	61
AS199095	Citymesh Integrator NV	Residential	IPv4	60
AS201984	E-Solutions BV	Unclassified	IPv4	60
AS204951	Ubicum BVBA	Unclassified	IPv4	59
AS205583	PC Yellow bv	Unclassified	IPv4	59
AS206665	BOLT BVBA	Unclassified	IPv4	59

Provenance

Where this comes from

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