asn.dev

Observed topology

AS17017 AS-CAMPUSCOLO

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS17017: 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
AS20055Wholesail networks LLCResidentialIPv4 IPv6160
AS6939Hurricane Electric LLCTransitIPv4 IPv649
AS11404Wave BroadbandResidentialIPv4 IPv625
AS9002RETN LimitedUnclassifiedIPv4 IPv69
AS24482SG.GSHostingIPv4 IPv65
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv65
AS3130RGnet OUUnclassifiedIPv44
AS7575Australian Academic and Research Network (AARNet)EducationIPv44
AS34927iFog GmbHHostingIPv44

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS399951Archous Networks Inc.UnclassifiedIPv4171
AS26695Cubed Networks LLCUnclassifiedIPv4 IPv6153

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS20055Wholesail networks LLCResidentialIPv4 IPv6436
AS399951Archous Networks Inc.UnclassifiedIPv4171
AS26695Cubed Networks LLCUnclassifiedIPv4 IPv6153
AS11404Wave BroadbandResidentialIPv4 IPv673
AS6939Hurricane Electric LLCTransitIPv4 IPv649
AS9002RETN LimitedUnclassifiedIPv4 IPv69
AS24482SG.GSHostingIPv4 IPv65
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv65
AS3130RGnet OUUnclassifiedIPv44
AS7575Australian Academic and Research Network (AARNet)EducationIPv44

All 11 adjacent →

Provenance

Where this comes from

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