IO errors on some clusters

What to do

• Check whether your product depends on Xata. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 2h 38m it lasted.

  Anything that failed between 2026-05-18 13:52 UTC and 2026-05-18 16:30 UTC may need a replay.

• Subscribe to Xata's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=xata works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Xata 6

1. investigatingMay 18, 2026, 1:52 PM UTC

   Some clusters are currently seeing IO errors, we're investigating.

   provider

2. identifiedMay 18, 2026, 2:46 PM UTC

   We've identified the issue causing IO errors for some clusters and we're deploying a fix.

   provider

3. monitoringMay 18, 2026, 3:52 PM UTC

   All databases are again fully operational, except for one customer with which we're in contact with.

   provider

4. monitoringMay 18, 2026, 3:53 PM UTC

   We've deployed a fix for the issue causing IO errors for some clusters and we're now monitoring.

   provider

5. monitoringMay 18, 2026, 3:55 PM UTC

   All databases are again fully operational, except for one customer with which we're in contact with.

   provider

6. resolvedMay 18, 2026, 4:30 PM UTC

   Fully resolved now.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.