asn.dev

Observed topology

AS10423 SPARTAN-NET

Residential ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS10423: 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 IPv6126
AS12129123.Net, Inc.HostingIPv4 IPv614
AS174Cogent Communications, LLCTransitIPv4 IPv612
AS1299Arelion Sweden ABTransitIPv4 IPv69
AS24482SG.GSHostingIPv4 IPv63
AS20205Amplex Electric, Inc.ResidentialIPv42
AS37721Virtual Technologies & SolutionsResidentialIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS33414Kent County Information SystemsUnclassifiedIPv476

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6174
AS33414Kent County Information SystemsUnclassifiedIPv476
AS12129123.Net, Inc.HostingIPv4 IPv625
AS174Cogent Communications, LLCTransitIPv4 IPv619
AS1299Arelion Sweden ABTransitIPv4 IPv615
AS24482SG.GSHostingIPv4 IPv65
AS37721Virtual Technologies & SolutionsResidentialIPv44
AS20205Amplex Electric, Inc.ResidentialIPv42

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-30 10:00 UTC by route-views2,rrc00, as seen from 76 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.