{
  "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-10-11T09:06:16.635Z"
  },
  "data": {
    "id": "incident_statuspage_linode_nkkf1pkgkrh4",
    "slug": "linode-emerging-service-issue-networking-us-mia-miami-2026-06-16",
    "title": "Emerging Service Issue - Networking - US-MIA (Miami)",
    "summary": "Emerging Service Issue - Networking - US-MIA (Miami)",
    "status": "resolved",
    "stale": false,
    "severity": "minor",
    "startedAt": "2026-06-16T14:29:21.687+00:00",
    "updatedAt": "2026-06-22T18:54:54.515+00:00",
    "resolvedAt": "2026-06-16T17:18:40.237+00:00",
    "provider": {
      "slug": "linode",
      "name": "Linode"
    },
    "affectedServices": [
      {
        "slug": "linode-regions",
        "name": "Compute Regions"
      }
    ],
    "links": {
      "html": "/incidents/linode-emerging-service-issue-networking-us-mia-miami-2026-06-16",
      "api": "/api/v1/incidents/linode-emerging-service-issue-networking-us-mia-miami-2026-06-16",
      "providerHtml": "/providers/linode",
      "alerts": "https://outagedeck.com/account?stack=linode&utm_source=api&utm_medium=response&utm_campaign=api_alerts&utm_content=incident"
    },
    "impactSummary": "Linode reported this event with no impact level.",
    "source": {
      "id": "source_linode_status",
      "kind": "official_api",
      "name": "Linode Status",
      "checkedAt": "2026-10-11T09:00:11.057+00:00",
      "stale": false,
      "officialUrl": "https://status.linode.com",
      "statusPageUrl": "https://status.linode.com"
    },
    "updates": [
      {
        "id": "update_statuspage_linode_nkkf1pkgkrh4_6kc2kp87j717",
        "status": "investigating",
        "body": "Our team is investigating an emerging service issue affecting networking in US-MIA (Miami). We will share additional updates as we have more information.",
        "createdAt": "2026-06-16T14:29:21.764+00:00"
      },
      {
        "id": "update_statuspage_linode_nkkf1pkgkrh4_qsxwxygrkyjz",
        "status": "resolved",
        "body": "We haven’t observed any additional connectivity issues in our US-MIA (Miami) data center, and will now consider this incident resolved. If you continue to experience problems, please <a href=\"https://cloud.linode.com/support/tickets\">open a Support ticket</a> for assistance.",
        "createdAt": "2026-06-16T17:18:40.237+00:00"
      },
      {
        "id": "update_statuspage_linode_nkkf1pkgkrh4_glyctlylc1j5",
        "status": "resolved",
        "body": "On June 16, 2026 Akamai investigated an  instance of performance degradation and connectivity slowness observed affecting applications within the Miami compute environment. This event occurred between around 13:37 UTC and 14:20 UTC on June 16, 2026.  The Investigation revealed a configuration change on an Akamai device in Miami triggered an underlying vendor software defect within the routing platform's operating system.  Actions were taken to mitigate the impact and restore intended routing paths.\n\nTo prevent any further recurrence, we have temporarily suspended related configuration changes.\n\nRoot Cause: During a routine, scheduled configuration update to an aggregated network link, an underlying vendor software defect within the routing platform's operating system was triggered.\n\nWhile the configuration change itself was standard and correct, the software bug caused the router to incorrectly process internal MPLS \\(Multiprotocol Label Switching\\) routing tables. Instead of applying changes only to the targeted link, the software inadvertently cleared the routing instructions for unrelated network interfaces. This unintended removal of routing paths led to the subsequent traffic disruption.\n\nWe apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent recurrence.\n\nThis summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.",
        "createdAt": "2026-06-22T18:54:27.617+00:00"
      }
    ],
    "access": {
      "plan": "public",
      "keyed": false
    }
  }
}