Observed topology

AS203954 ITNSGLOBAL-AS ITNS GLOBAL EOOD

Unclassified RIPE

Upstreams 4 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS203954: 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
AS31293	ITNS GLOBAL EOOD	Unclassified	IPv4	51
AS6939	Hurricane Electric LLC	Transit	IPv4	9
AS8218	Zayo Infrastructure France SA	Unclassified	IPv4	1
AS8280	SYNAPSECOM S.A. Provider of Telecommunications and Internet Services	Hosting	IPv4	1

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS394470	Ecloud360	Unclassified	IPv4	21

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS31293	ITNS GLOBAL EOOD	Unclassified	IPv4	51
AS6939	Hurricane Electric LLC	Transit	IPv4	27
AS394470	Ecloud360	Unclassified	IPv4	21
AS8280	SYNAPSECOM S.A. Provider of Telecommunications and Internet Services	Hosting	IPv4	4
AS8218	Zayo Infrastructure France SA	Unclassified	IPv4	1

Provenance

Where this comes from

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