{
  "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-07-30T23:30:28.940Z"
  },
  "data": {
    "id": "incident_statuspage_scaleway_lsjyhv32y74p",
    "slug": "scaleway-instances-post-mortem-fr-par-1-issue-with-some-pro2-instances-2026-07-28",
    "title": "[Instances][POST MORTEM] - FR-PAR-1 - Issue with some PRO2 instances",
    "summary": "[Instances][POST MORTEM] - FR-PAR-1 - Issue with some PRO2 instances",
    "status": "resolved",
    "severity": "minor",
    "startedAt": "2026-07-28T05:00:00+00:00",
    "updatedAt": "2026-07-30T12:02:20.466+00:00",
    "resolvedAt": "2026-07-28T07:00:00+00:00",
    "provider": {
      "slug": "scaleway",
      "name": "Scaleway"
    },
    "affectedServices": [],
    "links": {
      "html": "/incidents/scaleway-instances-post-mortem-fr-par-1-issue-with-some-pro2-instances-2026-07-28",
      "api": "/api/v1/incidents/scaleway-instances-post-mortem-fr-par-1-issue-with-some-pro2-instances-2026-07-28",
      "providerHtml": "/providers/scaleway"
    },
    "impactSummary": "Scaleway reported a minor event for the affected tracked services.",
    "source": {
      "id": "source_scaleway_status",
      "kind": "official_api",
      "name": "Scaleway Status",
      "checkedAt": "2026-07-30T23:25:01.876+00:00",
      "officialUrl": "https://status.scaleway.com",
      "statusPageUrl": "https://status.scaleway.com"
    },
    "updates": [
      {
        "id": "update_statuspage_scaleway_lsjyhv32y74p_40zfkwkjv532",
        "status": "resolved",
        "body": "July 28, 2026 — 09:02 CEST: Our monitoring system detected connectivity issues affecting multiple PRO2 hypervisors in FR-PAR-1. Several servers appeared unreachable.",
        "createdAt": "2026-07-30T11:59:15.715+00:00"
      },
      {
        "id": "update_statuspage_scaleway_lsjyhv32y74p_6wl9qtvdgq6q",
        "status": "resolved",
        "body": "July 28, 2026 — 09:02 CEST: Our monitoring system detected connectivity issues affecting multiple PRO2 hypervisors in FR-PAR-1. Several servers appeared unreachable.\n\nJuly 28, 2026 — 09:14 CEST: The Scaleway Instances team began investigating the issue.\n\nJuly 28, 2026 — 09:14 CEST: Initial findings showed that the affected servers were still operational, but network traffic was being disrupted.\n\nJuly 28, 2026 — 09:16 CEST: An internal incident was opened, and the Network team joined the investigation.\n\nJuly 28, 2026 — 09:32 CEST: One of the two leaf switches showed uplink issues. However, part of the traffic was still being forwarded through the affected switch.\n\nJuly 28, 2026 — 09:35 CEST: We disabled the hypervisor ports connected to the faulty leaf switch to force all traffic through the redundant switch.\n\nJuly 28, 2026 — 09:35 CEST: Connectivity was restored for the affected instances.\n\nJuly 28, 2026 — 09:37 CEST: Logs from the faulty leaf switch showed that several ports went down, followed by one of its power supply units and then its uplinks. This sequence of events caused traffic black hole.\n\nJuly 28, 2026 — 09:38 CEST: We also identified multiple power supply alerts affecting several hypervisors in the same rack.\n\nJuly 28, 2026 — 09:44 CEST: A ticket was opened with our data center provider to request an electrical inspection of the rack.\n\nJuly 28, 2026 — 11:19 CEST: While reviewing the equipment logs, we identified a protective shutdown on one switch following a temperature alert. However, no abnormal temperature readings were detected by the other sensors in the rack.\n\nJuly 28, 2026 — 11:21 CEST: The data center provider performed a visual inspection and found no visible issues with the rack.\n\nJuly 28, 2026 — 15:09 CEST: The faulty component responsible for the incident was identified. A defective power supply unit caused electrical disruptions across the rack, triggering temperature alerts, power supply alerts on other devices, and the loss of several links on one leaf switch.\n\nJuly 29, 2026 — 14:21 CEST: All faulty components were replaced. The network connections that had been disabled were re-enabled. The service was fully restored and remained stable.",
        "createdAt": "2026-07-30T11:59:36.625+00:00"
      }
    ],
    "access": {
      "plan": "public",
      "keyed": false
    }
  }
}