asn.dev

Observed topology

AS16417 IRONPORT-SYSTEMS-INC

Unclassified ARIN

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS16417: 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
AS12182Unitas GlobalHostingIPv4 IPv61,296
AS23005SWITCH, LTDUnclassifiedIPv4 IPv61,251
AS22911SINAP-TIX, LLCUnclassifiedIPv4 IPv61,146
AS174Cogent Communications, LLCTransitIPv4 IPv61,098
AS15830Equinix (EMEA) Acquisition Enterprises B.V.HostingIPv4 IPv6792
AS6939Hurricane Electric LLCTransitIPv4 IPv6687
AS6327Shaw CommunicationsResidentialIPv4 IPv6231
AS209CenturyLink Communications, LLCResidentialIPv4 IPv6228
AS24482SG.GSHostingIPv440
AS22652Videotron LteeResidentialIPv44

All 11 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS40427Cisco Systems Ironport DivisionUnclassifiedIPv4118

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS12182Unitas GlobalHostingIPv4 IPv61,296
AS23005SWITCH, LTDUnclassifiedIPv4 IPv61,283
AS22911SINAP-TIX, LLCUnclassifiedIPv4 IPv61,173
AS174Cogent Communications, LLCTransitIPv4 IPv61,131
AS15830Equinix (EMEA) Acquisition Enterprises B.V.HostingIPv4 IPv6811
AS6939Hurricane Electric LLCTransitIPv4 IPv6687
AS209CenturyLink Communications, LLCResidentialIPv4 IPv6235
AS6327Shaw CommunicationsResidentialIPv4 IPv6231
AS40427Cisco Systems Ironport DivisionUnclassifiedIPv4118
AS24482SG.GSHostingIPv440

All 12 adjacent →

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.