Skip to main content
Hasura Cloud

AWS us-east-1 region outage

Degraded Lasted 14h 32m · started · Hasura Cloud's page

Level
confirmed
Worst impact
Degraded
Regions
us, us-east-1
Down Index
31of 100

What to do

  • Check whether you use Hasura Cloud in us, us-east-1. 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 14h 32m it lasted.

    Anything that failed between 2025-10-20 09:19 UTC and 2025-10-20 23:50 UTC may need a replay.
  • Subscribe to Hasura Cloud's feed to hear about the next one first. RSS feed

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

Updates from Hasura Cloud 3

  1. investigating

    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

    provider

  2. investigating

    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.

    provider

  3. resolved

    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 many AWS customers and applications. The root cause was traced to a **DNS resolution issue** within DynamoDB, which led to cascading impacts on related systems. AWS resolved the primary issue early in the morning and completed full recovery by the afternoon. While our core systems remained stable, **some customer projects experienced disruptions and multi-hour downtime** during the AWS outage window. These issues were caused by dependencies on affected AWS services in the US-EAST-1 region. **No data loss occurred**, and all impacted services have since **fully recovered**. We’ll continue to monitor AWS updates and share any relevant follow-up information from their post-event report.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

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

Questions about DWN-692ad00642

Is Hasura Cloud still down?

No, this incident was resolved 2025-10-20 23:50 UTC. For Hasura Cloud's live state, see https://down.guide/hasura.

How long did it last?

14h 32m, from 2025-10-20 09:19 UTC to 2025-10-20 23:50 UTC, by the times Hasura Cloud posted.

What was affected?

Hasura Cloud named in us, us-east-1.

What caused it?

Hasura Cloud hasn't published a root cause. If it does, it shows here.

Where does this come from?

Hasura Cloud's official status page, https://hasura-status.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.