asn.dev

Observed topology

AS4474 TCT-AS - TCT West, Inc.

Residential ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS4474: 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 IPv6534
AS1299Arelion Sweden ABTransitIPv4 IPv698
AS6461Zayo BandwidthTransitIPv4 IPv674
AS174Cogent Communications, LLCTransitIPv4 IPv657
AS24482SG.GSHostingIPv4 IPv613
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv613
AS3130RGnet OUUnclassifiedIPv412
AS34927iFog GmbHHostingIPv411

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS30211Gallatin Wireless Internet, LLCUnclassifiedIPv4 IPv6359
AS397324Gallatin Wireless Internet, LLCUnclassifiedIPv4 IPv6330
AS40943Rural Broadband, L.L.C.UnclassifiedIPv4 IPv6134

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv61,100
AS30211Gallatin Wireless Internet, LLCUnclassifiedIPv4 IPv6359
AS397324Gallatin Wireless Internet, LLCUnclassifiedIPv4 IPv6330
AS1299Arelion Sweden ABTransitIPv4 IPv6175
AS6461Zayo BandwidthTransitIPv4 IPv6144
AS40943Rural Broadband, L.L.C.UnclassifiedIPv4 IPv6134
AS174Cogent Communications, LLCTransitIPv4 IPv6117
AS24482SG.GSHostingIPv4 IPv628
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv628
AS3130RGnet OUUnclassifiedIPv423

All 11 adjacent →

Provenance

Where this comes from

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