asn.dev

Observed topology

AS59637 ASRSINET

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 12

Networks observed carrying traffic for AS59637: 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
AS42861Foton Telecom CJSCUnclassifiedIPv459
AS12389PJSC RostelecomResidentialIPv452
AS50629LWLcom GmbHUnclassifiedIPv424
AS8732JSC ComcorUnclassifiedIPv412
AS24482SG.GSHostingIPv412
AS25091IP-Max SAUnclassifiedIPv412
AS34927iFog GmbHHostingIPv412
AS37721Virtual Technologies & SolutionsResidentialIPv412
AS20485Joint Stock Company TransTeleComUnclassifiedIPv46
AS3216PJSC "Vimpelcom"MobileIPv44

All 12 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS42861Foton Telecom CJSCUnclassifiedIPv459
AS12389PJSC RostelecomResidentialIPv452
AS50629LWLcom GmbHUnclassifiedIPv424
AS8732JSC ComcorUnclassifiedIPv412
AS24482SG.GSHostingIPv412
AS25091IP-Max SAUnclassifiedIPv412
AS34927iFog GmbHHostingIPv412
AS37721Virtual Technologies & SolutionsResidentialIPv412
AS20485Joint Stock Company TransTeleComUnclassifiedIPv46
AS3216PJSC "Vimpelcom"MobileIPv44

All 12 adjacent →

Provenance

Where this comes from

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