Observed topology

AS11038 SALISH-NETWORKS

Unclassified ARIN

Upstreams 13 carry this network

Downstreams 0 this network carries

Adjacent (IPv4) 13

Adjacent (IPv6) 0

Upstream graph Who carries AS11038, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS11038 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS11038: 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.

AS	Network	Type	Families	Paths seen
AS20055	Wholesail networks LLC	Residential	IPv4	209
AS174	Cogent Communications, LLC	Transit	IPv4	192
AS6939	Hurricane Electric LLC	Transit	IPv4	91
AS11404	Wave Broadband	Residential	IPv4	42
AS9002	RETN Limited	Unclassified	IPv4	25
AS3130	RGnet OU	Unclassified	IPv4	11
AS7575	Australian Academic and Research Network (AARNet)	Education	IPv4	11
AS24482	SG.GS	Hosting	IPv4	11
AS394256	Tech Futures Interactive Inc.	Unclassified	IPv4	11
AS52025	ParadoxNetworks Limited	Unclassified	IPv4	6

All 13 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 13

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

AS	Network	Type	Families	Paths seen
AS20055	Wholesail networks LLC	Residential	IPv4	209
AS174	Cogent Communications, LLC	Transit	IPv4	192
AS6939	Hurricane Electric LLC	Transit	IPv4	91
AS11404	Wave Broadband	Residential	IPv4	42
AS9002	RETN Limited	Unclassified	IPv4	25
AS3130	RGnet OU	Unclassified	IPv4	11
AS7575	Australian Academic and Research Network (AARNet)	Education	IPv4	11
AS24482	SG.GS	Hosting	IPv4	11
AS394256	Tech Futures Interactive Inc.	Unclassified	IPv4	11
AS52025	ParadoxNetworks Limited	Unclassified	IPv4	6

All 13 adjacent →

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.