asn.dev

Observed topology

AS40792 -Reserved AS-

Unclassified ARIN NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS40792: 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
AS216211CYBERVERSE LLCHostingIPv628
AS2914NTT America, Inc.TransitIPv68

Transit

Downstream networks

All 39

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

ASNetworkTypeFamiliesPaths seen
AS401615ACCK LLCUnclassifiedIPv4 IPv6236
AS216245CYBERJET PTE. LTD.UnclassifiedIPv4 IPv6141
AS203090BITSFLOWCLOUD LTDUnclassifiedIPv4 IPv6112
AS216211CYBERVERSE LLCHostingIPv4100
AS206069Cornseed LimitedResidentialIPv4 IPv697
AS218737SP NETWORKING, LLCUnclassifiedIPv4 IPv693
AS219401Yeah Tech LLCUnclassifiedIPv473
AS402782TAIPEI101UnclassifiedIPv4 IPv663
AS40929MoeDoveHostingIPv4 IPv657
AS394130StealthByte Network LLCUnclassifiedIPv450

All 39 downstreams →

Adjacency

Adjacent networks

All 42

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

ASNetworkTypeFamiliesPaths seen
AS2914NTT America, Inc.TransitIPv4 IPv61,812
AS206069Cornseed LimitedResidentialIPv4 IPv6293
AS401615ACCK LLCUnclassifiedIPv4 IPv6236
AS216245CYBERJET PTE. LTD.UnclassifiedIPv4 IPv6141
AS216211CYBERVERSE LLCHostingIPv4 IPv6128
AS203090BITSFLOWCLOUD LTDUnclassifiedIPv4 IPv6112
AS218737SP NETWORKING, LLCUnclassifiedIPv4 IPv693
AS219401Yeah Tech LLCUnclassifiedIPv473
AS402782TAIPEI101UnclassifiedIPv4 IPv673
AS40929MoeDoveHostingIPv4 IPv657

All 42 adjacent →

Provenance

Where this comes from

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