bgpreport

Network · data from 2026-11-12

AS17535 Genisyst

Registry name: GENISYST-AS-AP - Genisyst Pty Ltd, AU · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS17535, 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.63.204.0/24 No ROA Nonecovered by 203.63.204.0/23 166 25% 51
203.63.205.0/24 No ROA Nonecovered by 203.63.204.0/23 166 25% 51
210.8.204.0/24 No ROA Nonecovered by 210.8.204.0/23 166 25% 51
210.8.205.0/24 No ROA Nonecovered by 210.8.204.0/23 166 25% 51
210.11.44.0/23 No ROA Nonecovered by 210.11.44.0/22 166 25% 51
210.11.46.0/23 No ROA Nonecovered by 210.11.44.0/22 166 25% 51
202.4.190.0/24 No ROA Other IRR onlyRADB 672 100% 67
203.28.142.0/24 No ROA Other IRR onlyRADB 672 100% 67
203.63.204.0/23 No ROA Other IRR onlyRADB 668 99% 67
210.8.204.0/23 No ROA Other IRR onlyRADB 667 99% 67
210.11.44.0/22 No ROA Other IRR onlyRADB 667 99% 67

AS-SET

AS17535'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 27 are in fix.csv.

  • ROA: none11
  • Route object: none6
  • Route object: RIR5
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none203.63.204.0/24No ROA covers it. Add a ROA for AS17535, maxLength 24.166 of 673
Route object: none203.63.204.0/24No route object for it. A route object for 203.63.204.0/23 with origin AS17535 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17535 in the RIR database for the space.166 of 673
ROA: none203.63.205.0/24No ROA covers it. Add a ROA for AS17535, maxLength 24.166 of 673
Route object: none203.63.205.0/24No route object for it. A route object for 203.63.204.0/23 with origin AS17535 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17535 in the RIR database for the space.166 of 673
ROA: none210.8.204.0/24No ROA covers it. Add a ROA for AS17535, maxLength 24.166 of 673
Route object: none210.8.204.0/24No route object for it. A route object for 210.8.204.0/23 with origin AS17535 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17535 in the RIR database for the space.166 of 673
ROA: none210.8.205.0/24No ROA covers it. Add a ROA for AS17535, maxLength 24.166 of 673
Route object: none210.8.205.0/24No route object for it. A route object for 210.8.204.0/23 with origin AS17535 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17535 in the RIR database for the space.166 of 673
ROA: none210.11.44.0/23No ROA covers it. Add a ROA for AS17535, maxLength 23.166 of 673
Route object: none210.11.44.0/23No route object for it. A route object for 210.11.44.0/22 with origin AS17535 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17535 in the RIR database for the space.166 of 673
ROA: none210.11.46.0/23No ROA covers it. Add a ROA for AS17535, maxLength 23.166 of 673
Route object: none210.11.46.0/23No route object for it. A route object for 210.11.44.0/22 with origin AS17535 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17535 in the RIR database for the space.166 of 673
ROA: none202.4.190.0/24No ROA covers it. Add a ROA for AS17535, maxLength 24.672 of 673
Route object: RIR202.4.190.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.28.142.0/24No ROA covers it. Add a ROA for AS17535, maxLength 24.672 of 673
Route object: RIR203.28.142.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.63.204.0/23No ROA covers it. Add a ROA for AS17535, maxLength 23.668 of 673
Route object: RIR203.63.204.0/23Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none210.8.204.0/23No ROA covers it. Add a ROA for AS17535, maxLength 23.667 of 673
Route object: RIR210.8.204.0/23Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none210.11.44.0/22No ROA covers it. Add a ROA for AS17535, maxLength 22.667 of 673
Route object: RIR210.11.44.0/22Route object only in RADB. Add it in the RIR database for the space.667 of 673

Route objects not announced

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

203.26.242.0/24RADBNo ROA
210.8.223.68/30RADBNo ROA
210.11.44.0/24RADBNo ROA
210.11.129.96/29RADBNo ROA
210.11.131.208/29RADBNo 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.