bgpreport

Network · data from 2026-11-12

AS18361 ASX-AS-AP - ASX Operations Pty Ltd

Registry name: ASX-AS-AP - ASX Operations Pty Ltd, AU · not in PeeringDB

9IPv4 routes 22.2% RPKI valid · 33.3% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
7No 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 AS18361, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS18361, 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.15.144.0/23 No ROA Nonecovered by 203.15.144.0/22 673 100% 67
203.15.146.0/23 No ROA Nonecovered by 203.15.144.0/22 673 100% 67
203.15.145.0/24 No ROA Nonecovered by 203.15.144.0/22 671 100% 68
203.15.146.0/24 No ROA Nonecovered by 203.15.144.0/22 671 100% 68
203.15.147.0/24 No ROA Nonecovered by 203.15.144.0/22 671 100% 68
203.0.116.0/22 No ROA None 634 94% 67
203.15.144.0/22 No ROA Other IRR onlyRADB 671 100% 67
103.239.128.0/23 Valid RIR databaseAPNIC 671 100% 67
103.239.129.0/24 Valid RIR databaseAPNIC 671 100% 68

AS-SET

AS18361 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 19 are in fix.csv.

  • ROA: none7
  • Route object: none6
  • Route object: RIR1
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none203.15.144.0/23No ROA covers it. Add a ROA for AS18361, maxLength 23.673 of 673
Route object: none203.15.144.0/23No route object for it. A route object for 203.15.144.0/22 with origin AS18361 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18361 in the RIR database for the space.673 of 673
ROA: none203.15.146.0/23No ROA covers it. Add a ROA for AS18361, maxLength 23.673 of 673
Route object: none203.15.146.0/23No route object for it. A route object for 203.15.144.0/22 with origin AS18361 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18361 in the RIR database for the space.673 of 673
ROA: none203.15.145.0/24No ROA covers it. Add a ROA for AS18361, maxLength 24.671 of 673
Route object: none203.15.145.0/24No route object for it. A route object for 203.15.144.0/22 with origin AS18361 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18361 in the RIR database for the space.671 of 673
ROA: none203.15.146.0/24No ROA covers it. Add a ROA for AS18361, maxLength 24.671 of 673
Route object: none203.15.146.0/24No route object for it. A route object for 203.15.144.0/22 with origin AS18361 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18361 in the RIR database for the space.671 of 673
ROA: none203.15.147.0/24No ROA covers it. Add a ROA for AS18361, maxLength 24.671 of 673
Route object: none203.15.147.0/24No route object for it. A route object for 203.15.144.0/22 with origin AS18361 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18361 in the RIR database for the space.671 of 673
ROA: none203.0.116.0/22No ROA covers it. Add a ROA for AS18361, maxLength 22.634 of 673
Route object: none203.0.116.0/22No route object for it. Add a route object with origin AS18361 in the RIR database for the space.634 of 673
ROA: none203.15.144.0/22No ROA covers it. Add a ROA for AS18361, maxLength 22.671 of 673
Route object: RIR203.15.144.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

43.255.128.0/22RADBNo ROA
43.255.128.0/24RADBNo ROA
43.255.129.0/24RADBNo ROA
43.255.130.0/24RADBNo ROA
43.255.131.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.