Metabase

Affected: Metabase Store

Failure mode: The text does not say enough to tell. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-12 19:13 UTC

   We are performing maintenance on the Metabase Store infrastructure. We expect it to be operational within an hour.

2. resolved 2026-08-12 20:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Metabase's status page.

Affected: Metabase Cloud Platform

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-16 02:48 UTC

   We are currently investigating this issue.

2. resolved 2026-02-16 03:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Metabase's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2025-10-20 06:00 UTC

   Our cloud service provider reported an outage on one of their key services in a region, leading to other services that depended on it to fail. Metabase token check service relies on one of these services to work, which led to our service to fail and all instances that depend on...

Excerpts are shortened. Read the full incident on Metabase's status page.

Affected: Metabase Cloud Platform

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-04-02 13:00 UTC

   We are currently investigating this issue.

2. monitoring 2025-04-02 13:46 UTC

   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.

3. resolved 2025-04-02 21:34 UTC

   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...

Excerpts are shortened. Read the full incident on Metabase's status page.

Failure mode: A code release introduced the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2025-01-06 19:30 UTC

   Metabase store was unavailable intermittently for an hour due to a problem during the store update.

Excerpts are shortened. Read the full incident on Metabase's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2023-11-15 10:30 UTC

   We had an issue in our EU cluster where instances were not being provisioned due to an autoscaler problem in that specific region. Issue is now resolved and we'll be monitoring the situation.

Excerpts are shortened. Read the full incident on Metabase's status page.

Affected: Metabase Cloud Platform

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2023-11-09 19:37 UTC

   We're investigating an issue in our cloud with certificate management that's causing browsers to receive incorrect certificates

2. resolved 2023-11-09 20:02 UTC

   Ingress controller certificates are now back to normal. You should be able to get the correct certificate in the browser now. We're very sorry for the inconvenience, we'll publish a retrospective about the issue in the next few days.

3. postmortem 2023-11-15 13:15 UTC

   **Summary** On Thursday Nov 9th the default certificate for the external Nginx ingress was replaced with a dummy certificate. Users attempting to reach their hosted instances would get an invalid certificate error. This was due to a misconfiguration in the new CI for releasing...

Excerpts are shortened. Read the full incident on Metabase's status page.

Affected: Metabase Store

Failure mode: A code release introduced the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-08-19 13:09 UTC

   We are preforming routine maintenance on the Metabase Store infrastructure. We expect it to be fully operational within the hour.

2. investigating 2023-08-19 13:50 UTC

   We are continuing to investigate this issue.

3. resolved 2023-08-19 13:52 UTC

   We are continuing to investigate this issue.

Excerpts are shortened. Read the full incident on Metabase's status page.

Affected: Metabase Cloud Platform

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-07-29 15:11 UTC

   Metabase Cloud customers are unable to send outbound emails temporarily

2. resolved 2023-07-29 18:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Metabase's status page.

Affected: Metabase Store

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-07-28 13:10 UTC

   Metabase customers trying to create a new cloud trial or cloud instance are unable to do so.

2. resolved 2023-07-29 10:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Metabase's status page.

Affected: Metabase Cloud Platform

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2023-07-28 13:01 UTC

   Metabase Cloud customers are currently unable to add new databases or edit database connections.

2. resolved 2023-07-29 09:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Metabase's status page.

Affected: Metabase Cloud Platform

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2023-07-24 19:30 UTC

   We are aware of an issue in Google identity services that's affecting our customers in LATAM. If you're running Metabase self hosted or in our Cloud and have Google SSO enabled, you'll see an error on the login screen that won't let you access the product. We will keep...

2. resolved 2023-07-25 01:37 UTC

   We've built and pushed new release artifacts to ship to our cloud and self hosted users who are facing this issue. Please refer to our website, Dockerhub or Github releases site to pull the new artifact that will solve this issue. Our Cloud instances will be upgraded as soon as...

Excerpts are shortened. Read the full incident on Metabase's status page.

Affected: Metabase Cloud Platform, Metabase Store

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. 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.

2. resolved 2023-06-13 23:13 UTC

   AWS reports that the service should be normalized now

Excerpts are shortened. Read the full incident on Metabase's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2023-04-05 18:00 UTC

   During the day we hit the quota in our email gateway and made the subscriptions and alerts of our Cloud hosted customers to fail. The service is restored now.

Excerpts are shortened. Read the full incident on Metabase's status page.

Affected: Metabase Cloud Platform

Failure mode: A configuration change caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2022-11-17 18:47 UTC

   We identified an issue with our Cloud. We're currently investigating

2. resolved 2022-11-17 19:14 UTC

   We have restored the service. We will provide a description of the issue in the next few days.

3. postmortem 2022-11-28 23:55 UTC

   While provisioning new K8S clusters in our AWS environment, DNS and load balancer related configurations were accidentally overwritten with wrong parameters, preventing ingress network access to all Metabase Cloud instances. We have restored the correct configurations and added...

Excerpts are shortened. Read the full incident on Metabase's status page.

Affected: Metabase Cloud Platform

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2022-11-01 13:22 UTC

   On Oct-31th, Google pushed a change without notice to their oAuth2 flows to the LATAM and other regions changing the name of a parameter that broke all SSO flows. We're actively working to push a new version of Metabase with a hotfix along upgrading our Cloud instances. In the...

2. identified 2022-11-01 19:40 UTC

   We finished the release process to obtain a new Metabase version that includes the fix for the issue. We'll be starting our Cloud upgrade process in the next hour.

3. resolved 2022-11-01 21:21 UTC

   We have started rolling out 44.6 version which includes the fix for the SSO issue. All instances should be upgraded in the next few hours.

Excerpts are shortened. Read the full incident on Metabase's status page.

Affected: Metabase Cloud Platform

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2022-10-11 17:43 UTC

   We're currently investigating an issue that is causing downtime on our Cloud

2. investigating 2022-10-11 17:43 UTC

   We are continuing to investigate this issue.

3. resolved 2022-10-11 17:53 UTC

   Service has been restored, we will provide more details about the issue as soon as possible. In case you have further questions, please reach out to our support email.

Excerpts are shortened. Read the full incident on Metabase's status page.

Affected: Metabase Cloud Platform

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2022-07-21 12:23 UTC

   We're aware that emails are not being sent on instances that run on Metabase Cloud. We're investigating the issue.

2. resolved 2022-07-21 12:53 UTC

   We've identified that we run over quota on our Cloud email service so we requested to increase the limits. Emails on our instances are now back to normal.

Excerpts are shortened. Read the full incident on Metabase's status page.

Affected: Metabase Cloud Platform

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. monitoring 2021-12-07 17:39 UTC

   Due to an ongoing issue with AWS us-east-1 region, a few our customers are experiencing temporary downtime. We’re monitoring the situation closely

2. monitoring 2021-12-07 23:45 UTC

   AWS has restored most of their services and as a result, our customers who were experiencing downtime are now operational. We will continue to monitor closely. Please do not hesitate to contact support if you have any questions or experience any issues.

3. resolved 2021-12-07 23:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Metabase's status page.

Affected: Metabase Cloud Platform

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2021-08-10 16:37 UTC

   We identified an issue in our Business tier customers that run on isolated environments. The issue appears to be an issue with our load balancers not being able to flag instances as healthy which results in application servers being recycled continously.

2. identified 2021-08-10 17:46 UTC

   We've identified a fix for the outage and we're in the process of issuing an update to resolve the situation

3. monitoring 2021-08-10 18:46 UTC

   We've deployed a fix and we're monitoring the health of the instances.

4. resolved 2021-08-10 20:38 UTC

   This incident has been resolved.

5. postmortem 2021-08-10 23:25 UTC

   A failure in the upgrade in our Elastic Beanstalk deployment for improving the timeout on reverse proxies led to instances not being able to revert back to previous version leaving them in an inconsistent state.

Excerpts are shortened. Read the full incident on Metabase's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2021-06-21 11:00 UTC

   A customer alerted us about instances not being created on our Cloud environment. After some investigations, our engineers detected that an endpoint in our Docker image registry was returning a 500 error status so our customers were receiving the emails about instance creation...

Excerpts are shortened. Read the full incident on Metabase's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2021-06-09 19:30 UTC

   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...

Excerpts are shortened. Read the full incident on Metabase's status page.