Observed topology
AS45577 INTERVOLVE-MELBOURNE-AS-AP - Intervolve Pty Ltd
Unclassified APNIC
Transit
Upstream networks
Networks observed carrying traffic for AS45577: 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 |
|---|---|---|---|---|
| AS4826 | Vocus Connect International Backbone | Unclassified | IPv4 IPv6 | 1,729 |
| AS133934 | AUS IT SERVICES PTY LTD | Unclassified | IPv4 | 1,229 |
| AS7551 | Cloud Central Pty Ltd | Hosting | IPv4 | 629 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 523 |
| AS45671 | Wholesale Services Provider | Unclassified | IPv4 | 96 |
| AS24482 | SG.GS | Hosting | IPv4 | 18 |
| AS64073 | Vetta Group | Unclassified | IPv4 | 18 |
Transit
Downstream networks
Networks for which AS45577 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS10207 | Intervolve Pty Ltd | Hosting | IPv4 IPv6 | 1,262 |
Adjacency
Adjacent networks
Every AS seen directly next to AS45577 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS4826 | Vocus Connect International Backbone | Unclassified | IPv4 IPv6 | 1,814 |
| AS10207 | Intervolve Pty Ltd | Hosting | IPv4 IPv6 | 1,262 |
| AS133934 | AUS IT SERVICES PTY LTD | Unclassified | IPv4 | 1,229 |
| AS7551 | Cloud Central Pty Ltd | Hosting | IPv4 | 934 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 733 |
| AS2764 | AAPT Limited | Unclassified | IPv4 IPv6 | 661 |
| AS45671 | Wholesale Services Provider | Unclassified | IPv4 | 96 |
| AS24482 | SG.GS | Hosting | IPv4 | 18 |
| AS64073 | Vetta Group | Unclassified | IPv4 | 18 |
| AS7575 | Australian Academic and Research Network (AARNet) | Education | IPv4 | 1 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-04 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.33M 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.