asn.dev

Observed topology

AS51032 NEVOD-AS

Residential RIPE

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

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS51032: 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
AS31133PJSC MegaFonMobileIPv4 IPv6230
AS3216PJSC "Vimpelcom"MobileIPv4 IPv6222
AS6939Hurricane Electric LLCTransitIPv4100
AS50509Transroute Telecom LTDUnclassifiedIPv460
AS41344Vist on-line LTDUnclassifiedIPv457
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv4 IPv613
AS24482SG.GSHostingIPv4 IPv612
AS50673Serverius Holding B.V.UnclassifiedIPv412
AS49673Truenetwork LLCUnclassifiedIPv411
AS8218Zayo Infrastructure France SAUnclassifiedIPv410

All 13 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS39707LLC POWERNETUnclassifiedIPv4122

Adjacency

Adjacent networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS3216PJSC "Vimpelcom"MobileIPv4 IPv6280
AS31133PJSC MegaFonMobileIPv4 IPv6256
AS39707LLC POWERNETUnclassifiedIPv4122
AS6939Hurricane Electric LLCTransitIPv4118
AS50509Transroute Telecom LTDUnclassifiedIPv468
AS41344Vist on-line LTDUnclassifiedIPv457
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv4 IPv615
AS24482SG.GSHostingIPv4 IPv614
AS50673Serverius Holding B.V.UnclassifiedIPv414
AS49673Truenetwork LLCUnclassifiedIPv413

All 14 adjacent →

Provenance

Where this comes from

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