Vendor reports: major outageResolved · vendor status “resolved”Official status API
Metabase Store is unavailable
Reported by Metabase Cloud · Data & Analytics · source last read 13 min ago
- Vendor start
- Aug 12, 2026, 19:13 UTC
- Vendor's clock
- Resolved
- Aug 12, 2026, 20:52 UTC
- Vendor's clock
- First seen by Statuswall
- Before tracking began
- Statuswall's clock
- Duration
- 1 h 39 min
- From vendor start and resolution
Summary
Built from the facts below, no AI
Potential impact, not a confirmed outage of your systems.
What the vendor confirmed
Affected products and regions
- Components: Metabase Store.[E6]
What is unknown
- Which regions are affected: the vendor did not say.[E5]
- Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.
Last update in these facts: 2026-08-12 20:52 UTC · summary s1, evidence 4df9e477164257f0
Evidence (7)
- E1Metabase Cloud reports major outage. (vendor) source (opens in a new tab)
- E2Vendor title: "Metabase Store is unavailable". (vendor) source (opens in a new tab)
- E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
- E4Vendor-reported start: 2026-08-12 19:13 UTC. (vendor) source (opens in a new tab)
- E5The vendor did not state which regions are affected. (Statuswall)
- E6Components the vendor attached: Metabase Store. (vendor) source (opens in a new tab)
- E7Vendor-reported resolution: 2026-08-12 20:52 UTC. (vendor) source (opens in a new tab)
Affected scope
Not stated by the vendor
Components: Metabase Store
No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.
Potential relevance
Metabase Cloud is not in your stack. Follow it to see whether reports like this fall inside the regions you use.
Timeline
Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.
- Aug 12, 2026, 19:13 UTCVendor-reported startVendor time
- Aug 12, 2026, 20:52 UTCVendor-reported resolutionVendor time
No changes observed yet. Statuswall began recording changes on incidents in November 2026.