bgpreport

Network · data from 2026-11-12

AS9667 Hostworks

Registry name: HOSTWORKS-AS-AP - 5G NETWORK OPERATIONS PTY LTD, AU · PeeringDB

8IPv4 routes 100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
0No ROA 0 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
79Route objects not announced registered with origin AS9667, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS9667, 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.
202.58.32.0/19 Valid RIR databaseAPNIC 673 100% 67
202.58.34.0/23 Valid RIR databaseAPNIC 671 100% 67
202.58.40.0/22 Valid RIR databaseAPNIC 671 100% 67
202.58.45.0/24 Valid RIR databaseAPNIC 671 100% 67
202.58.48.0/24 Valid RIR databaseAPNIC 671 100% 67
202.58.56.0/24 Valid RIR databaseAPNIC 671 100% 67
202.58.63.0/24 Valid RIR databaseAPNIC 671 100% 67
180.94.113.0/24 Valid RIR databaseAPNIC, RADB 2 0%low visibility 2

AS-SET

AS9667'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 79 are in fix.csv.

  • Route object: not announced79

Route objects not announced

Route objects with origin AS9667 whose prefix no peer sees AS9667 announce. Many are kept on purpose (backup routes, space announced only in some places).

103.20.208.0/24APNIC, RADBValid
103.20.209.0/24APNIC, RADBValid
103.20.210.0/24APNIC, RADBValid
103.20.211.0/24APNIC, RADBValid
103.21.108.0/22RADBNo ROA
103.21.109.0/24RADBNo ROA
103.21.110.0/24RADBNo ROA
103.21.111.0/24RADBNo ROA
180.94.112.0/22APNICValid
180.94.112.0/23APNICValid
180.94.112.0/24APNIC, RADBValid
180.94.114.0/23APNICValid
180.94.114.0/24APNIC, RADBValid
180.94.115.0/24APNIC, RADBValid
180.94.116.0/22APNICValid
180.94.116.0/23APNICValid
180.94.116.0/24APNIC, RADBValid
180.94.117.0/24APNIC, RADBValid
180.94.118.0/23APNICValid
180.94.118.0/24APNIC, RADBValid
180.94.119.0/24APNIC, RADBValid
202.14.134.0/24RADBNo ROA
202.58.32.0/20APNICValid
202.58.32.0/21APNICValid
202.58.32.0/22APNICValid
202.58.32.0/23APNICValid
202.58.32.0/24APNICValid
202.58.33.0/24APNICValid
202.58.34.0/24APNICValid
202.58.35.0/24APNICValid
202.58.36.0/22APNICValid
202.58.36.0/23APNICValid
202.58.36.0/24APNICValid
202.58.37.0/24APNICValid
202.58.38.0/23APNICValid
202.58.38.0/24APNICValid
202.58.39.0/24APNICValid
202.58.40.0/21APNICValid
202.58.40.0/23APNICValid
202.58.40.0/24APNICValid
202.58.41.0/24APNICValid
202.58.42.0/23APNICValid
202.58.42.0/24APNICValid
202.58.43.0/24APNICValid
202.58.44.0/22APNICValid
202.58.44.0/23APNICValid
202.58.44.0/24APNICValid
202.58.46.0/23APNICValid
202.58.46.0/24APNICValid
202.58.47.0/24APNICValid
202.58.48.0/20APNICValid
202.58.48.0/21APNICValid
202.58.48.0/22APNICValid
202.58.48.0/23APNICValid
202.58.49.0/24APNICValid
202.58.50.0/23APNICValid
202.58.50.0/24APNICValid
202.58.51.0/24APNICValid
202.58.52.0/22APNICValid
202.58.52.0/23APNICValid
202.58.52.0/24APNICValid
202.58.53.0/24APNICValid
202.58.54.0/23APNICValid
202.58.54.0/24APNICValid
202.58.55.0/24APNICValid
202.58.56.0/21APNICValid
202.58.56.0/22APNICValid
202.58.56.0/23APNICValid
202.58.57.0/24APNICValid
202.58.58.0/23APNICValid
202.58.58.0/24APNICValid
202.58.59.0/24APNICValid
202.58.60.0/22APNICValid
202.58.60.0/23APNICValid
202.58.60.0/24APNICValid
202.58.61.0/24APNICValid
202.58.62.0/23APNICValid
202.58.62.0/24APNICValid
203.6.251.0/24RADBNo 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.