Observed topology

AS203101 NAVARINO-POP Navarino Single Member S.A.

Unclassified RIPE

Upstreams 23 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 25

Adjacent (IPv6) 0

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

Transit

Upstream networks

All 23

Networks observed carrying traffic for AS203101: 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
AS3356	Level 3 Parent, LLC	Transit	IPv4	277
AS6939	Hurricane Electric LLC	Transit	IPv4	99
AS4637	Telstra Global	Unclassified	IPv4	85
AS2914	NTT America, Inc.	Transit	IPv4	16
AS174	Cogent Communications, LLC	Transit	IPv4	11
AS24482	SG.GS	Hosting	IPv4	11
AS3216	PJSC "Vimpelcom"	Mobile	IPv4	10
AS3333	Reseaux IP Europeens Network Coordination Centre (RIPE NCC)	Unclassified	IPv4	10
AS12552	GlobalConnect AB	Unclassified	IPv4	10
AS12779	IT.Gate S.p.A.	Unclassified	IPv4	10

All 23 upstreams →

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS16509	Amazon.com, Inc.	Hosting	IPv4	1

Adjacency

Adjacent networks

All 25

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

AS	Network	Type	Families	Paths seen
AS3356	Level 3 Parent, LLC	Transit	IPv4	277
AS6939	Hurricane Electric LLC	Transit	IPv4	99
AS4637	Telstra Global	Unclassified	IPv4	85
AS2914	NTT America, Inc.	Transit	IPv4	16
AS174	Cogent Communications, LLC	Transit	IPv4	11
AS24482	SG.GS	Hosting	IPv4	11
AS3216	PJSC "Vimpelcom"	Mobile	IPv4	10
AS3333	Reseaux IP Europeens Network Coordination Centre (RIPE NCC)	Unclassified	IPv4	10
AS12552	GlobalConnect AB	Unclassified	IPv4	10
AS12779	IT.Gate S.p.A.	Unclassified	IPv4	10

All 25 adjacent →

Provenance

Where this comes from

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