asn.dev

Observed topology

AS57045 NGS Panin Kirill Evgenyevich

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS57045: 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
AS9049JSC "ER-Telecom Holding"UnclassifiedIPv4 IPv6129
AS50384iHome LLCUnclassifiedIPv448
AS6939Hurricane Electric LLCTransitIPv440
AS197275Link Telecom NN Ltd.UnclassifiedIPv428
AS8218Zayo Infrastructure France SAUnclassifiedIPv44
AS24482SG.GSHostingIPv44
AS37721Virtual Technologies & SolutionsResidentialIPv44
AS49673Truenetwork LLCUnclassifiedIPv44
AS50673Serverius Holding B.V.UnclassifiedIPv44
AS56655Gigahost ASUnclassifiedIPv44

All 11 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS57193RUWEB-NN LLCUnclassifiedIPv4118
AS57629LLC IVI.RUHostingIPv633
AS198932CEK, LLCUnclassifiedIPv422

Adjacency

Adjacent networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS9049JSC "ER-Telecom Holding"UnclassifiedIPv4 IPv6210
AS57193RUWEB-NN LLCUnclassifiedIPv4118
AS50384iHome LLCUnclassifiedIPv471
AS6939Hurricane Electric LLCTransitIPv468
AS197275Link Telecom NN Ltd.UnclassifiedIPv449
AS57629LLC IVI.RUHostingIPv633
AS198932CEK, LLCUnclassifiedIPv422
AS24482SG.GSHostingIPv47
AS37721Virtual Technologies & SolutionsResidentialIPv47
AS49673Truenetwork LLCUnclassifiedIPv47

All 14 adjacent →

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.