asn.dev

Observed topology

AS394367 SYSLIFELINE - System Lifeline Inc.

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS394367: 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 IPv6258
AS174Cogent Communications, LLCTransitIPv4 IPv6107
AS577Bell CanadaMobileIPv414
AS22652Videotron LteeResidentialIPv4 IPv611
AS24482SG.GSHostingIPv4 IPv66
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv66
AS1403EBOXResidentialIPv62
AS20473The Constant Company, LLCHostingIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS394786Avetria WirelessUnclassifiedIPv4220
AS32018GET RACKEDHostingIPv4 IPv6161
AS26922SimplyNet Canada Inc.UnclassifiedIPv4 IPv6135

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6515
AS174Cogent Communications, LLCTransitIPv4 IPv6315
AS394786Avetria WirelessUnclassifiedIPv4220
AS32018GET RACKEDHostingIPv4 IPv6161
AS26922SimplyNet Canada Inc.UnclassifiedIPv4 IPv6135
AS22652Videotron LteeResidentialIPv4 IPv628
AS577Bell CanadaMobileIPv419
AS24482SG.GSHostingIPv4 IPv616
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv616
AS1403EBOXResidentialIPv68

All 11 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.