- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 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 0m it lasted.
Anything that failed between 2024-11-26 20:25 UTC and 2020-12-11 11:00 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 1
- resolved
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 infrastructure nodes. We’ve made technical and process changes to make sure we can prevent such incidents in the future. Primarily, we are immediately separating the orchestration components of critical path infrastructure (Hasura GraphQL APIs) from non-critical path infrastructure (monitoring/metrics).
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-4029a224a1
Is Hasura Cloud still down?
No, this incident was resolved 2020-12-11 11:00 UTC. For Hasura Cloud's live state, see https://down.guide/hasura.
How long did it last?
0m, from 2024-11-26 20:25 UTC to 2020-12-11 11:00 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.