{
  "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, Discord, webhook, and email outage alerts across your vendor stack."
      }
    },
    "generatedAt": "2026-07-22T20:03:37.954Z"
  },
  "data": {
    "id": "incident_statuspage_scaleway_jg2npy29tp0c",
    "slug": "scaleway-caas-fr-par-namespaces-and-containers-stuck-in-transient-statuses-2026-07-22",
    "title": "[CAAS] - [fr-par] - namespaces and containers stuck in transient statuses",
    "summary": "[CAAS] - [fr-par] - namespaces and containers stuck in transient statuses",
    "status": "resolved",
    "severity": "minor",
    "startedAt": "2026-07-22T09:33:41.83+00:00",
    "updatedAt": "2026-07-22T09:55:33.338+00:00",
    "resolvedAt": "2026-07-22T09:55:33.309+00:00",
    "provider": {
      "slug": "scaleway",
      "name": "Scaleway"
    },
    "affectedServices": [],
    "links": {
      "html": "/incidents/scaleway-caas-fr-par-namespaces-and-containers-stuck-in-transient-statuses-2026-07-22",
      "api": "/api/v1/incidents/scaleway-caas-fr-par-namespaces-and-containers-stuck-in-transient-statuses-2026-07-22",
      "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-22T19:55:17.166+00:00",
      "officialUrl": "https://status.scaleway.com",
      "statusPageUrl": "https://status.scaleway.com"
    },
    "updates": [
      {
        "id": "update_statuspage_scaleway_jg2npy29tp0c_zpv5gb3ykpj9",
        "status": "identified",
        "body": "Following incident on Compute instances (https://status.scaleway.com/incidents/bsp2y5fysy9w), a few Serverless Containers and namespaces on fr-par region have been stuck in transient statuses (updating/deleting) during the night.\n\nNot all resources were impacted, only a fraction on one part of our infrastructure (~1/10). On this part, impacted resources were either:\n\n- updated between 2026-07-21 21:07 UTC and 2026-07-21 22:05 UTC\n- or deleted between 2026-07-21 21:33 UTC and 2026-07-22 03:18 UTC\n\nWe have fixed the statuses, so resources are not stuck anymore. But, this would require impacted users to update or delete again their namespaces/containers if the status is in error with one of these error messages:\n\n- For previously \"updating\" containers: Last container update could not be processed successfully. Please try again\n- For previously \"deleting\" containers: Container could not be succesfully deleted. Please try again\n- For previously \"updating\" namespaces: Last namespace update could not be processed successfully. Please try again\n- For previously \"deleting\" namespaces: Namespace could not be succesfully deleted. Please try again\n\nSorry about any inconvenience.",
        "createdAt": "2026-07-22T09:33:41.952+00:00"
      },
      {
        "id": "update_statuspage_scaleway_jg2npy29tp0c_f86dzdknf816",
        "status": "resolved",
        "body": "Incident is now resolved. Please read instructions in the previous message if your container or namespace has one of the following error messages.\n\nSorry again for any inconvenience.",
        "createdAt": "2026-07-22T09:55:33.309+00:00"
      }
    ],
    "access": {
      "plan": "public",
      "keyed": false
    }
  }
}