{
  "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-17T02:40:53.236Z"
  },
  "data": {
    "id": "incident_statuspage_asana_7402jg0zwnnv",
    "slug": "asana-asana-application-incident-2026-08-31",
    "title": "Asana full outage for some users (2 hours, 25% outage)",
    "summary": "Asana full outage for some users (2 hours, 25% outage)",
    "status": "resolved",
    "stale": false,
    "severity": "major",
    "startedAt": "2026-08-31T15:14:14.063+00:00",
    "updatedAt": "2026-09-02T21:38:00.116+00:00",
    "resolvedAt": "2026-08-31T17:18:36.736+00:00",
    "provider": {
      "slug": "asana",
      "name": "Asana"
    },
    "affectedServices": [
      {
        "slug": "asana-us",
        "name": "US Region"
      }
    ],
    "links": {
      "html": "/incidents/asana-asana-application-incident-2026-08-31",
      "api": "/api/v1/incidents/asana-asana-application-incident-2026-08-31",
      "providerHtml": "/providers/asana",
      "alerts": "https://outagedeck.com/account?stack=asana&utm_source=api&utm_medium=response&utm_campaign=api_alerts&utm_content=incident"
    },
    "impactSummary": "Asana reported a major event for the affected tracked services.",
    "source": {
      "id": "source_asana_status",
      "kind": "official_api",
      "name": "Asana Status",
      "checkedAt": "2026-10-17T02:40:10.614+00:00",
      "stale": false,
      "officialUrl": "https://status.asana.com",
      "statusPageUrl": "https://status.asana.com"
    },
    "updates": [
      {
        "id": "update_statuspage_asana_7402jg0zwnnv_1hfzghtqhc3f",
        "status": "investigating",
        "body": "We are investigating alerts for slow performance and application errors.",
        "createdAt": "2026-08-31T15:14:14.212+00:00"
      },
      {
        "id": "update_statuspage_asana_7402jg0zwnnv_jnwgjkw7qcy4",
        "status": "investigating",
        "body": "We are continuing to investigate the issue; we have reverted recent changes, and are working to identify the source of the errors.",
        "createdAt": "2026-08-31T15:55:24.277+00:00"
      },
      {
        "id": "update_statuspage_asana_7402jg0zwnnv_h6v08w77gbhs",
        "status": "investigating",
        "body": "We have made configuration changes and see partial recovery, but we continue to see some elevated errors.",
        "createdAt": "2026-08-31T16:24:35.633+00:00"
      },
      {
        "id": "update_statuspage_asana_7402jg0zwnnv_mq4g4x3ktw68",
        "status": "monitoring",
        "body": "We've applied a fix are seeing signs of recovery.",
        "createdAt": "2026-08-31T16:47:28.394+00:00"
      },
      {
        "id": "update_statuspage_asana_7402jg0zwnnv_dpsgyh33j9td",
        "status": "resolved",
        "body": "User-facing symptoms have recovered. We'll continue to monitor, and will prioritize a retrospective to understand and prevent similar incidents in the future.",
        "createdAt": "2026-08-31T17:18:36.736+00:00"
      },
      {
        "id": "update_statuspage_asana_7402jg0zwnnv_6rdjwdjvcvsw",
        "status": "resolved",
        "body": "We’ve been working to add a caching layer to our update pipeline, tuning it carefully and rolling it out gradually. On Wednesday, August 26 we enabled it for most use cases, and it initially performed well.\n\nOn Monday, August 31, a combination of unrelated infrastructure changes and peak traffic pushed the cache past its scaling limits. Once that threshold was crossed, the cache became unusable, and many pods serving read traffic for the Asana application could no longer serve it.\n\nWe mitigated the incident by reverting the system to use the previous, non-cached code path. The revert was successful, but recovery took longer than we would expect for this class of issue.\n\nA fuller analysis is underway. We will follow up with root causes, action items, and improvements, including why recovery took as long as it did.\n\nWe were fully down for about 25% of our users, for 2 hours, 15 minutes.",
        "createdAt": "2026-09-02T21:29:30.165+00:00"
      }
    ],
    "access": {
      "plan": "public",
      "keyed": false
    }
  }
}