<html><head><meta http-equiv="content-type" content="text/html; charset=us-ascii"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Dear colleagues, <span style="font-size: 11pt; font-family: Arial; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;">Yesterday, at 11:06 UTC we attempted to migrate the RPKI core on the production environment from JDK8 to JDK11 via an automated deployment. Unfortunately, the update to the RPKI core was not successful, which resulted in RPKI becoming partially unavailable. <span style="font-size: 11pt; font-family: Arial; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;">The RPKI dashboard and API were no longer accessible which meant that no changes could be made to the ROA configurations or alerts. The provisioning (up/down) protocol used by non-hosted Certificate Authorities was also unavailable during this time. <span style="font-size: 11pt; font-family: Arial; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;">The RRDP and rsync public repositories were not impacted by this incident. <span style="font-size: 11pt; font-family: Arial; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;">At approximately 12:30 UTC, we reverted our changes and the RPKI core was back up and running. The RPKI team has since then fixed the upgrade issue and the migration has been completed successfully. <span style="font-size: 11pt; font-family: Arial; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;">The upgrade issue was caused by the production environment still using some file-based HSM keys. These file-based HSM keys are no longer used in the staging environment, so the issue was not detected before we attempted the production upgrade to JDK11.<span style="font-size: 11pt; font-family: Arial; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;"> <span style="font-size: 11pt; font-family: Arial; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;">Kind regards,<span style="font-size: 11pt; font-family: Arial; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;">Stella Vouteva</body></html>