{
  "meta": {
    "version": "v1",
    "pricing": {
      "public": {
        "label": "Public",
        "description": "Read-only API access for lightweight status checks and public integrations."
      },
      "premium": {
        "label": "Premium",
        "description": "API keys with higher hourly quotas, plus Slack, Teams, Discord, webhook, and email outage alerts across your vendor stack."
      }
    },
    "generatedAt": "2026-11-19T05:10:38.083Z"
  },
  "data": {
    "id": "incident_statuspage_metabase_n2t6lybnmrp0",
    "slug": "metabase-issue-with-ssl-certificates-2023-11-09",
    "title": "Issue with SSL certificates",
    "summary": "Issue with SSL certificates",
    "status": "resolved",
    "stale": false,
    "severity": "critical",
    "startedAt": "2023-11-09T19:37:20+00:00",
    "updatedAt": "2023-11-15T13:21:50.718+00:00",
    "resolvedAt": "2023-11-09T20:02:12.559+00:00",
    "provider": {
      "slug": "metabase",
      "name": "Metabase"
    },
    "affectedServices": [
      {
        "slug": "metabase-platform",
        "name": "Cloud platform"
      }
    ],
    "links": {
      "html": "/incidents/metabase-issue-with-ssl-certificates-2023-11-09",
      "api": "/api/v1/incidents/metabase-issue-with-ssl-certificates-2023-11-09",
      "providerHtml": "/providers/metabase",
      "alerts": "https://outagedeck.com/account?stack=metabase&utm_source=api&utm_medium=response&utm_campaign=api_alerts&utm_content=incident"
    },
    "impactSummary": "Metabase reported a critical event for the affected tracked services.",
    "source": {
      "id": "source_metabase_status",
      "kind": "official_api",
      "name": "Metabase Cloud Status",
      "checkedAt": "2026-11-19T05:10:12.108+00:00",
      "stale": false,
      "officialUrl": "https://status.metabase.com",
      "statusPageUrl": "https://status.metabase.com"
    },
    "updates": [
      {
        "id": "update_statuspage_metabase_n2t6lybnmrp0_2862md4gvqfw",
        "status": "investigating",
        "body": "We're investigating an issue in our cloud with certificate management that's causing browsers to receive incorrect certificates",
        "createdAt": "2023-11-09T19:37:20.248+00:00"
      },
      {
        "id": "update_statuspage_metabase_n2t6lybnmrp0_fr1235xcx7f7",
        "status": "resolved",
        "body": "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.",
        "createdAt": "2023-11-09T20:02:12.559+00:00"
      },
      {
        "id": "update_statuspage_metabase_n2t6lybnmrp0_w1gq50psgtvp",
        "status": "resolved",
        "body": "**Summary**\n\nOn 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 our helm charts that used the internal Nginx ingress values files for the external Nginx ingress.\n\n**Impact**\n\nAll hosted customers not using custom domains were affected.\n\n**How was the root cause diagnosed?**\n\nWe identified that the values were properly set in the values files. We Investigated the CI steps to determine why the correct values were not set. It was determined that the wrong values files were being used for external Nginx ingress.\n\n**How we’ll make this not happen again?**\n\n* Update staging and production value files to match.\n* Add alert to pagerduty for non-custom domains \\(catch alerts faster\\)",
        "createdAt": "2023-11-15T13:15:58.952+00:00"
      }
    ],
    "access": {
      "plan": "public",
      "keyed": false
    }
  }
}