asn.dev

Observed topology

AS50903 TRINAPS

Unclassified RIPE Cable/DSL/ISP

Upstreams 9 carry this network
Downstreams 1 this network carries
Adjacent (IPv4) 9
Adjacent (IPv6) 7
Upstream graph Who carries AS50903, and who carries them, drawn as a map up to the transit-free core. 3 exchanges Where AS50903 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS29075IELO-LIAZO SERVICES SASUnclassifiedIPv4 IPv6165
AS6939Hurricane Electric LLCTransitIPv4 IPv661
AS5511Orange S.A.TransitIPv424
AS24482SG.GSHostingIPv4 IPv65
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv65
AS6696VERIXI SAUnclassifiedIPv44
AS37100SEACOM LimitedUnclassifiedIPv44
AS37721Virtual Technologies & SolutionsResidentialIPv44
AS13030Init7 (Switzerland) Ltd.HostingIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS210403Groupe LWS SARLUnclassifiedIPv4 IPv6524

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS210403Groupe LWS SARLUnclassifiedIPv4 IPv6524
AS29075IELO-LIAZO SERVICES SASUnclassifiedIPv4 IPv6458
AS6939Hurricane Electric LLCTransitIPv4 IPv6206
AS5511Orange S.A.TransitIPv466
AS24482SG.GSHostingIPv4 IPv615
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv615
AS6696VERIXI SAUnclassifiedIPv411
AS37100SEACOM LimitedUnclassifiedIPv411
AS37721Virtual Technologies & SolutionsResidentialIPv411
AS25091IP-Max SAUnclassifiedIPv63

All 11 adjacent →

Provenance

Where this comes from

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