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).
No components marked as affected
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).