Rownd - Notice history

After extensive monitoring, the service appears to be stable. We have opened a ticket with our database provider, as it appears they had some internal issues during this outage. We'll add details to the a postmortem once we are confident in the root cause.

The service is operating normally and we are monitoring for further disruptions.

Our services were having trouble connecting to our primary database for about 20 minutes. Services appear to be recovering. We are continuing to investigate the cause of this disruption.

We take any amount of downtime very seriously, and we want to provide full transparency regarding our recent service interruption. We sincerely apologize for the inconvenience this caused to you and your users.

• Root Cause: During a routine auto-rotation of our internal certificates, an unexpected race condition occurred. This caused the certificate trust chain to break between our internal service members, leading to the outage.

• Resolution: Our engineering team quickly identified the issue, manually recycled the necessary certificates, and restarted the affected services. All systems have successfully recovered and are operating normally.

• Preventative Measures: To ensure this does not happen again, we are implementing configuration changes to our infrastructure prior to our next scheduled certificate rotation. These updates will strictly enforce the proper rotation sequence and guarantee that certificates cannot fall out of sync.