Xata incident

IO errors on some clusters

Minor Resolved View vendor source →

Xata experienced a minor incident on May 18, 2026, lasting —. The incident has been resolved; the full update timeline is below.

Started
May 18, 2026, 04:30 PM UTC
Resolved
May 18, 2026, 04:30 PM UTC
Duration
Detected by Pingoru
May 18, 2026, 04:30 PM UTC

Update timeline

  1. investigating May 18, 2026, 01:52 PM UTC

    Status: Investigating Some clusters are currently seeing IO errors, we're investigating. Affected components Database connectivity (us-east-1) (Degraded performance)

  2. identified May 18, 2026, 02:46 PM UTC

    Status: Identified We've identified the issue causing IO errors for some clusters and we're deploying a fix. Affected components Database connectivity (us-east-1) (Degraded performance)

  3. monitoring May 18, 2026, 03:52 PM UTC

    Status: Monitoring All databases are again fully operational, except for one customer with which we're in contact with. Affected components Database connectivity (us-east-1) (Degraded performance)

  4. monitoring May 18, 2026, 03:53 PM UTC

    Status: Monitoring We've deployed a fix for the issue causing IO errors for some clusters and we're now monitoring. Affected components Database connectivity (us-east-1) (Operational)

  5. monitoring May 18, 2026, 03:55 PM UTC

    Status: Monitoring All databases are again fully operational, except for one customer with which we're in contact with. Affected components Database connectivity (us-east-1) (Operational)

  6. resolved May 18, 2026, 04:30 PM UTC

    Status: Resolved Fully resolved now. Affected components Database connectivity (us-east-1) (Operational)