{
  "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:20.785Z"
  },
  "data": {
    "id": "incident_statuspage_snowflake_v8nyb5fhd95v",
    "slug": "snowflake-inc20000158-2026-08-14",
    "title": "INC20000158",
    "summary": "INC20000158",
    "status": "resolved",
    "severity": "critical",
    "startedAt": "2026-08-14T17:29:49.596+00:00",
    "updatedAt": "2026-08-14T19:35:34.082+00:00",
    "resolvedAt": "2026-08-14T19:35:34.064+00:00",
    "provider": {
      "slug": "snowflake",
      "name": "Snowflake"
    },
    "affectedServices": [],
    "links": {
      "html": "/incidents/snowflake-inc20000158-2026-08-14",
      "api": "/api/v1/incidents/snowflake-inc20000158-2026-08-14",
      "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-08-18T19:10:16.933+00:00",
      "officialUrl": "https://status.snowflake.com",
      "statusPageUrl": "https://status.snowflake.com"
    },
    "updates": [
      {
        "id": "update_statuspage_snowflake_v8nyb5fhd95v_jzjf1l8j9wrf",
        "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 using Snowsight. Affected users may be unable to sign in and may observe \"503 Service Unavailable\" errors.\n\nIncident start time: 17:05 UTC August 14, 2026",
        "createdAt": "2026-08-14T17:29:49.705+00:00"
      },
      {
        "id": "update_statuspage_snowflake_v8nyb5fhd95v_t0rc7k340k60",
        "status": "identified",
        "body": "Current status: We've identified a system configuration issue affecting Snowsight, 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 access or use Snowsight and may observe \"503 Service Unavailable\" errors.\n\nETA: Our current estimate is that service will be restored within 30 minutes.\n\nWorkaround: There are currently no available workarounds for this issue.\n\nIncident start time: 17:05 UTC August 14, 2026",
        "createdAt": "2026-08-14T17:58:31.804+00:00"
      },
      {
        "id": "update_statuspage_snowflake_v8nyb5fhd95v_wy45htv90b7k",
        "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.\n\nCustomer experience: Customers hosted in the specified region may have been unable to access or use Snowsight and may have seen \"503 Service Unavailable\" errors.\n\nIncident start time: 17:05 UTC August 14, 2026\nIncident end time: 18:12 UTC August 14, 2026\n\nPreliminary root cause: A routine system configuration change intended to optimize performance caused elevated latency in the metadata layer, resulting in service disruptions. Once identified, the configuration was reverted and affected service infrastructure was restarted to restore service.",
        "createdAt": "2026-08-14T18:30:21.726+00:00"
      },
      {
        "id": "update_statuspage_snowflake_v8nyb5fhd95v_8qt3nkgh6fxf",
        "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 region may be unable to access or use Snowsight and may observe \"503 Service Unavailable\" errors.\n\nIncident start time: 17:05 UTC August 14, 2026\nIncident end time: 18:12 UTC August 14, 2026\n\nPreliminary root cause: A routine system configuration change intended to optimize performance caused elevated latency in the metadata layer, resulting in service disruptions. Once identified, the configuration was reverted and affected service infrastructure was restarted to restore service.\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-14T19:35:34.064+00:00"
      }
    ],
    "access": {
      "plan": "public",
      "keyed": false
    }
  }
}