asn.dev

Observed topology

AS17088 CURRENEX

Hosting ARIN Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS17088: 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
AS701Verizon BusinessResidentialIPv4727
AS3356Level 3 Parent, LLCTransitIPv4532
AS46887Crown Castle Fiber LLCUnclassifiedIPv4390
AS15830Equinix (EMEA) Acquisition Enterprises B.V.HostingIPv4250
AS10021KVH Co.,LtdUnclassifiedIPv4178
AS4713NTT DOCOMO BUSINESS,Inc.ResidentialIPv475
AS8220COLT Technology Services Group LimitedHostingIPv458
AS37100SEACOM LimitedUnclassifiedIPv44
AS48362Stadtwerke FeldkirchResidentialIPv44
AS50304Blix Solutions ASUnclassifiedIPv44

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS36102State Street Bank and Trust CompanyUnclassifiedIPv44

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS701Verizon BusinessResidentialIPv4731
AS3356Level 3 Parent, LLCTransitIPv4532
AS46887Crown Castle Fiber LLCUnclassifiedIPv4390
AS15830Equinix (EMEA) Acquisition Enterprises B.V.HostingIPv4250
AS10021KVH Co.,LtdUnclassifiedIPv4178
AS4713NTT DOCOMO BUSINESS,Inc.ResidentialIPv475
AS8220COLT Technology Services Group LimitedHostingIPv458
AS36102State Street Bank and Trust CompanyUnclassifiedIPv44
AS37100SEACOM LimitedUnclassifiedIPv44
AS48362Stadtwerke FeldkirchResidentialIPv44

All 11 adjacent →

Provenance

Where this comes from

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