bgpreport

Network · data from 2026-11-12

AS17461 DPWSAU-AP - NSW Department of Commerce

Registry name: DPWSAU-AP - NSW Department of Commerce, AU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS17461, 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.
203.3.220.0/22 No ROA Other origin only 672 100% 67
203.3.232.0/22 No ROA Other origin only 672 100% 67
103.52.1.0/24 No ROA Other IRR onlyRADB 672 100% 67
103.224.160.0/24 No ROA Other IRR onlyRADB 672 100% 67
203.3.232.0/24 No ROA Other IRR onlyRADB 672 100% 67
203.3.237.0/24 Valid RIR databaseAPNIC 673 100% 70
143.119.160.0/24 Valid RIR databaseAPNIC 672 100% 67
143.119.161.0/24 Valid RIR databaseAPNIC 672 100% 67
143.119.162.0/24 Valid RIR databaseAPNIC 672 100% 67
143.119.163.0/24 Valid RIR databaseAPNIC 672 100% 67

AS-SET

AS17461 isn't in PeeringDB, where networks name their 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 24 are in fix.csv.

  • ROA: none5
  • Route object: none2
  • Route object: RIR3
  • Route object: not announced14
ChangePrefix or setDetailFull-table peers
ROA: none203.3.220.0/22No ROA covers it. Add a ROA for AS17461, maxLength 22.672 of 673
Route object: none203.3.220.0/22Route objects for it name AS24130. Add a route object with origin AS17461 in the RIR database for the space.672 of 673
ROA: none203.3.232.0/22No ROA covers it. Add a ROA for AS17461, maxLength 22.672 of 673
Route object: none203.3.232.0/22Route objects for it name AS24130. Add a route object with origin AS17461 in the RIR database for the space.672 of 673
ROA: none103.52.1.0/24No ROA covers it. Add a ROA for AS17461, maxLength 24.672 of 673
Route object: RIR103.52.1.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none103.224.160.0/24No ROA covers it. Add a ROA for AS17461, maxLength 24.672 of 673
Route object: RIR103.224.160.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.3.232.0/24No ROA covers it. Add a ROA for AS17461, maxLength 24.672 of 673
Route object: RIR203.3.232.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

143.119.160.0/22RADBNo ROA
143.119.160.0/23RADBNo ROA
143.119.162.0/23RADBNo ROA
203.3.220.0/23RADBNo ROA
203.3.220.0/24RADBNo ROA
203.3.221.0/24RADBNo ROA
203.3.222.0/23RADBNo ROA
203.3.222.0/24RADBNo ROA
203.3.223.0/24RADBNo ROA
203.3.232.0/23RADBNo ROA
203.3.233.0/24RADBNo ROA
203.3.234.0/23RADBNo ROA
203.3.234.0/24RADBNo ROA
203.3.235.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.