At 10:29 UTC, the RPKI core systems and Publication as a Service (PaaS) were unavailable. Around 11:18 UTC, both systems were fully operational again.
Any changes made during the outage on the Publicaion as a Service are lost. Since these are changes from automated systems, recovery should be automatic.
Due to an issue with an NFS volume share, both RPKI CA and PaaS were unavailable.
The RPKI on-call engineer first began troubleshooting the RPKI CA issue, hence why troubleshooting the issue with the Publication as a Service (PAAS) was delayed. Unlike the issue with RPKI CA systems, the backup of the PaaS service was also unreachable, which meant restoring directly on the filesystem was not a possible workaround. Around 11:18 UTC, the service was restored, and Publication as a Service was again operational.
Following this event, the RPKI team has planned effort to move away from using NFS storage and implement a more stable solution.