Service Outage

Update timeline

1. investigating Feb 21, 2026, 07:02 PM UTC

   Service outage under investigation

2. resolved Feb 21, 2026, 07:16 PM UTC

   Database transaction log issue resolve. Services back online

3. identified Feb 21, 2026, 07:25 PM UTC

   Transaction Log blocking commits

4. monitoring Feb 21, 2026, 07:54 PM UTC

   Administrators indicating resolution will be completed within an hour.

5. resolved Feb 21, 2026, 09:00 PM UTC

   All services online

6. investigating Feb 24, 2026, 02:21 PM UTC

   During routine certificate renewals, one certificate was inadvertently not upgraded. This certificate was associated with the backup process. Because it was not updated, automated backups began failing without immediate detection. As a result, the database transaction log continued to grow until it reached its configured size limit. Once this limit was reached, the database was unable to process transactions, resulting in the service interruption. The missed certificate has since been updated, backup operations have been verified to be functioning normally, and the transaction log has been returned to standard operating levels. We are currently reviewing monitoring and validation procedures to ensure all certificates are properly accounted for during renewals and that backup failures are detected more promptly in the future.