asn.dev

Observed topology

AS396097 SAIL-INET - Sail Internet, Inc.

Residential ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS396097: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6898
AS6461Zayo BandwidthTransitIPv4 IPv6267
AS174Cogent Communications, LLCTransitIPv4 IPv6113
AS24482SG.GSHostingIPv4 IPv621
AS17639Converge ICT Solutions Inc.UnclassifiedIPv419

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS63450Ether Web Network, Inc.UnclassifiedIPv41,686
AS401484Astera LabsUnclassifiedIPv451

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS63450Ether Web Network, Inc.UnclassifiedIPv41,686
AS6939Hurricane Electric LLCTransitIPv4 IPv61,378
AS174Cogent Communications, LLCTransitIPv4 IPv61,250
AS6461Zayo BandwidthTransitIPv4 IPv6307
AS401484Astera LabsUnclassifiedIPv451
AS24482SG.GSHostingIPv4 IPv649
AS17639Converge ICT Solutions Inc.UnclassifiedIPv447
AS7575Australian Academic and Research Network (AARNet)EducationIPv424

Provenance

Where this comes from

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