bgpreport

Network · data from 2026-11-12

AS38716 DC West

Registry name: DCWEST-AS-AU-AP - DC West Pty. Ltd., AU · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS38716, 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.
149.18.72.0/24 No ROA Other IRR onlyRADB 670 100% 67
103.16.134.0/23 No ROA RIR databaseAPNIC, RADB 670 100% 67
103.99.240.0/24 No ROA RIR databaseAPNIC, RADB 670 100% 67
103.169.14.0/24 No ROA RIR databaseAPNIC, RADB 670 100% 67
103.169.15.0/24 No ROA RIR databaseAPNIC, RADB 670 100% 67
103.161.227.0/24 Valid RIR databaseAPNIC, RADB 670 100% 67

AS-SET

AS38716'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 22 are in fix.csv.

  • ROA: none5
  • Route object: RIR1
  • Route object: not announced16
ChangePrefix or setDetailFull-table peers
ROA: none149.18.72.0/24No ROA covers it. Add a ROA for AS38716, maxLength 24.670 of 673
Route object: RIR149.18.72.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none103.16.134.0/23No ROA covers it. Add a ROA for AS38716, maxLength 23.670 of 673
ROA: none103.99.240.0/24No ROA covers it. Add a ROA for AS38716, maxLength 24.670 of 673
ROA: none103.169.14.0/24No ROA covers it. Add a ROA for AS38716, maxLength 24.670 of 673
ROA: none103.169.15.0/24No ROA covers it. Add a ROA for AS38716, maxLength 24.670 of 673

Route objects not announced

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

103.9.160.0/22APNIC, RADBNo ROA
103.9.160.0/24APNICNo ROA
103.9.161.0/24APNICNo ROA
103.9.162.0/24APNICNo ROA
103.9.163.0/24APNICNo ROA
103.16.134.0/24APNIC, NTTCOMNo ROA
103.16.135.0/24APNIC, NTTCOMNo ROA
103.169.14.0/23APNIC, RADBNo ROA
103.241.0.0/22APNICValid
103.241.0.0/24APNIC, NTTCOMValid
103.241.1.0/24APNIC, NTTCOMValid
103.241.2.0/24APNIC, NTTCOMValid
103.241.3.0/24APNIC, NTTCOMValid
2001:df5:d480::/48RADBNo ROA
2001:df6:e680::/48APNIC, RADBNo ROA
2402:1300::/36APNICValid

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.