{
  "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-11T19:04:34.276Z"
  },
  "data": {
    "id": "incident_statuspage_temporal_vc05z9f6rtvf",
    "slug": "temporal-some-customers-in-us-west-2-may-experience-elevated-rate-of-api-errors-2026-05-05-z9f6rtvf",
    "title": "Some customers in us-west-2 may experience elevated rate of API errors and high latency",
    "summary": "Some customers in us-west-2 may experience elevated rate of API errors and high latency",
    "status": "resolved",
    "stale": false,
    "severity": "major",
    "startedAt": "2026-05-05T05:43:53.841+00:00",
    "updatedAt": "2026-05-05T21:46:19.664+00:00",
    "resolvedAt": "2026-05-05T21:46:19.642+00:00",
    "provider": {
      "slug": "temporal",
      "name": "Temporal Cloud"
    },
    "affectedServices": [
      {
        "slug": "temporal-aws-regions",
        "name": "AWS Regions"
      }
    ],
    "regions": [
      "us-west-2"
    ],
    "links": {
      "html": "/incidents/temporal-some-customers-in-us-west-2-may-experience-elevated-rate-of-api-errors-2026-05-05-z9f6rtvf",
      "api": "/api/v1/incidents/temporal-some-customers-in-us-west-2-may-experience-elevated-rate-of-api-errors-2026-05-05-z9f6rtvf",
      "providerHtml": "/providers/temporal",
      "alerts": "https://outagedeck.com/account?stack=temporal&utm_source=api&utm_medium=response&utm_campaign=api_alerts&utm_content=incident"
    },
    "impactSummary": "Temporal Cloud reported a major event for the affected tracked services.",
    "source": {
      "id": "source_temporal_status",
      "kind": "official_api",
      "name": "Temporal Cloud Status",
      "checkedAt": "2026-10-11T19:00:10.151+00:00",
      "stale": false,
      "officialUrl": "https://status.temporal.io",
      "statusPageUrl": "https://status.temporal.io"
    },
    "updates": [
      {
        "id": "update_statuspage_temporal_vc05z9f6rtvf_g6hypld8tn6h",
        "status": "investigating",
        "body": "We are currently investigating the issue.",
        "createdAt": "2026-05-05T05:43:53.985+00:00"
      },
      {
        "id": "update_statuspage_temporal_vc05z9f6rtvf_kt4v1r9xw41l",
        "status": "investigating",
        "body": "This is still in investigation",
        "createdAt": "2026-05-05T06:22:16.388+00:00"
      },
      {
        "id": "update_statuspage_temporal_vc05z9f6rtvf_0fr35ckz5j12",
        "status": "identified",
        "body": "We are working to mitigate the issue. Error rates are recovering.",
        "createdAt": "2026-05-05T07:12:34.843+00:00"
      },
      {
        "id": "update_statuspage_temporal_vc05z9f6rtvf_1z95j0pp4jm0",
        "status": "identified",
        "body": "We continue working to mitigate the issue.",
        "createdAt": "2026-05-05T07:39:20.096+00:00"
      },
      {
        "id": "update_statuspage_temporal_vc05z9f6rtvf_nwy66hhy1xdx",
        "status": "monitoring",
        "body": "A fix has been implemented and we are monitoring the results.",
        "createdAt": "2026-05-05T07:50:10.338+00:00"
      },
      {
        "id": "update_statuspage_temporal_vc05z9f6rtvf_h23q5tb9rfd3",
        "status": "monitoring",
        "body": "API latencies and error rates have remained stable after a fix in history service and we continue to monitor the situation.",
        "createdAt": "2026-05-05T09:24:47.613+00:00"
      },
      {
        "id": "update_statuspage_temporal_vc05z9f6rtvf_lk1r9d9z20x7",
        "status": "monitoring",
        "body": "We are continuing to monitor the affected cell and have kept our status page in a monitoring state while we validate stability.\n\nAs a precaution, Multi-region Namespace traffic has been failed over to secondary regions, where it continues to be served normally.\n\nWhile we complete stabilization work, Multi-region Namespaces will continue running from secondary regions.\n\nOur current priority is to ensure the affected cell is stable and operating normally. Once confirmed, and the incident is resolved, we will restore Multi-region Namespace traffic to primary regions.\n\nFor Multi-region Namespaces failed over by Temporal, we will manage fail back. For manually failed over namespaces, customers can initiate fail back once the incident is resolved.",
        "createdAt": "2026-05-05T16:47:34.138+00:00"
      },
      {
        "id": "update_statuspage_temporal_vc05z9f6rtvf_wbg7f5b5dgdr",
        "status": "monitoring",
        "body": "Some customers may have experienced additional latencies and errors during this period (17:40 - 18:01 UTC) when we applied additional mitigation.",
        "createdAt": "2026-05-05T20:09:13.722+00:00"
      },
      {
        "id": "update_statuspage_temporal_vc05z9f6rtvf_jzjhm7fc3cqr",
        "status": "resolved",
        "body": "This incident has been resolved.",
        "createdAt": "2026-05-05T21:46:19.642+00:00"
      }
    ],
    "access": {
      "plan": "public",
      "keyed": false
    }
  }
}