Observed topology

AS41477 LMAX

Unclassified RIPE

Upstreams 5 carry this network

Downstreams 4 this network carries

Adjacent (IPv4) 10

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS41477: 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
AS13335	Cloudflare, Inc.	Hosting	IPv4	325
AS6461	Zayo Bandwidth	Transit	IPv4	77
AS3491	PCCW Global (HK) Ltd.	Transit	IPv4	20
AS2914	NTT America, Inc.	Transit	IPv4	19
AS174	Cogent Communications, LLC	Transit	IPv4	1

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS39498	LMAX Digital Group Limited	Unclassified	IPv4	59
AS51221	LMAX Limited	Unclassified	IPv4	59
AS63428	LMAX USA Inc	Unclassified	IPv4	57
AS47675	LMAX Digital Group Limited	Unclassified	IPv4	56

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS13335	Cloudflare, Inc.	Hosting	IPv4	325
AS6461	Zayo Bandwidth	Transit	IPv4	199
AS1299	Arelion Sweden AB	Transit	IPv4	72
AS39498	LMAX Digital Group Limited	Unclassified	IPv4	59
AS51221	LMAX Limited	Unclassified	IPv4	59
AS63428	LMAX USA Inc	Unclassified	IPv4	57
AS47675	LMAX Digital Group Limited	Unclassified	IPv4	56
AS2914	NTT America, Inc.	Transit	IPv4	42
AS3491	PCCW Global (HK) Ltd.	Transit	IPv4	20
AS174	Cogent Communications, LLC	Transit	IPv4	15

Provenance

Where this comes from

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