asn.dev

Observed topology

AS13319 S-I-S - Storm Internet Services

Residential ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS13319: 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 IPv61,240
AS174Cogent Communications, LLCTransitIPv4 IPv6262
AS577Bell CanadaMobileIPv4160
AS22652Videotron LteeResidentialIPv4 IPv650
AS24482SG.GSHostingIPv4 IPv628
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv628
AS1403EBOXResidentialIPv612
AS20473The Constant Company, LLCHostingIPv66

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS26227Sandelman Software Works CorporationUnclassifiedIPv4 IPv6168

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv61,366
AS174Cogent Communications, LLCTransitIPv4 IPv6290
AS26227Sandelman Software Works CorporationUnclassifiedIPv4 IPv6168
AS577Bell CanadaMobileIPv4160
AS22652Videotron LteeResidentialIPv4 IPv655
AS24482SG.GSHostingIPv4 IPv631
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv631
AS1403EBOXResidentialIPv614
AS20473The Constant Company, LLCHostingIPv67

Provenance

Where this comes from

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