Observed topology
AS56030 VOYAGERNET-AS-AP - Voyager Internet Ltd.
Unclassified APNIC NSP
Transit
Upstream networks
Networks observed carrying traffic for AS56030: 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.
Transit
Downstream networks
Networks for which AS56030 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS9245 | COMPASS NZ | Residential | IPv4 IPv6 | 539 |
| AS139580 | RIMU HOSTING LIMITED | Unclassified | IPv4 IPv6 | 419 |
| AS134110 | MiIT Limited | Unclassified | IPv4 | 320 |
| AS132692 | GlobiCom Limited | Unclassified | IPv4 IPv6 | 298 |
| AS38437 | Wicked Networks | Residential | IPv4 IPv6 | 285 |
| AS18400 | Xtreme Networks Limited | Unclassified | IPv4 IPv6 | 216 |
| AS140870 | Accelerate Wireless Limited | Unclassified | IPv4 | 126 |
| AS139054 | Auckland Data Centre Limited | Unclassified | IPv4 IPv6 | 99 |
| AS137262 | InTune Technologies Limited | Unclassified | IPv4 IPv6 | 97 |
| AS132697 | Accelero Limited | Unclassified | IPv4 | 64 |
Adjacency
Adjacent networks
Every AS seen directly next to AS56030 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS9790 | Two Degrees Networks Limited | Residential | IPv4 IPv6 | 5,267 |
| AS4648 | Global-Gateway Internet | Unclassified | IPv4 IPv6 | 1,549 |
| AS18400 | Xtreme Networks Limited | Unclassified | IPv4 IPv6 | 1,460 |
| AS9245 | COMPASS NZ | Residential | IPv4 IPv6 | 1,247 |
| AS139580 | RIMU HOSTING LIMITED | Unclassified | IPv4 IPv6 | 419 |
| AS134110 | MiIT Limited | Unclassified | IPv4 | 320 |
| AS132692 | GlobiCom Limited | Unclassified | IPv4 IPv6 | 298 |
| AS38437 | Wicked Networks | Residential | IPv4 IPv6 | 285 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 127 |
| AS140870 | Accelerate Wireless Limited | Unclassified | IPv4 | 126 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-07 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 72.97M 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.