Hasura

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-12 14:48 UTC

   We're investigating elevated latency on PromptQL. You might see the app taking longer than usual to load or failures in sending messages. Dedicated data planes are not affected.

2. identified 2026-09-12 15:18 UTC

   We've identified the root cause and are working on mitigation.

3. monitoring 2026-09-12 15:37 UTC

   Applied a fix.

4. resolved 2026-09-12 15:44 UTC

   Resolved.

Excerpts are shortened. Read the full incident on Hasura's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-10 16:03 UTC

   We are investigating an issue where DDN connector builds are not completing. Our team is working to identify the cause and restore normal build processing.

2. investigating 2026-09-10 17:23 UTC

   We've identified the root cause: an authentication change in a recent control-plane upgrade caused new connector deployments to stall in a pending state. The fix has been merged and is being rolled out now. Once deployed, we'll re-run your pending connector builds and confirm...

3. monitoring 2026-09-10 18:00 UTC

   We identified the root cause: an authentication change in the service that initializes connector deployments, introduced by an internal upgrade and deployed a fix at approximately 17:30 UTC. New builds started after this time are processing normally. Action required: builds...

4. resolved 2026-09-10 18:10 UTC

   Connector deployments have been processing normally since the fix was deployed. Builds started during the impacted window still need to be re-run.

Excerpts are shortened. Read the full incident on Hasura's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-05-08 14:39 UTC

   We're investigating alerts

2. investigating 2026-05-08 14:47 UTC

   Current signals point to DNS resolution errors with hasura.app domain

3. investigating 2026-05-08 14:57 UTC

   All systems are impacted. DNS resolution failures for hasura.app are affecting all systems.

4. monitoring 2026-05-08 15:08 UTC

   We've applied a fix and are seeing recovery.

5. monitoring 2026-05-08 15:13 UTC

   We're continuing to monitor.

6. monitoring 2026-05-08 15:24 UTC

   The issue has been resolved and services are restored. Due to DNS caching, some users may continue to experience connectivity issues cached records expire. We recommend clearing the cache wherever possible.

7. resolved 2026-05-08 15:50 UTC

   Incident is resolved. Please reach out to our support team if you're still encountering issues.

Excerpts are shortened. Read the full incident on Hasura's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-02-28 03:31 UTC

   We're aware of an issue causing elevated errors rates on PromptQL. Team is actively working on a fix.

2. monitoring 2026-02-28 03:40 UTC

   A fix has been applied.

3. resolved 2026-02-28 04:34 UTC

   This incident is now resolved.

Excerpts are shortened. Read the full incident on Hasura's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. investigating 2025-12-05 09:08 UTC

   There is an ongoing incident with [Cloudflare](https://www.cloudflarestatus.com/incidents/lfrm31y6sw9q) that is impacting Hasura Cloud. We're trying to gauge the impact.

2. monitoring 2025-12-05 09:13 UTC

   we are seeing the system is recovering and apis are coming up.

3. resolved 2025-12-05 09:22 UTC

   All the API's are up and running, cloudflare has also update their status page to resolved.

Excerpts are shortened. Read the full incident on Hasura's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2025-10-20 09:19 UTC

   We're currently assessing the impact on Hasura and PromptQL. Will update shortly. More details on the AWS outage here: https://health.aws.amazon.com/health/status

2. investigating 2025-10-20 17:45 UTC

   Hasura cloud platform is degraded because of the ongoing AWS outage. Hasura team is continuing to monitor this situation. We will post an update as soon as we receive confirmation from AWS regarding service recovery.

3. resolved 2025-10-20 23:50 UTC

   Our team monitored a significant **AWS service disruption** that occurred between **11:49 PM PDT on October 19 and 3:01 PM PDT on October 20** in the **US-EAST-1 region**. This AWS outage affected multiple AWS core services, resulting in elevated error rates and latency across...

Excerpts are shortened. Read the full incident on Hasura's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-10-08 17:57 UTC

   Any supergraph builds that are also building new revisions of connectors are failing now. We're working on a fix.

2. identified 2025-10-08 18:07 UTC

   Existing builds will continue to work. PromptQL and DDN connectors are affected. A fix is being tested and will be deployed in a few minutes.

3. monitoring 2025-10-08 18:29 UTC

   We've rolled out a fix and is monitoring the impact.

4. resolved 2025-10-08 18:50 UTC

   The issue is now resolved. Connector builds should work now.

Excerpts are shortened. Read the full incident on Hasura's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2025-09-29 16:50 UTC

   PromptQL services were affected, resulting in timeouts and errors. Will add more details soon.

Excerpts are shortened. Read the full incident on Hasura's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Azure.

Started during Azure: Network Connectivity – Multiple services impacted in Switzerland North.

1. investigating 2025-09-27 00:49 UTC

   We are currently experiencing an issue affecting services hosted in Azure Switzerland North. Some Virtual Machines in this region may be inaccessible and may have restarted unexpectedly. Azure has acknowledged the issue and is actively investigating. We are monitoring the...

2. investigating 2025-09-27 00:56 UTC

   Azure team continues to investigate

3. identified 2025-09-27 02:49 UTC

   We are aware of an ongoing issue affecting Azure services in the Switzerland North region. Microsoft is actively investigating and preparing a fix. You can follow the latest updates directly on the [Azure Status Page](https://azure.status.microsoft/en-us/status). We will...

4. monitoring 2025-09-27 04:05 UTC

   Azure has identified the root cause of the issue impacting services in the Switzerland North region. A recent deployment introduced a malformed certificate prefix that disrupted connection authorization. Microsoft has rolled back the faulty deployment and is seeing recovery...

5. resolved 2025-09-27 06:48 UTC

   This incident has been **resolved**. Azure has rolled back the faulty deployment that caused the issue with connection authorization in the Switzerland North region. Most impacted services have fully recovered, and the remaining few are nearing completion. We have observed...

Excerpts are shortened. Read the full incident on Hasura's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Anthropic (Claude), Cloudflare, Google Cloud.

1. investigating 2025-06-12 18:35 UTC

   **We are currently investigating potential issues affecting services on Google Cloud Platform.** Some functionality may be impacted. We will share updates as soon as more information becomes available.

2. investigating 2025-06-12 19:10 UTC

   There is an ongoing incident with [Google Cloud](https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW) and [Cloudflare](https://www.cloudflarestatus.com/incidents/25r9t0vz99rp) that is impacting Hasura Cloud. We're trying to gauge the impact, but our monitoring systems...

3. investigating 2025-06-12 19:39 UTC

   The Google Cloud outage is affecting Anthropic ([status page](https://status.anthropic.com/)) as well, affecting most of the PromptQL projects using Claude models. Users might see intermittent failures when using PromptQL API or the Playground.

4. investigating 2025-06-12 19:51 UTC

   Google Cloud is reporting that all regions except us-central1 have recovered. Most of Hasura monitoring services are in us-central1 region. We're continuing to monitor the recovery.

5. identified 2025-06-12 21:08 UTC

   Most of the components have recovered, except for our monitoring system. Viewing traces on the console are still affected.

6. resolved 2025-06-12 22:38 UTC

   Everything is operational now. Incidents are now resolved at Cloudflare, Google Cloud is still monitoring the situation, but we are not seeing any impact.

Excerpts are shortened. Read the full incident on Hasura's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-03-12 05:36 UTC

   We are experiencing issues accessing PromptQL for both public and private DDN. Our team is actively investigating the issue.

2. identified 2025-03-12 05:46 UTC

   We have Identified the issue and a patch has been deployed

3. monitoring 2025-03-12 05:49 UTC

   The issue has been resolved, and we are currently monitoring the infrastructure.

4. resolved 2025-03-12 05:54 UTC

   The issue has been resolved, and all PromptQL services are now accessible to customers.

Excerpts are shortened. Read the full incident on Hasura's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-02-13 22:24 UTC

   The issue has been identified and a fix is being implemented.

2. identified 2025-02-13 22:44 UTC

   CLI version v2.23.0 has been rolled back. If you are using this version, please downgrade to v2.22.0 using `ddn update-cli --version v2.22.0`

3. identified 2025-02-13 22:58 UTC

   We are working on a fix for v2.23.0 CLI

4. monitoring 2025-02-13 23:13 UTC

   A fix has been implemented and we are monitoring the results.

5. resolved 2025-02-13 23:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hasura's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. identified 2025-02-05 18:55 UTC

   Some users may experience API performance degradation due to network related issues being reported under Cloudflare. The incident is being tracked and reported here: https://www.cloudflarestatus.com/ Note that users under Hasura's DDN platform are not affected. At this time,...

2. resolved 2025-02-05 22:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hasura's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2024-12-31 22:09 UTC

   We are currently investigating this issue.

2. identified 2024-12-31 22:23 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2024-12-31 22:27 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2024-12-31 22:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hasura's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-12-03 17:44 UTC

   We are currently investigating this issue.

2. monitoring 2024-12-03 19:35 UTC

   A fix has been applied, we're monitoring.

3. resolved 2024-12-03 20:06 UTC

   The incident has been resolved, we'll update this page with a postmortem.

Excerpts are shortened. Read the full incident on Hasura's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2021-01-06 13:59 UTC

   We are currently investigating degraded performance in us-east-2. Users might be seeing increased response times.

2. identified 2021-01-06 14:14 UTC

   We've identified an issue with underlying infrastructure and we're now implementing fixes.

3. monitoring 2021-01-06 14:39 UTC

   We've temporarily moved a few projects to new infrastructure and we're monitoring the results.

4. monitoring 2021-01-06 15:01 UTC

   We are continuing to monitor for any further issues.

5. investigating 2021-01-06 19:00 UTC

   We have narrowed down the issue to a set of 15 projects that were part of the same node in the us-east-2 region. If notice any slow responses to operations/queries or see any issues when trying to load the console, please try changing the region as a temporary workaround. We...

6. investigating 2021-01-06 19:04 UTC

   We are continuing to investigate this issue.

7. resolved 2021-01-06 21:24 UTC

   We’ve fixed the issue with degraded performance and are actively monitoring the situation over the next few hours. If you face any issues, please reach out to us by writing to support@hasura.io or at https://hasura.io/help

Excerpts are shortened. Read the full incident on Hasura's status page.

Failure mode: A code release introduced the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2020-12-11 11:00 UTC

   Hasura Cloud experienced an incident earlier today where projects were unavailable from 11:00 UTC to 11:45 UTC. A deployment process to a non-critical component resulted in an error state which affected our main orchestration service - causing disruption across all...

Excerpts are shortened. Read the full incident on Hasura's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2021-02-16 13:00 UTC

   We are currently investigating the high error rates(502s) for some of the free-tier tenants in the us-east-2 region. There are no issues with the paid tier cluster in any of the regions. We will update the findings here.

2. monitoring 2021-02-16 13:57 UTC

   We have rolled out the fix and we see the tenants facing the issues are back up. We are actively monitoring for anomalies and outliers tenants. We would update the issue in the next 15 minutes.

3. resolved 2021-02-16 14:21 UTC

   We can confirm all the free tenants in us-east-2 region which were having problems are responding well and everything seems to be working as expected. Sorry for the inconvenience and trouble faced. We are working hard to keep our system up and running and trying to improve the...

Excerpts are shortened. Read the full incident on Hasura's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2021-02-16 12:20 UTC

   We are currently facing the intermittent login issue with the Hasura console. Please subscribe for the continuous update.

2. resolved 2021-02-16 12:31 UTC

   We have resolved the issue of the intermittent login with Hasura Console. We are actively monitoring the systems for any failure. We would keep you posted incase the error rates escalates.

Excerpts are shortened. Read the full incident on Hasura's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2021-02-14 14:11 UTC

   We are currently investigating delays in processing metrics in us-east-2. You might see the metrics under monitoring tab with delays of about 10minutes or even more.

2. resolved 2021-02-14 16:26 UTC

   Metrics are being processed without any issues now.

Excerpts are shortened. Read the full incident on Hasura's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2021-02-01 06:30 UTC

   Between 21.30PM GMT(Sun) to 6AM GMT(Mon) Hasura Cloud experienced an issue that impacted approximately 5% of free-tier projects and caused those projects to suffer downtime. One of our worker nodes hosting a portion of free-tier tenants failed an internal health check and was...

Excerpts are shortened. Read the full incident on Hasura's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2021-01-20 12:25 UTC

   we are currently investigating the latency issue with our metrics and reporting system in eu-west-2(london) region. subscribe/visit the page for regular updates.

2. identified 2021-01-20 19:00 UTC

   we have identified the possible cause and we are in process of implementing the fix. we should have the next update in 30mins.

3. monitoring 2021-01-20 19:36 UTC

   we have fixed the underlying issue and we are actively monitoring it.

4. resolved 2021-01-20 19:54 UTC

   we can confirm the applied fix is working. we will keep monitoring the systems and update in case of any issue.

Excerpts are shortened. Read the full incident on Hasura's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2021-03-24 07:21 UTC

   A subset of projects are having issues with accessing Hasura Console. We're investigating the issue and preliminary findings indicate that the affected versions are v1.3.3 which were upgraded to the latest `cloud.5` release recently. Engineering is working on the issue.

2. investigating 2021-03-24 07:27 UTC

   We're continuing to investigate the issue. GraphQL and other APIs are not affected.

3. identified 2021-03-24 07:50 UTC

   We've identified the issue to be a bad build of the console assets. A fix is being deployed.

4. monitoring 2021-03-24 07:51 UTC

   We've rolled out a fix and are now monitoring the status. Force refresh if you're still unable access the console.

5. resolved 2021-03-24 08:01 UTC

   The incident has been resolved. The root cause was found to be a bad deployment of the console JavaScript assets build following a latest update. The build is now corrected and steps are taken to ensure that console assets are built along with the release builds. The following...

Excerpts are shortened. Read the full incident on Hasura's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2021-02-16 10:51 UTC

   We are currently investigating delays in processing metrics in us-east-2. You might see the metrics under monitoring tab with delays.

2. monitoring 2021-02-16 15:32 UTC

   We have identified the underlying issue and implemented the fix. We see the latency for processing the metrics is reduced significantly. You should be able to see the metrics almost immediately. We are actively monitoring the fix implemented for any errors.

3. monitoring 2021-02-16 18:06 UTC

   We have fixed the issue of delay with processing metrics. You should see the metrics almost immediately for pro tab and also Datadog integration should be working well.

4. resolved 2021-02-16 18:06 UTC

   We have fixed the issue of delay with processing metrics. You should see the metrics almost immediately for pro tab and also Datadog integration should be working well.

Excerpts are shortened. Read the full incident on Hasura's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2021-04-12 16:30 UTC

   We are currently investigating delays in processing metrics across all regions. GraphQL APIs are not affected. You might not be seeing the real time data in the monitoring tab.

2. investigating 2021-04-12 16:37 UTC

   We've identified the issue and are rolling out a fix.

3. monitoring 2021-04-12 16:38 UTC

   We've rolled out the fix and are now monitoring the status.

4. resolved 2021-04-12 16:42 UTC

   The issue is now fixed. You should see realtime metrics on the monitoring tab now.

Excerpts are shortened. Read the full incident on Hasura's status page.