Xata Outage History

Xata is up right now

Xata had 11 outages in the last 2 years totaling 103h 5m of downtime — averaging 0.5 incidents per month.

There were 11 Xata outages since October 20, 2025 totaling 103h 5m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://www.xatastatus.com

Minor July 28, 2026

Provision failing for new clusters

Detected by Pingoru
Jul 28, 2026, 08:08 AM UTC
Resolved
Jul 28, 2026, 08:08 AM UTC
Duration
—
Affected: Management APIs
Timeline · 4 updates
  1. investigating Jul 28, 2026, 07:35 AM UTC

    Status: Investigating We are investigating an issue affecting provisioning of new clusters Affected components Management APIs (Degraded performance)

  2. identified Jul 28, 2026, 07:40 AM UTC

    Status: Identified We have identified the root cause on new nodes added after capacity increase, we are working on remediating the issue Affected components Management APIs (Degraded performance)

  3. monitoring Jul 28, 2026, 07:47 AM UTC

    Status: Monitoring We have implemented a fix and are currently monitoring the situation Affected components Management APIs (Degraded performance)

  4. resolved Jul 28, 2026, 08:08 AM UTC

    Status: Resolved The issue has been resolved. Affected components Management APIs (Operational)

Read the full incident report →

Minor July 22, 2026

GCP regions provisions of new DBs is failing

Detected by Pingoru
Jul 22, 2026, 07:54 PM UTC
Resolved
Jul 22, 2026, 07:54 PM UTC
Duration
—
Affected: Management APIs
Timeline · 4 updates
  1. investigating Jul 22, 2026, 07:04 PM UTC

    Status: Investigating GCP regions are failing to provision new branches. Investigating the cause. Affected components Management APIs (Degraded performance)

  2. identified Jul 22, 2026, 07:35 PM UTC

    Status: Identified Issue is identified and we are applying a fix. Affected components Management APIs (Degraded performance)

  3. monitoring Jul 22, 2026, 07:48 PM UTC

    Status: Monitoring Issue should be solved, monitoring. Affected components Management APIs (Degraded performance)

  4. resolved Jul 22, 2026, 07:54 PM UTC

    Status: Resolved Issue is now resolved. Affected components Management APIs (Operational)

Read the full incident report →

Minor May 18, 2026

IO errors on some clusters

Detected by Pingoru
May 18, 2026, 04:30 PM UTC
Resolved
May 18, 2026, 04:30 PM UTC
Duration
—
Timeline · 6 updates
  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)

Read the full incident report →

Minor April 30, 2026

Branching degraded in us-east-1 region

Detected by Pingoru
Apr 30, 2026, 08:23 AM UTC
Resolved
Apr 30, 2026, 08:23 AM UTC
Duration
—
Affected: Management APIs
Timeline · 3 updates
  1. investigating Apr 30, 2026, 07:55 AM UTC

    Status: Investigating We're seeing some child branches of older database instances remain in "Setting up primary". Affected components Management APIs (Degraded performance)

  2. monitoring Apr 30, 2026, 08:09 AM UTC

    Status: Monitoring Issue is now solved, continuing to monitor. Affected components Management APIs (Degraded performance)

  3. resolved Apr 30, 2026, 08:23 AM UTC

    Status: Resolved All branches are up now. Affected components Management APIs (Operational)

Read the full incident report →

Minor February 26, 2026

Investigating intermitent errors

Detected by Pingoru
Feb 26, 2026, 04:18 PM UTC
Resolved
Feb 26, 2026, 04:18 PM UTC
Duration
—
Timeline · 8 updates
  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)

Read the full incident report →

Minor February 24, 2026

Some clusters facing I/O errors

Detected by Pingoru
Feb 24, 2026, 05:34 PM UTC
Resolved
Feb 24, 2026, 05:34 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating Feb 24, 2026, 12:31 PM UTC

    Status: Investigating We are currently investigating a small number of clusters facing I/O errors in us-east-1 region Affected components Database connectivity (us-east-1) (Degraded performance)

  2. identified Feb 24, 2026, 12:38 PM UTC

    Status: Identified A routine update caused an issue with one of our storage nodes. We are currently working on a remediation Affected components Database connectivity (us-east-1) (Degraded performance)

  3. monitoring Feb 24, 2026, 03:28 PM UTC

    Status: Monitoring All active clusters have recovered. Affected components Database connectivity (us-east-1) (Operational)

  4. resolved Feb 24, 2026, 05:34 PM UTC

    Status: Resolved All good. Affected components Database connectivity (us-east-1) (Operational)

Read the full incident report →

Minor February 11, 2026

Errors creating new clusters

Detected by Pingoru
Feb 11, 2026, 09:50 AM UTC
Resolved
Feb 11, 2026, 09:50 AM UTC
Duration
—
Timeline · 2 updates
  1. investigating Feb 11, 2026, 09:10 AM UTC

    Status: Investigating We are investigating an issue in creating new branches in us-east-1. Affected components Database connectivity (us-east-1) (Partial outage)

  2. resolved Feb 11, 2026, 09:50 AM UTC

    Status: Resolved We've identified the issue and pushed a fix. New branches can be created in us-east-1. Affected components Database connectivity (us-east-1) (Operational)

Read the full incident report →