クラウド・サービスの障害情報
8月13日(木)
Metabase Store is unavailable
Aug 12 , 20:52 UTC Resolved - This incident has been resolved. Aug 12 , 19:13 UTC Investigating - We are performing maintenance on the Metabase Store infrastructure. We expect it to be operational within an hour.
2月16日(月)
Some Metabase functionality unavailable
Feb 16 , 03:15 UTC Resolved - This incident has been resolved. Feb 16 , 02:48 UTC Investigating - We are currently investigating this issue.
10月20日(月)
Cloud service provider service outage leading to service interruption
Oct 20 , 06:00 UTC Resolved - 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 this service were not able to start or be downgraded to non-premium instances (without any premium features working). Instances that did this token check before the outage did not see any issues. Service is now fully recovered
4月3日(木)
Some Metabase Cloud customers hosted in the EU are reporting their site is down or slowness
Apr 2 , 21:34 UTC Resolved - 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. Apr 2 , 13:46 UTC Monitoring - 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. Apr 2 , 13:00 UTC Investigating - We are currently investigating this issue.
1月7日(火)
Metabase Store unavailable
Jan 6 , 19:30 UTC Resolved - Metabase store was unavailable intermittently for an hour due to a problem during the store update.
11月15日(水)
EU region not available
Nov 15 , 10:30 UTC Resolved - 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.
11月10日(金)
Issue with SSL certificates
Nov 9 , 20:02 UTC Resolved - 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. Nov 9 , 19:37 UTC Investigating - We're investigating an issue in our cloud with certificate management that's causing browsers to receive incorrect certificates
7月30日(日)
Unable to send outbound emails
Jul 29 , 18:48 UTC Resolved - This incident has been resolved. Jul 29 , 15:11 UTC Investigating - Metabase Cloud customers are unable to send outbound emails temporarily
7月29日(土)
Unable to create new Metabase cloud instances
Jul 29 , 10:21 UTC Resolved - This incident has been resolved. Jul 28 , 13:10 UTC Investigating - Metabase customers trying to create a new cloud trial or cloud instance are unable to do so.
Unable to create new database connections
Jul 29 , 09:06 UTC Resolved - This incident has been resolved. Jul 28 , 13:01 UTC Investigating - Metabase Cloud customers are currently unable to add new databases or edit database connections.
7月25日(火)
Google SSO bug affecting LATAM customers
Jul 25 , 01:37 UTC Resolved - 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 we can in order to normalize the service. Jul 24 , 19:30 UTC Investigating - 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 sc…
6月14日(水)
Problems when creating instances
Jun 13 , 23:13 UTC Resolved - AWS reports that the service should be normalized now Jun 13 , 19:56 UTC 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.
4月6日(木)
Cloud email quota exceeded
Apr 5 , 18:00 UTC Resolved - 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.
11月18日(金)
Issue with Metabase Cloud
Nov 17 , 19:14 UTC Resolved - We have restored the service. We will provide a description of the issue in the next few days. Nov 17 , 18:47 UTC Investigating - We identified an issue with our Cloud. We're currently investigating
11月2日(水)
Google SSO might not work in LATAM/other regions
Nov 1 , 21:21 UTC Resolved - 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. Nov 1 , 19:40 UTC Update - 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. Nov 1 , 13:22 UTC Identified - 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 o…
10月12日(水)
Issues on our Cloud
Oct 11 , 17:53 UTC Resolved - 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. Oct 11 , 17:43 UTC Update - We are continuing to investigate this issue. Oct 11 , 17:43 UTC Investigating - We're currently investigating an issue that is causing downtime on our Cloud
7月21日(木)
Emails not sending
Jul 21 , 12:53 UTC Resolved - 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. Jul 21 , 12:23 UTC Investigating - We're aware that emails are not being sent on instances that run on Metabase Cloud. We're investigating the issue.
12月8日(水)
AWS Outage
Dec 7 , 23:51 UTC Resolved - This incident has been resolved. Dec 7 , 23:45 UTC Update - 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. Dec 7 , 17:39 UTC Monitoring - 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
8月11日(水)
Degraded service in our Business tier
Aug 10 , 20:38 UTC Resolved - This incident has been resolved. Aug 10 , 18:46 UTC Monitoring - We've deployed a fix and we're monitoring the health of the instances. Aug 10 , 17:46 UTC Identified - We've identified a fix for the outage and we're in the process of issuing an update to resolve the situation Aug 10 , 16:37 UTC Investigating - 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.
6月21日(月)
Issues creating new instances in Metabase Cloud
Jun 21 , 11:00 UTC Resolved - 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 but there was no instance at all. Systems should be back to normal now.
6月10日(木)
Database incident
Jun 9 , 19:30 UTC Resolved - 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 they found out that a cluster resize didn't apply correctly due to a configuration mismatch between the configuration scripts and the CSP offering resulting in downtime. The configuration script was modified to be compatible with the CSP and the database instances came back online.