Investigating intermitent errors

Update timeline

1. investigating Feb 26, 2026, 06:11 AM UTC

   Status: Investigating We're investigating intermitent errors in us-east-1. Affected components Database connectivity (us-east-1) (Degraded performance)

2. identified Feb 26, 2026, 06:31 AM UTC

   Status: Identified Currently have IO errors on several clusters in us-east-1, we're working on resolving. Affected components Database connectivity (us-east-1) (Partial outage)

3. identified Feb 26, 2026, 07:34 AM UTC

   Status: Identified Still working on the restore procedure, no clear ETA for full resolution yet. Affected components Database connectivity (us-east-1) (Partial outage)

4. identified Feb 26, 2026, 08:36 AM UTC

   Status: Identified Some clusters are recovered, recovery of remaining clusters is in progress. Affected components Database connectivity (us-east-1) (Partial outage)

5. identified Feb 26, 2026, 10:10 AM UTC

   Status: Identified Most clusters are healthy again, a few are in progress of recovery. If you are affected, please reach out over support to prioritise yours. Affected components Database connectivity (us-east-1) (Partial outage)

6. monitoring Feb 26, 2026, 01:54 PM UTC

   Status: Monitoring Access to all clusters has been restored. Monitoring the rest of the recovery. Affected components Database connectivity (us-east-1) (Partial outage)

7. monitoring Feb 26, 2026, 03:39 PM UTC

   Status: Monitoring A fix has been pushed and we are monitoring clsuter connectivity. Affected components Database connectivity (us-east-1) (Operational)

8. resolved Feb 26, 2026, 04:18 PM UTC

   Status: Resolved All access has been restored. Affected components Database connectivity (us-east-1) (Operational)