{
  "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-13T13:48:27.778Z"
  },
  "data": {
    "id": "incident_statuspage_upstash_774krfq667vd",
    "slug": "upstash-region-ap-northeast-1-outage-on-upstash-global-2026-03-06",
    "title": "Region ap-northeast-1 outage on Upstash Global",
    "summary": "Region ap-northeast-1 outage on Upstash Global",
    "status": "resolved",
    "severity": "critical",
    "startedAt": "2026-03-06T13:50:17.426+00:00",
    "updatedAt": "2026-03-09T10:09:03.241+00:00",
    "resolvedAt": "2026-03-06T14:49:57.18+00:00",
    "provider": {
      "slug": "upstash",
      "name": "Upstash"
    },
    "affectedServices": [],
    "links": {
      "html": "/incidents/upstash-region-ap-northeast-1-outage-on-upstash-global-2026-03-06",
      "api": "/api/v1/incidents/upstash-region-ap-northeast-1-outage-on-upstash-global-2026-03-06",
      "providerHtml": "/providers/upstash"
    },
    "impactSummary": "Upstash reported a critical event for the affected tracked services.",
    "source": {
      "id": "source_upstash_status",
      "kind": "official_api",
      "name": "Upstash Status",
      "checkedAt": "2026-07-13T13:45:03.124+00:00",
      "officialUrl": "https://status.upstash.com",
      "statusPageUrl": "https://status.upstash.com"
    },
    "updates": [
      {
        "id": "update_statuspage_upstash_774krfq667vd_7b3m0w0flz4x",
        "status": "investigating",
        "body": "We are currently investigating this issue.",
        "createdAt": "2026-03-06T13:50:17.509+00:00"
      },
      {
        "id": "update_statuspage_upstash_774krfq667vd_n5q3qptcmsv8",
        "status": "monitoring",
        "body": "A fix has been implemented and we are monitoring the results.",
        "createdAt": "2026-03-06T14:08:22.691+00:00"
      },
      {
        "id": "update_statuspage_upstash_774krfq667vd_s2km3lxx8zfz",
        "status": "resolved",
        "body": "This incident has been resolved.",
        "createdAt": "2026-03-06T14:49:57.18+00:00"
      },
      {
        "id": "update_statuspage_upstash_774krfq667vd_bspdxxc2c69s",
        "status": "resolved",
        "body": "On March 6, between approximately 13:44–14:07 UTC, some databases experienced elevated latency and connection errors in the Tokyo \\(ap-northeast-1\\) region.\n\nThe issue was caused by a sudden spike in traffic that significantly increased network utilization and connection load on a subset of nodes.\n\nOur team mitigated the incident by scaling up capacity in the region and redistributing load across additional nodes. Service recovered once the additional capacity was brought online.\n\nResolution\n\nWe have increased the number of machines in the Tokyo region to provide additional headroom and reduce the likelihood of similar incidents during traffic spikes.\n\nNext Steps\n\nWe are continuing to review capacity safeguards and connection-handling limits to improve resilience against sudden traffic surges.",
        "createdAt": "2026-03-09T10:07:57.441+00:00"
      }
    ],
    "access": {
      "plan": "public",
      "keyed": false
    }
  }
}