{
  "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-09-04T22:16:53.098Z"
  },
  "data": {
    "id": "incident_statuspage_snowflake_09f44bx0y6lj",
    "slug": "snowflake-inc20000188-2026-08-31",
    "title": "INC20000188",
    "summary": "INC20000188",
    "status": "resolved",
    "severity": "critical",
    "startedAt": "2026-08-31T17:20:24.419+00:00",
    "updatedAt": "2026-08-31T19:44:40.497+00:00",
    "resolvedAt": "2026-08-31T19:44:40.483+00:00",
    "provider": {
      "slug": "snowflake",
      "name": "Snowflake"
    },
    "affectedServices": [],
    "links": {
      "html": "/incidents/snowflake-inc20000188-2026-08-31",
      "api": "/api/v1/incidents/snowflake-inc20000188-2026-08-31",
      "providerHtml": "/providers/snowflake",
      "alerts": "https://outagedeck.com/account?stack=snowflake&utm_source=api&utm_medium=response&utm_campaign=api_alerts&utm_content=incident"
    },
    "impactSummary": "Snowflake reported a critical event for the affected tracked services.",
    "source": {
      "id": "source_snowflake_status",
      "kind": "official_api",
      "name": "Snowflake Status",
      "checkedAt": "2026-09-04T22:15:02.141+00:00",
      "officialUrl": "https://status.snowflake.com",
      "statusPageUrl": "https://status.snowflake.com"
    },
    "updates": [
      {
        "id": "update_statuspage_snowflake_09f44bx0y6lj_ydpkzgcjcs15",
        "status": "investigating",
        "body": "Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 30 minutes.\n\nCustomer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data.",
        "createdAt": "2026-08-31T17:20:24.513+00:00"
      },
      {
        "id": "update_statuspage_snowflake_09f44bx0y6lj_fkmpw5fp1g2x",
        "status": "identified",
        "body": "Current status: We identified and have since reverted a problematic change as a potential mitigation. Initial telemetry indicates that the service is recovering. We will continue to monitor to confirm recovery. We'll provide an update within 30 minutes.\n\nCustomer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data.\n\nETA: Customers should be starting to see recovery, and our current estimate is that service will be restored within 1 hour.",
        "createdAt": "2026-08-31T17:31:52.003+00:00"
      },
      {
        "id": "update_statuspage_snowflake_09f44bx0y6lj_gt01t9gh1t98",
        "status": "identified",
        "body": "Current status: We are continuing to monitor service recovery, and have confirmed that the majority of service impact has been resolved as of 17:25 UTC with some residual impact to Snowsight access and Snowpipe Streaming. We'll provide an update within 30 minutes.\n\nCustomer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data.\n\nETA: Most services have returned to a healthy state. We expect any residual impact to Snowsight access and Snowpipe Streaming to be resolved within the next hour.\n\nIncident start time: 16:58 UTC August 31, 2026",
        "createdAt": "2026-08-31T17:59:28.755+00:00"
      },
      {
        "id": "update_statuspage_snowflake_09f44bx0y6lj_8ckrk9sk615l",
        "status": "monitoring",
        "body": "Current status: We've implemented a fix to address the residual impact, and we'll continue to monitor the environment until we're confident all services are functioning properly.\n\nCustomer experience: Customers hosted in the specified region may have been unable to access or use multiple core Snowflake services and features, including signing in to Snowsight, executing queries, loading and unloading data, and using Snowpark Container Services. Some customers may have also experienced delays with Snowpipe Streaming ingestion and elevated error rates when accessing Snowsight.\n\nThe majority of impact was resolved at 17:25 UTC; however, some customers may have continued to experience some residual errors or increased latency until approximately 18:10 UTC.\n\nIncident start time: 16:58 UTC August 31, 2026\nIncident end time: 18:10 UTC August 31, 2026\n\nPreliminary root cause: A recent change on the affected infrastructure inadvertently resulted in an increase in resource contention and subsequent impact to multiple Snowflake services and features.",
        "createdAt": "2026-08-31T18:45:33.306+00:00"
      },
      {
        "id": "update_statuspage_snowflake_09f44bx0y6lj_1817hrlmhmnk",
        "status": "resolved",
        "body": "Current status: We've monitored the environment to confirm that service was restored. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight.\n\nCustomer experience: Customers hosted in the specified region may have been unable to access or use multiple core Snowflake services and features, including signing in to Snowsight, executing queries, loading and unloading data, and using Snowpark Container Services. Some customers may have also experienced delays with Snowpipe Streaming ingestion and elevated error rates when accessing Snowsight.\n\nThe majority of impact was resolved at 17:25 UTC; however, some customers may have continued to experience some residual errors or increased latency until approximately 18:10 UTC.\n\nIncident start time: 16:58 UTC August 31, 2026\nIncident end time: 18:10 UTC August 31, 2026\n\nPreliminary root cause: A recent configuration change degraded backend processing due to a compatibility issue with how the affected systems handled requests. As a result, the infrastructure experienced resource contention and subsequent impact to multiple Snowflake services and features.\n\nA root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.",
        "createdAt": "2026-08-31T19:44:40.483+00:00"
      }
    ],
    "access": {
      "plan": "public",
      "keyed": false
    }
  }
}