asn.dev

Observed topology

AS60062 ThreeDATA-AS 3DATA LLC

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS60062: 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
AS29226JSC MastertelUnclassifiedIPv4132
AS57304JSC "RetnNet"UnclassifiedIPv4111
AS201706SERVICEPIPE LLCUnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS207634Digital Link Limited Liability CompanyUnclassifiedIPv419
AS212620RusGazShelf LLCUnclassifiedIPv412

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS29226JSC MastertelUnclassifiedIPv4153
AS57304JSC "RetnNet"UnclassifiedIPv4121
AS207634Digital Link Limited Liability CompanyUnclassifiedIPv419
AS212620RusGazShelf LLCUnclassifiedIPv412
AS201706SERVICEPIPE LLCUnclassifiedIPv41

Provenance

Where this comes from

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