asn.dev

Observed topology

AS60051 EARTHLINK-DMCC

Unclassified RIPE

Upstreams 5 carry this network
Downstreams 2 this network carries
Adjacent (IPv4) 43
Adjacent (IPv6) 18
Upstream graph Who carries AS60051, and who carries them, drawn as a map up to the transit-free core. 6 exchanges Where AS60051 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS60051: 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
AS1299Arelion Sweden ABTransitIPv4155
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv454
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv422
AS34984Superonline Iletisim Hizmetleri A.S.MobileIPv46
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS205906Informatics and Telecommunications Public Company (ITPC)UnclassifiedIPv4119
AS59773Al Ard Al Thahabia Phone & Internet Devices Trading L.L.CUnclassifiedIPv4117

Adjacency

Adjacent networks

All 45

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

ASNetworkTypeFamiliesPaths seen
AS208293AlSalam State CompanyUnclassifiedIPv4 IPv661,847
AS1299Arelion Sweden ABTransitIPv4 IPv621,183
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv68,886
AS3356Level 3 Parent, LLCTransitIPv4 IPv67,116
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv65,173
AS39386Saudi Telecom Company JSCUnclassifiedIPv4 IPv62,512
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv62,086
AS6939Hurricane Electric LLCTransitIPv4 IPv61,578
AS33891Core-Backbone GmbHHostingIPv4838
AS8280SYNAPSECOM S.A. Provider of Telecommunications and Internet ServicesHostingIPv4 IPv6713

All 45 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-21 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.