Xata Outage History

Xata is up right now

There were 4 Xata outages since February 11, 2026. Each is summarised below — incident details, duration, and resolution information.

Source: https://www.xatastatus.com

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 →

Looking to track Xata downtime and outages?

Pingoru polls Xata's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Xata reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Xata alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Xata for free

5 free monitors · No credit card required