asn.dev

Observed topology

AS23486 NETSPAN

Residential ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS23486: 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
AS174Cogent Communications, LLCTransitIPv4180
AS3491PCCW Global (HK) Ltd.TransitIPv4114
AS6939Hurricane Electric LLCTransitIPv450
AS14907Wikimedia Foundation Inc.HostingIPv46

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS54800Laredo ISDUnclassifiedIPv4116
AS395112Beaumont ISDUnclassifiedIPv432
AS20280Corpus Christi ISDUnclassifiedIPv415
AS26670Mission CISDUnclassifiedIPv415
AS29753Brownsville Independent School DistrictUnclassifiedIPv415
AS393332McAllen Independent School DistrictUnclassifiedIPv415
AS40049Education Service Center, Region 2UnclassifiedIPv413

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4280
AS3491PCCW Global (HK) Ltd.TransitIPv4203
AS54800Laredo ISDUnclassifiedIPv4116
AS6939Hurricane Electric LLCTransitIPv474
AS395112Beaumont ISDUnclassifiedIPv432
AS20280Corpus Christi ISDUnclassifiedIPv415
AS26670Mission CISDUnclassifiedIPv415
AS29753Brownsville Independent School DistrictUnclassifiedIPv415
AS393332McAllen Independent School DistrictUnclassifiedIPv415
AS14907Wikimedia Foundation Inc.HostingIPv414

Provenance

Where this comes from

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