asn.dev

Observed topology

AS40779 VoltNet inc

Unclassified ARIN Route Server

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS40779: 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.

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS401701cognetcloud INCUnclassifiedIPv43,275
AS401696cognetcloud INCUnclassifiedIPv42,684
AS137899I LAYER LIMITEDUnclassifiedIPv42,286
AS35876VoltNet incUnclassifiedIPv4432

Adjacency

Adjacent networks

All 18

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

ASNetworkTypeFamiliesPaths seen
AS2914NTT America, Inc.TransitIPv45,028
AS401701cognetcloud INCUnclassifiedIPv43,547
AS18013ASLINE LIMITEDHostingIPv42,736
AS401696cognetcloud INCUnclassifiedIPv42,684
AS137899I LAYER LIMITEDUnclassifiedIPv42,286
AS137409GSL Networks Pty LTDUnclassifiedIPv4680
AS35876VoltNet incUnclassifiedIPv4432
AS4635Hong Kong Internet Exchange--Route Server 1UnclassifiedIPv4334
AS24482SG.GSHostingIPv478
AS9304HGC Global Communications LimitedHostingIPv472

All 18 adjacent →

Provenance

Where this comes from

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