{
  "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-08-18T19:12:11.822Z"
  },
  "data": {
    "id": "incident_statuspage_snowflake_yk5sqhcjp266",
    "slug": "snowflake-inc20000163-2026-08-18",
    "title": "INC20000163",
    "summary": "INC20000163",
    "status": "resolved",
    "severity": "major",
    "startedAt": "2026-08-18T12:58:11.116+00:00",
    "updatedAt": "2026-08-18T14:51:45.821+00:00",
    "resolvedAt": "2026-08-18T14:51:45.803+00:00",
    "provider": {
      "slug": "snowflake",
      "name": "Snowflake"
    },
    "affectedServices": [],
    "links": {
      "html": "/incidents/snowflake-inc20000163-2026-08-18",
      "api": "/api/v1/incidents/snowflake-inc20000163-2026-08-18",
      "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 major event for the affected tracked services.",
    "source": {
      "id": "source_snowflake_status",
      "kind": "official_api",
      "name": "Snowflake Status",
      "checkedAt": "2026-08-18T19:10:16.933+00:00",
      "officialUrl": "https://status.snowflake.com",
      "statusPageUrl": "https://status.snowflake.com"
    },
    "updates": [
      {
        "id": "update_statuspage_snowflake_yk5sqhcjp266_6yj3ht9xl4zm",
        "status": "investigating",
        "body": "Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 1 hour.\n\nCustomer experience: Customers hosted in the specified regions may experience issues with AI and ML functionality. Specifically, when using Cortex Code in Snowsight, customer may see the following: “Internal Server error: You may need to start a new chat.”. All other Snowflake features are not impacted.\n\nETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures.\n\nIncident start time: 11:10 UTC August 18, 2026",
        "createdAt": "2026-08-18T12:58:11.233+00:00"
      },
      {
        "id": "update_statuspage_snowflake_yk5sqhcjp266_j2k28st5qtvg",
        "status": "identified",
        "body": "Current status: We've identified an issue with container scheduling in our compute infrastructure that is affecting AI and ML functionality, and we're implementing a fix to restore service. We'll provide another update within 30 minutes.\n\nCustomer experience: Customers hosted in the specified region may be unable to use Cortex Code in Snowsight and may see the following error message: \"Internal Server error: You may need to start a new chat.\" All other Snowflake features are not impacted.\n\nETA: Our current estimate is that service will be restored within 30 minutes.\n\nIncident start time: 11:20 UTC August 18, 2026\n\nPreliminary root cause: Resource exhaustion in the compute infrastructure caused container scheduling failures, resulting in AI and ML functionality becoming unavailable.",
        "createdAt": "2026-08-18T13:33:15.008+00:00"
      },
      {
        "id": "update_statuspage_snowflake_yk5sqhcjp266_ds3fqcpdhsw3",
        "status": "monitoring",
        "body": "Current status: We've implemented the fix for this issue, and we'll continue to monitor the environment until we're confident all services are functioning properly. We'll provide another update within 60 minutes.\n\nCustomer experience: Customers hosted in the specified region may have been unable to use Cortex Code in Snowsight and may have seen the following error message: \"Internal Server error: You may need to start a new chat.\" All other Snowflake features are not impacted.\n\nIncident start time: 11:20 UTC August 18, 2026\nIncident end time: 13:45 UTC August 18, 2026\n\nPreliminary root cause: Resource exhaustion in the compute infrastructure caused container scheduling failures, resulting in AI and ML functionality becoming unavailable.",
        "createdAt": "2026-08-18T13:55:12.871+00:00"
      },
      {
        "id": "update_statuspage_snowflake_yk5sqhcjp266_7wlw7tl9g08w",
        "status": "resolved",
        "body": "Current status: We've implemented the fix for this issue and 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 regions may have experienced issues with AI and ML functionality. Specifically, when using Cortex Code in Snowsight, customers may have seen the following: “Internal Server error: You may need to start a new chat.” All other Snowflake features were not impacted.\n\nIncident start time: 11:20 UTC August 18, 2026\nIncident end time: 13:45 UTC August 18, 2026\n\nPreliminary root cause: Resource exhaustion in the compute infrastructure caused container scheduling failures, resulting in AI and ML functionality becoming unavailable.\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-18T14:51:45.803+00:00"
      }
    ],
    "access": {
      "plan": "public",
      "keyed": false
    }
  }
}