Observed topology
AS7489 HOSTUS-GLOBAL-AS - HostUS
Hosting APNIC
Transit
Upstream networks
Networks observed carrying traffic for AS7489: 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 |
|---|---|---|---|---|
| AS40676 | Psychz Networks | Hosting | IPv4 IPv6 | 1,954 |
| AS29802 | HIVELOCITY, Inc. | Hosting | IPv4 IPv6 | 1,340 |
| AS42831 | UK Dedicated Servers Limited | Hosting | IPv4 IPv6 | 600 |
| AS35200 | TransitX Ltd | Unclassified | IPv4 | 405 |
| AS136557 | Host Universal Pty Ltd | Unclassified | IPv4 IPv6 | 398 |
| AS49870 | Alsycon B.V. | Hosting | IPv4 IPv6 | 150 |
| AS41095 | IPTP LTD | Hosting | IPv4 IPv6 | 149 |
| AS22653 | Cyber Wurx LLC | Hosting | IPv4 IPv6 | 148 |
| AS140951 | IPTP Networks | Unclassified | IPv4 | 2 |
Transit
Downstream networks
Networks for which AS7489 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS132647 | Pengelola Nama Domain Internet Indonesia | Unclassified | IPv4 | 4 |
Adjacency
Adjacent networks
Every AS seen directly next to AS7489 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS40676 | Psychz Networks | Hosting | IPv4 IPv6 | 1,954 |
| AS29802 | HIVELOCITY, Inc. | Hosting | IPv4 IPv6 | 1,340 |
| AS42831 | UK Dedicated Servers Limited | Hosting | IPv4 IPv6 | 600 |
| AS35200 | TransitX Ltd | Unclassified | IPv4 | 405 |
| AS136557 | Host Universal Pty Ltd | Unclassified | IPv4 IPv6 | 398 |
| AS41095 | IPTP LTD | Hosting | IPv4 IPv6 | 153 |
| AS49870 | Alsycon B.V. | Hosting | IPv4 IPv6 | 150 |
| AS22653 | Cyber Wurx LLC | Hosting | IPv4 IPv6 | 148 |
| AS132647 | Pengelola Nama Domain Internet Indonesia | Unclassified | IPv4 | 4 |
| AS140951 | IPTP Networks | Unclassified | IPv4 | 2 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.00M 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.