History

January 24
Increased query latency in all regions
Resolved

The issue has been resolved. Latency is back to the expected level in all regions.

January 24 5:03 PM UTC
Monitoring

A fix has been deployed. We are monitoring closely as latency in all regions is returning to expected levels.

January 24 4:47 PM UTC
Identified

We have identified the root cause for the increased latency in a recent code update and we are working on a fix.

January 24 3:16 PM UTC
Investigating

We are observing increased query latency in all regions. We are currently investigating.

January 24 2:53 PM UTC
January 18
Partial Search store degradation in us-east-1
Resolved

Search functionality is fully restored in the impacted region us-east-1.

January 19 4:19 PM UTC
Monitoring

We continue restoring search functionality for the impacted databases and monitoring recovery.

January 19 8:50 AM UTC
Identified

The search store is impacted in a subset of databases in the region us-east-1. The root cause has been identified and we are working to restore functionality for the impacted branches.

January 18 4:39 PM UTC
January 9
Replication to Search store degraded in us-west-2
Resolved

The issue has been resolved and replication to the Search store is restored in the affected region us-west-2.

January 9 6:29 PM UTC
Monitoring

A fix has been deployed and we are monitoring the recovery of replication to the Search store in the affected region us-west-2.

January 9 4:55 PM UTC
Identified

We have identified the root cause blocking data replication in this region and working on mitigation steps.

January 9 4:29 PM UTC
Investigating

We are investigating an issue with degraded data replication to the Search store, affecting databases in region us-west-2.

Impact: Newly inserted records or updated column content are not available for Search.

January 9 4:26 PM UTC
January 3
Error from the app.xata.io Web UI
Resolved

We have confirmed that the issue is resolved for all users.

January 3 11:09 AM UTC
Monitoring

We have taken corrective action, app.xata.io is recovering and error response codes should be resolved. We continue monitoring closely.

January 3 10:51 AM UTC
Investigating

We are investigating HTTP response codes 500 from app.xata.io

January 3 10:49 AM UTC
September 15, 2023
Creating new dbs and schema migrations fail in N. Virginia region
Resolved

The root cause was identified as a bug that surfaced during routine maintenance operations. The issue has been resolved permanently with a code deployment.

September 15, 2023 11:32 AM UTC
Monitoring

The issue has been mitigated. Creation of new databases and schema migrations are restored in the affected region N. Virginia (us-east-1). We continue monitoring and working on root cause analysis.

September 15, 2023 9:49 AM UTC
Investigating

We are currently investigating an issue which disrupted the creation of new databases and schema migrations in N. Virginia region (us-east-1)

September 15, 2023 9:26 AM UTC
June 21, 2023
Search store in degraded state
Resolved

Replication to the Search store has been restored. The issue was caused by an error in the deployment pipeline. We are taking all relevant measures to ensure such occurrences will be prevented in the future.

June 21, 2023 3:46 PM UTC
Identified

We have identified the root cause and we are rolling out a fix. The Search store issue will begin to recover in all regions soon.

June 21, 2023 3:40 PM UTC
Investigating

Search and aggregation functionality is degraded because replication from the primary store is currently stopped.

June 21, 2023 3:33 PM UTC
June 13, 2023
Error while loading app.xata.io
Resolved

The issue has been resolved, all Xata services are now fully operational.

June 13, 2023 9:27 PM UTC
Monitoring

The Xata Web UI at app.xata.io is available again. We are monitoring closely the recovery and stability of all service components in Xata.

June 13, 2023 7:48 PM UTC
Investigating

We are investigating impact of AWS service degradation in us-east-1 on aspects of the Xata platform (Web UI, API) and taking all possible actions to minimize impact.

June 13, 2023 7:21 PM UTC
Investigating

We are investigating errors "500: INTERNAL_SERVER_ERROR" while loading the Xata Web UI.

June 13, 2023 7:13 PM UTC
May 15, 2023
API Response serialization issues
Resolved

The rollback completed in all regions and we have verified that the API response serialization issue has been resolved.

May 15, 2023 8:10 PM UTC
Monitoring

The rollback that we anticipate to resolve the issue is ongoing and we are monitoring progress across all regions.

May 15, 2023 8:00 PM UTC
Identified

We have identified the root cause of the serialization issues and we are currently working on reverting the change that introduced it.

May 15, 2023 7:44 PM UTC
Investigating

We are currently investigating reports of incorrect serialization in the API response content which may affect various API operations.

May 15, 2023 7:24 PM UTC
February 10, 2023
Error when creating new databases from the Web UI
Resolved

The issue has been resolved. Xata users are now able to create new databases from the Web UI, in all regions.

February 10, 2023 4:00 PM UTC
Monitoring

We are deploying a fix that we are confident will mitigate the issue.
The problem has been attributed to a new deployment.

February 10, 2023 3:58 PM UTC
Identified

We have identified that users are not able to create new databases in any region from the Xata Web UI.

February 10, 2023 3:55 PM UTC
November 13, 2022
API errors in the presence of ascii control characters
Resolved

We have confirmed that the fix which was deployed resolved the issue successfully.

November 13, 2022 5:32 PM UTC
Monitoring

We have identified the root cause of the issue, deployed a fix and monitoring the results closely

November 13, 2022 5:26 PM UTC
Identified

We have identified an issue causing HTTP 400 error responses to be returned by the Xata API, when records with text columns containing ascii control characters are inserted or updated.

November 13, 2022 5:04 PM UTC