asn.dev

Observed topology

AS39561 AS-REGRU "Domain names registrar REG.RU", Ltd

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS39561: 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
AS59692IQWeb FZ-LLCUnclassifiedIPv456
AS57724DDOS-GUARD LTDUnclassifiedIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS197695"Domain names registrar REG.RU", LtdHostingIPv4 IPv69,189
AS49352"Domain names registrar REG.RU", LtdUnclassifiedIPv41,598
AS205952LLC "ASTRA CLOUD"UnclassifiedIPv458

Adjacency

Adjacent networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS197695"Domain names registrar REG.RU", LtdHostingIPv4 IPv69,574
AS202984Chernyshov Aleksandr AleksandrovichUnclassifiedIPv45,694
AS57724DDOS-GUARD LTDUnclassifiedIPv4 IPv61,959
AS49352"Domain names registrar REG.RU", LtdUnclassifiedIPv4 IPv61,658
AS59692IQWeb FZ-LLCUnclassifiedIPv4 IPv61,517
AS6939Hurricane Electric LLCTransitIPv41,071
AS201706SERVICEPIPE LLCUnclassifiedIPv4471
AS5537JSC "RU-CENTER"HostingIPv4393
AS43298Storm Networks LLCUnclassifiedIPv4385
AS59796StormWall s.r.o.UnclassifiedIPv4364

All 14 adjacent →

Provenance

Where this comes from

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