# Metabase: Problems when creating instances

- Impact (vendor’s label): minor
- Status: resolved
- Started: 2023-06-13 19:56 UTC · Resolved: 2023-06-13 23:13 UTC · Duration: 3.3 h
- Updates: 2 · Affected components: Metabase Cloud Platform, Metabase Store
- [Vendor status page: https://stspg.io/nrv9y0rnsrz6](https://stspg.io/nrv9y0rnsrz6)
- [Company: Metabase](https://rewindex.com/company/metabase.md)

## Part of an outage event

- [AWS outage, Jun 13, 2023: 56 vendors, 56 incidents](https://rewindex.com/events/2023-06-13-aws)
- This incident blames AWS as the cause. (hop 1, posted +44 min vs the first vendor naming AWS)
- Evidence: “…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…”

```mermaid
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 --- me
```

_Detected automatically from incidents that started together and named the same provider; a link means one incident named another vendor, not a confirmed cause._

## Timeline of updates

- **identified** 2023-06-13 19:56 UTC: 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** 2023-06-13 23:13 UTC: AWS reports that the service should be normalized now


---
Canonical: https://rewindex.com/company/metabase/incidents/bbsf6jt53z14 · Markdown: https://rewindex.com/company/metabase/incidents/bbsf6jt53z14.md · JSON: https://rewindex.com/api/v1/companies/metabase/incidents/bbsf6jt53z14 · Generated 2026-10-19T23:16:21.300Z