bgpreport

Network · data from 2026-11-12

AS7716 WORLEY-AS-AP - Worley Organisation Australia

Registry name: WORLEY-AS-AP - Worley Organisation Australia, AU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS7716, 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.20.241.0/24 No ROA Other IRR onlyNTTCOM, RADB 671 100% 67

AS-SET

AS7716 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 14 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: none203.20.241.0/24No ROA covers it. Add a ROA for AS7716, maxLength 24.671 of 673
Route object: RIR203.20.241.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

202.3.32.0/19RADBNo ROA
202.3.32.0/22RADBNo ROA
202.3.42.0/24RADBNo ROA
202.3.56.0/21RADBNo ROA
203.27.67.0/24RADBNo ROA
203.29.98.0/24APNIC, RADBValid
203.31.238.0/23RADBNo ROA
203.31.239.0/24RADBNo ROA
203.34.88.0/24APNICValid
203.56.32.0/23RADBNo ROA
210.8.110.0/24RADBNo ROA
2400:de60::/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.