asn.dev

Observed topology

AS62787 SNARKNET

Residential ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS62787: 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
AS36236NetActuate, IncHostingIPv4 IPv6258
AS37989DCS1 Pte. Ltd.HostingIPv4 IPv69
AS212895Johannes ErnstUnclassifiedIPv46
AS4913410VPN Research Network LTDUnclassifiedIPv43
AS58057Securebit AGUnclassifiedIPv63
AS212508Lowhosting services of Davide GennariUnclassifiedIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS402577SnarkUnclassifiedIPv61

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS36236NetActuate, IncHostingIPv4 IPv6258
AS37989DCS1 Pte. Ltd.HostingIPv4 IPv69
AS212895Johannes ErnstUnclassifiedIPv46
AS4913410VPN Research Network LTDUnclassifiedIPv43
AS58057Securebit AGUnclassifiedIPv63
AS212508Lowhosting services of Davide GennariUnclassifiedIPv43
AS20473The Constant Company, LLCHostingIPv61
AS402577SnarkUnclassifiedIPv61

Provenance

Where this comes from

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