asn.dev

Observed topology

AS41704 OGS-AS JSC "Ufanet"

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS41704: 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
AS47775JSC "Ufanet"UnclassifiedIPv41,680
AS31133PJSC MegaFonMobileIPv4 IPv61,530
AS3216PJSC "Vimpelcom"MobileIPv4 IPv61,136

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS200401Kazakov Aleksey AlexandrovichUnclassifiedIPv458
AS219201Sistema Gorod JSCUnclassifiedIPv458
AS57629LLC IVI.RUHostingIPv636
AS50284Goroshko Evgeniy AndreevichUnclassifiedIPv415
AS34085PJSC NICO-BANKUnclassifiedIPv45

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS47775JSC "Ufanet"UnclassifiedIPv41,680
AS31133PJSC MegaFonMobileIPv4 IPv61,635
AS3216PJSC "Vimpelcom"MobileIPv4 IPv61,203
AS200401Kazakov Aleksey AlexandrovichUnclassifiedIPv458
AS219201Sistema Gorod JSCUnclassifiedIPv458
AS57629LLC IVI.RUHostingIPv636
AS50284Goroshko Evgeniy AndreevichUnclassifiedIPv415
AS34085PJSC NICO-BANKUnclassifiedIPv45

Provenance

Where this comes from

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