Observed topology
AS4851 HOSTNETWORKS-AS-AU-AP - Host Networks
Hosting APNIC Content
Transit
Upstream networks
Networks observed carrying traffic for AS4851: 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 |
|---|---|---|---|---|
| AS63956 | 5G NETWORK OPERATIONS PTY LTD | Unclassified | IPv4 IPv6 | 850 |
Transit
Downstream networks
Networks for which AS4851 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS23727 | Managed Solutions Internet AS Internet Service Provider | Unclassified | IPv4 | 290 |
| AS58929 | Datbury Pty Ltd | Unclassified | IPv4 | 290 |
| AS132498 | ASPEDIA AUSTRALIA PTY LTD | Unclassified | IPv4 | 58 |
| AS150438 | Secure-ISS Holdings Pty Ltd | Unclassified | IPv4 | 58 |
| AS139279 | OPTIMISED SOLUTIONS | Unclassified | IPv4 IPv6 | 25 |
| AS56057 | Entity Data Pty Limited | Unclassified | IPv4 | 19 |
| AS198125 | Jacob Ian Wicks Trading as CONXT | Unclassified | IPv4 | 14 |
Adjacency
Adjacent networks
Every AS seen directly next to AS4851 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS63956 | 5G NETWORK OPERATIONS PTY LTD | Unclassified | IPv4 IPv6 | 1,603 |
| AS23727 | Managed Solutions Internet AS Internet Service Provider | Unclassified | IPv4 | 290 |
| AS58929 | Datbury Pty Ltd | Unclassified | IPv4 | 290 |
| AS132498 | ASPEDIA AUSTRALIA PTY LTD | Unclassified | IPv4 | 58 |
| AS150438 | Secure-ISS Holdings Pty Ltd | Unclassified | IPv4 | 58 |
| AS139279 | OPTIMISED SOLUTIONS | Unclassified | IPv4 IPv6 | 25 |
| AS56057 | Entity Data Pty Limited | Unclassified | IPv4 | 19 |
| AS198125 | Jacob Ian Wicks Trading as CONXT | Unclassified | IPv4 | 14 |
| AS4764 | Aussie Broadband | Residential | IPv4 | 1 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-02 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.44M 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.