asn.dev

Observed topology

AS40966 L7GUARD-AS ZAO Web Hosting

Hosting RIPE Content

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS40966: 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
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4280
AS30943ZAO Web HostingUnclassifiedIPv4199
AS12389PJSC RostelecomResidentialIPv447
AS3216PJSC "Vimpelcom"MobileIPv437
AS6939Hurricane Electric LLCTransitIPv424
AS24482SG.GSHostingIPv44
AS34927iFog GmbHHostingIPv44
AS37721Virtual Technologies & SolutionsResidentialIPv44
AS49673Truenetwork LLCUnclassifiedIPv44
AS50673Serverius Holding B.V.UnclassifiedIPv44

All 11 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS63258Web Hosting, Inc.UnclassifiedIPv4250
AS30943ZAO Web HostingUnclassifiedIPv450

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4580
AS63258Web Hosting, Inc.UnclassifiedIPv4250
AS30943ZAO Web HostingUnclassifiedIPv4249
AS12389PJSC RostelecomResidentialIPv447
AS3216PJSC "Vimpelcom"MobileIPv437
AS6939Hurricane Electric LLCTransitIPv424
AS24482SG.GSHostingIPv44
AS34927iFog GmbHHostingIPv44
AS37721Virtual Technologies & SolutionsResidentialIPv44
AS49673Truenetwork LLCUnclassifiedIPv44

All 12 adjacent →

Provenance

Where this comes from

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