Metabase: Problems when creating instances
AWS outage, Jun 13, 2023 · 56 vendors, 56 incidents
Metabase’s incident blames AWS as the cause. (hop 1, posted +44 min vs the first vendor naming AWS)
“…Problems when creating instances AWS reports that the service should be normalized now AWS reports that the service should be normalized now There is a problem with our cloud service provider that doe…”
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["AWS<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>13 vendors, 13 blamed AWS<br/>Pipedream, Wiz, Temporal Cloud +10"]:::blames
root --> h1
h4["1 to 4 hours later<br/>7 vendors, 6 blamed AWS<br/>CockroachDB, Vanta, Asana +4"]:::blames
root --> h4
me["Metabase (this incident)<br/>posted +44 min"]:::me
h1 --- meFull event: timeline, evidence and all vendors →
Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.
Affected components: Metabase Cloud PlatformMetabase Store
Timeline of updates
- identified
There is a problem with our cloud service provider that doesn’t let us create new instances of Metabase. We have identified the problem and we are waiting for the cloud service provider to restore its services.
- resolved
AWS reports that the service should be normalized now
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).