asn.dev

Observed topology

AS18988 CITYWEST-CORP

Residential ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS18988: 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 IPv61,153
AS174Cogent Communications, LLCTransitIPv4 IPv6583
AS6461Zayo BandwidthTransitIPv4222
AS22652Videotron LteeResidentialIPv462
AS24482SG.GSHostingIPv4 IPv631
AS394256Tech Futures Interactive Inc.UnclassifiedIPv431
AS3130RGnet OUUnclassifiedIPv430
AS9002RETN LimitedUnclassifiedIPv423
AS34927iFog GmbHHostingIPv46

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS32204KPU TelecommunicationsResidentialIPv42,442
AS27256Cybernet Communications LtdUnclassifiedIPv466
AS398157TECH NORTH SOLUTIONS INCUnclassifiedIPv466
AS54904Evolve Communications IncUnclassifiedIPv632

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv62,933
AS32204KPU TelecommunicationsResidentialIPv42,442
AS174Cogent Communications, LLCTransitIPv4 IPv6969
AS6461Zayo BandwidthTransitIPv4467
AS22652Videotron LteeResidentialIPv4140
AS24482SG.GSHostingIPv4 IPv670
AS394256Tech Futures Interactive Inc.UnclassifiedIPv470
AS3130RGnet OUUnclassifiedIPv469
AS27256Cybernet Communications LtdUnclassifiedIPv466
AS398157TECH NORTH SOLUTIONS INCUnclassifiedIPv466

All 13 adjacent →

Provenance

Where this comes from

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