Observed topology
AS23089 HOTWIRE-COMMUNICATIONS - Hotwire Communications
Unclassified ARIN NSP
Transit
Upstream networks
Networks observed carrying traffic for AS23089: 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 |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 17,926 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 11,758 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 6,222 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 1,844 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 338 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 | 323 |
| AS9304 | HGC Global Communications Limited | Hosting | IPv4 | 277 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 | 9 |
Transit
Downstream networks
Networks for which AS23089 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS62622 | Hotwire Communications | Unclassified | IPv4 | 528 |
| AS17082 | SMART CITY NETWORKS, LIMITED PARTNERSHIP | Unclassified | IPv4 | 355 |
| AS396260 | FONTAINEBLEAU-MIAMI-BEACH | Unclassified | IPv4 | 132 |
| AS62954 | Walser Technology Group Inc. | Unclassified | IPv4 | 118 |
| AS402211 | UNIVERSAL HEALTH SERVICES | Unclassified | IPv4 | 62 |
| AS18698 | Icahn Associates Corp. | Unclassified | IPv4 | 42 |
| AS26903 | City of Salisbury, North Carolina | Unclassified | IPv4 | 8 |
Adjacency
Adjacent networks
Every AS seen directly next to AS23089 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 18,685 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 11,954 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 6,471 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 1,844 |
| AS62622 | Hotwire Communications | Unclassified | IPv4 | 528 |
| AS17082 | SMART CITY NETWORKS, LIMITED PARTNERSHIP | Unclassified | IPv4 | 355 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 355 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 | 339 |
| AS9304 | HGC Global Communications Limited | Hosting | IPv4 | 285 |
| AS396260 | FONTAINEBLEAU-MIAMI-BEACH | Unclassified | IPv4 | 132 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-01 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.48M 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.