asn.dev

Observed topology

AS14401 SOLIDNETWORK-AS-02 - SolidNetwork Technologies, Inc.

Hosting ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS14401: 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 IPv6286
AS1299Arelion Sweden ABTransitIPv4 IPv664
AS24482SG.GSHostingIPv4 IPv66
AS17639Converge ICT Solutions Inc.UnclassifiedIPv45

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS36221Esosoft CorporationUnclassifiedIPv4 IPv6628
AS398032CHEROKEE-COMMUNICATIONSUnclassifiedIPv4 IPv6159
AS402898ppflightUnclassifiedIPv64

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6963
AS36221Esosoft CorporationUnclassifiedIPv4 IPv6628
AS1299Arelion Sweden ABTransitIPv4 IPv6173
AS398032CHEROKEE-COMMUNICATIONSUnclassifiedIPv4 IPv6159
AS24482SG.GSHostingIPv4 IPv69
AS17639Converge ICT Solutions Inc.UnclassifiedIPv47
AS402898ppflightUnclassifiedIPv64

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.