- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 17of 100
What to do
Check whether your product depends on Hasura Cloud. 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 53m it lasted.
Anything that failed between 2025-10-08 17:57 UTC and 2025-10-08 18: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 4
- identified
Any supergraph builds that are also building new revisions of connectors are failing now. We're working on a fix.
provider
- identified
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.
provider
- monitoring
We've rolled out a fix and is monitoring the impact.
provider
- resolved
The issue is now resolved. Connector builds should work now.
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-3a423b4926
Is Hasura Cloud still down?
No, this incident was resolved 2025-10-08 18:50 UTC. For Hasura Cloud's live state, see https://down.guide/hasura.
How long did it last?
53m, from 2025-10-08 17:57 UTC to 2025-10-08 18:50 UTC, by the times Hasura Cloud posted.
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.