asn.dev

Observed topology

AS62913 SPEEDYNET

Unclassified ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS62913: 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
AS1299Arelion Sweden ABTransitIPv4 IPv6197
AS23520Columbus Networks USA, Inc.ResidentialIPv4 IPv653
AS6939Hurricane Electric LLCTransitIPv445
AS10396DATACOM CARIBE, INC.ResidentialIPv4 IPv611
AS3303Swisscom (Schweiz) AGResidentialIPv45
AS24482SG.GSHostingIPv45
AS11992Liberty Mobile Puerto Rico Inc.UnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS398244EchoNetUnclassifiedIPv458
AS21944VelocityNet PRUnclassifiedIPv48

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6244
AS23520Columbus Networks USA, Inc.ResidentialIPv4 IPv665
AS398244EchoNetUnclassifiedIPv458
AS6939Hurricane Electric LLCTransitIPv445
AS10396DATACOM CARIBE, INC.ResidentialIPv4 IPv616
AS21944VelocityNet PRUnclassifiedIPv48
AS3303Swisscom (Schweiz) AGResidentialIPv45
AS24482SG.GSHostingIPv45
AS11992Liberty Mobile Puerto Rico Inc.UnclassifiedIPv4 IPv63

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.