Network · data from 2026-11-12
AS45152 Zone Networks Managed Hosting Solutions
Registry name: ZoneNetworks-AS-AP - Zone Networks Pty Ltd, Managed Hosting Solutions, AU · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS45152, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 119.82.150.0/24 | No ROA | RIR databaseAPNIC, RADB | 672 100% |
| 122.252.13.0/24 | No ROA | RIR databaseAPNIC, RADB | 672 100% |
| 103.9.56.0/22 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.210.148.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 119.252.184.0/22 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 119.252.188.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 139.5.52.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 103.9.56.0/24 | Valid | RIR databaseAPNIC | 75 11% |
| 103.9.57.0/24 | Valid | RIR databaseAPNIC | 75 11% |
| 103.9.59.0/24 | Valid | RIR databaseAPNIC | 75 11% |
| 103.210.148.0/24 | Valid | RIR databaseAPNIC | 75 11% |
| 103.210.149.0/24 | Valid | RIR databaseAPNIC | 75 11% |
| 119.252.184.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 75 11% |
| 119.252.185.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 75 11% |
| 119.252.186.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 75 11% |
AS-SET
AS45152's PeeringDB record names no AS-SET.
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 17 are in fix.csv.
- ROA: none2
- Route object: not announced15
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 119.82.150.0/24 | No ROA covers it. Add a ROA for AS45152, maxLength 24. |
| ROA: none | 122.252.13.0/24 | No ROA covers it. Add a ROA for AS45152, maxLength 24. |
Route objects not announced
Route objects with origin AS45152 whose prefix no peer sees AS45152 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.9.58.0/24 | APNIC | Valid |
| 103.210.150.0/24 | APNIC | Valid |
| 103.210.151.0/24 | APNIC | Valid |
| 119.82.150.0/23 | RADB | No ROA |
| 119.82.151.0/24 | APNIC | No ROA |
| 119.252.187.0/24 | APNIC, NTTCOM | Valid |
| 122.252.1.0/24 | APNIC | No ROA |
| 122.252.7.0/24 | APNIC | No ROA |
| 122.252.12.0/24 | APNIC | No ROA |
| 139.5.52.0/24 | APNIC | Valid |
| 139.5.53.0/24 | APNIC | Valid |
| 139.5.54.0/24 | APNIC | Valid |
| 139.5.55.0/24 | APNIC | Valid |
| 203.57.45.0/24 | RADB | No ROA |
| 203.132.31.0/24 | NTTCOM | No ROA |
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.