bgpreport

Network · data from 2026-11-12

AS9792 CORINTHIAN-AS-AP - Corinthian Engineering Pty Ltd

Registry name: CORINTHIAN-AS-AP - Corinthian Engineering Pty Ltd, AU · not in PeeringDB

5IPv4 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
0Low visibility seen by under 10% of full-table peers
18Route objects not announced registered with origin AS9792, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS9792, 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.

192.65.182.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
198.22.61.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
203.1.240.0/21 Valid RIR databaseAPNIC, RADB 673 100% 67
192.160.170.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
192.160.169.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67

AS-SET

AS9792 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 18 are in fix.csv.

  • Route object: not announced18

Route objects not announced

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

156.50.0.0/16RADBNo ROA
192.84.230.0/24RADBNo ROA
203.57.194.0/24RADBNo ROA
203.60.0.0/16RADBNo ROA
203.60.0.0/24RADBNo ROA
203.60.4.0/22RADBNo ROA
203.60.4.0/24RADBNo ROA
203.60.5.0/24RADBNo ROA
203.60.6.0/24RADBNo ROA
203.60.7.0/24RADBNo ROA
203.60.8.0/21RADBNo ROA
203.60.16.0/20RADBNo ROA
203.60.17.0/24RADBNo ROA
203.60.32.0/19RADBNo ROA
203.60.51.0/24RADBNo ROA
203.60.64.0/18RADBNo ROA
203.60.128.0/17RADBNo ROA
2406:11c0::/32APNICValid

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.