asn.dev

Observed topology

AS11708 LINKCITY

Residential ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS11708: 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
AS32097WholeSale Internet, Inc.HostingIPv4 IPv6154
AS6939Hurricane Electric LLCTransitIPv4 IPv648
AS52025ParadoxNetworks LimitedUnclassifiedIPv42
AS9002RETN LimitedUnclassifiedIPv61
AS24482SG.GSHostingIPv61
AS34927iFog GmbHHostingIPv61
AS394256Tech Futures Interactive Inc.UnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS26199North Kansas City Hospital AuxiliaryUnclassifiedIPv421

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS32097WholeSale Internet, Inc.HostingIPv4 IPv6171
AS6939Hurricane Electric LLCTransitIPv4 IPv648
AS26199North Kansas City Hospital AuxiliaryUnclassifiedIPv421
AS34927iFog GmbHHostingIPv4 IPv62
AS52025ParadoxNetworks LimitedUnclassifiedIPv42
AS9002RETN LimitedUnclassifiedIPv61
AS24482SG.GSHostingIPv61
AS394256Tech Futures Interactive Inc.UnclassifiedIPv61

Provenance

Where this comes from

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