- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 100
What to do
Check whether your product depends on Metabase 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 2021-06-10 21:21 UTC and 2021-06-09 19:30 UTC may need a replay.Subscribe to Metabase Cloud's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=metabase works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Metabase Cloud 1
- resolved
Around 16:30 PT we received a report of a customer that could not connect to it's Metabase instance. Our engineering team identified an issue on the application database which showed that the clusters weren't available in our cloud provider (CSP). After further investigation they found out that a cluster resize didn't apply correctly due to a configuration mismatch between the configuration scripts and the CSP offering resulting in downtime. The configuration script was modified to be compatible with the CSP and the database instances came back online.
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-44a8970197
Is Metabase Cloud still down?
No, this incident was resolved 2021-06-09 19:30 UTC. For Metabase Cloud's live state, see https://down.guide/metabase.
How long did it last?
0m, from 2021-06-10 21:21 UTC to 2021-06-09 19:30 UTC, by the times Metabase Cloud posted.
What caused it?
Metabase Cloud hasn't published a root cause. If it does, it shows here.
Where does this come from?
Metabase Cloud's official status page, https://status.metabase.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.