Observed topology
AS139077 FREEDOMINTERNET-HPL-AS-AP - FREEDOM INTERNET HOLDINGS PTY LTD
Residential APNIC Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS139077: 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 |
|---|---|---|---|---|
| AS49915 | Megaport (UK) Limited | Unclassified | IPv4 IPv6 | 506 |
| AS7594 | On Q | Unclassified | IPv4 | 208 |
| AS9507 | NextHop Pty Ltd | Unclassified | IPv4 | 114 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 86 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 20 |
| AS64073 | Vetta Group | Unclassified | IPv4 IPv6 | 16 |
| AS4608 | Asia Pacific Network Information Centre | Unclassified | IPv4 | 10 |
Transit
Downstream networks
Networks for which AS139077 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS138657 | MarchNet | Unclassified | IPv4 | 10 |
Adjacency
Adjacent networks
Every AS seen directly next to AS139077 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS49915 | Megaport (UK) Limited | Unclassified | IPv4 IPv6 | 506 |
| AS7594 | On Q | Unclassified | IPv4 | 244 |
| AS9507 | NextHop Pty Ltd | Unclassified | IPv4 | 120 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 86 |
| AS138657 | MarchNet | Unclassified | IPv4 | 43 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 20 |
| AS64073 | Vetta Group | Unclassified | IPv4 IPv6 | 16 |
| AS4608 | Asia Pacific Network Information Centre | Unclassified | IPv4 | 11 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-12 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.36M 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.