Changes / Metabase / Some Metabase Cloud customers hosted in the EU are reporting their site is down or slowness
Metabase: Major incident: Some Metabase Cloud customers hosted in the EU are reporting their site is down or slowness
Summary
Some EU-hosted Metabase Cloud sites were down or slow in a major outage starting 2025-04-02 13:00 UTC, lasting 8 h 33 min and marked resolved at 2025-04-02 21:34 UTC. Metabase reported service restored at 13:46 UTC and added infrastructure monitoring while continuing work on a root-cause fix.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: Some Metabase Cloud customers hosted in the EU are reporting their site is down or slowness
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2025-04-02 13:00 UTC
Before: not present
After: 2025-04-02 21:34 UTC
Before: not present
After: Metabase Cloud Platform
Before: not present
After: We are currently investigating this issue.
Before: not present
After: The issue has been resolved for impacted customers. We will be monitoring closely for the next several hours to insure there is not a recurrence.
Before: not present
After: We have identified the issue which caused some EU-based instances to become unresponsive, which we are tracking here: https://github.com/metabase/metabase/issues/56148
We have added additional monitoring to our cloud infrastructure to alert us if this issue appears again while we work on fixing the root cause.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Some Metabase Cloud customers hosted in the EU are reporting their site is down or slowness (this change) Some EU-hosted Metabase Cloud sites were down or slow in a major outage starting 2025-04-02 13:00 UTC, lasting 8 h 33 min and marked resolved at 2025-04-02 21:34 UTC. Metabase reported service restored at 13:46 UTC and added infrastructure monitoring while continuing work on a root-cause fix. | Major incident |