Issue with Metabase Cloud
Nov 17, 18:47 UTCNov 17, 19:14 UTC
Duration
27m
Impact
Critical
Root cause
Not disclosed
Metabase, 90 days
0 incidents
Affected
Metabase Cloud Platform
Final update
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 additional process controls and automated checks to prevent this from happening in the future.
Timeline
- Postmortem · Nov 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 additional process controls and automated checks to prevent this from happening in the future.
- Resolved · Nov 17, 19:14 UTC
We have restored the service. We will provide a description of the issue in the next few days.
- Investigating · Nov 17, 18:47 UTC
We identified an issue with our Cloud. We're currently investigating
More from Metabase
Full historyMetabase Store is unavailablelasted 1h 39mSome Metabase functionality unavailablelasted 27mCloud service provider service outage leading to service interruptionlasted 0mSome Metabase Cloud customers hosted in the EU are reporting their site is down or slownesslasted 8h 34mMetabase Store unavailablelasted 0mEU region not availablelasted 0m