{
  "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-07-30T23:26:30.378Z"
  },
  "data": {
    "id": "incident_statuspage_snowflake_0js22rxjm66q",
    "slug": "snowflake-inc20000115-2026-07-30",
    "title": "INC20000115",
    "summary": "INC20000115",
    "status": "resolved",
    "severity": "critical",
    "startedAt": "2026-07-30T03:00:18.446+00:00",
    "updatedAt": "2026-07-30T04:56:55.384+00:00",
    "resolvedAt": "2026-07-30T04:56:55.367+00:00",
    "provider": {
      "slug": "snowflake",
      "name": "Snowflake"
    },
    "affectedServices": [],
    "links": {
      "html": "/incidents/snowflake-inc20000115-2026-07-30",
      "api": "/api/v1/incidents/snowflake-inc20000115-2026-07-30",
      "providerHtml": "/providers/snowflake"
    },
    "impactSummary": "Snowflake reported a critical event for the affected tracked services.",
    "source": {
      "id": "source_snowflake_status",
      "kind": "official_api",
      "name": "Snowflake Status",
      "checkedAt": "2026-07-30T23:20:29.477+00:00",
      "officialUrl": "https://status.snowflake.com",
      "statusPageUrl": "https://status.snowflake.com"
    },
    "updates": [
      {
        "id": "update_statuspage_snowflake_0js22rxjm66q_br04cnktjs68",
        "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 log in to Snowsight. Affected users may encounter HTTP 404 errors or \"Incoming request with IP/Token is not allowed to access Snowflake\" errors when attempting to access Snowsight via private endpoints.",
        "createdAt": "2026-07-30T03:00:18.64+00:00"
      },
      {
        "id": "update_statuspage_snowflake_0js22rxjm66q_j1xwwn4ntx9p",
        "status": "identified",
        "body": "Current status: We've identified the source of the issue, and we're developing and implementing a fix to restore service. We'll provide another update within 30 minutes.\n\nCustomer experience: Customers hosted in the specified regions may be unable to log in to Snowsight. Affected users may encounter HTTP 404 errors or \"Incoming request with IP/Token is not allowed to access Snowflake\" errors when attempting to access Snowsight via private endpoints.\n\nETA: Our current estimate is that service will be restored within 1 hour.\n\nWorkaround: There are currently no available workarounds for this issue.",
        "createdAt": "2026-07-30T03:30:18.363+00:00"
      },
      {
        "id": "update_statuspage_snowflake_0js22rxjm66q_5qqxhrhhpszv",
        "status": "monitoring",
        "body": "Current status: We've reverted a recent configuration change and confirmed that service has been restored. We'll continue to monitor the environment until we're confident all services are functioning properly.\n\nCustomer experience: Customers hosted in the specified regions may have been unable to log in to Snowsight. Affected users may have encountered HTTP 404 errors or \"Incoming request with IP/Token is not allowed to access Snowflake\" errors when attempting to access Snowsight via private endpoints.\n\nWorkaround: There were no available workarounds for this issue.\n\nIncident start time: 00:18 UTC July 30, 2026\nIncident end time: 03:52 UTC July 30, 2026\n\nPreliminary root cause: A recent configuration change to a subset of the routing infrastructure caused connectivity failures for customers accessing Snowsight via private endpoints.",
        "createdAt": "2026-07-30T04:17:38.335+00:00"
      },
      {
        "id": "update_statuspage_snowflake_0js22rxjm66q_pc3w1xxvf05j",
        "status": "resolved",
        "body": "Current status: We've monitored the environment and confirmed that reverting the configuration change restored service. 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 been unable to log in to Snowsight. Affected users may have encountered HTTP 404 errors or \"Incoming request with IP/Token is not allowed to access Snowflake\" errors when attempting to access Snowsight via private endpoints.\n\nWorkaround: There were no available workarounds for this issue.\n\nIncident start time: 00:18 UTC July 30, 2026\nIncident end time: 03:52 UTC July 30, 2026\n\nPreliminary root cause: A recent configuration change to a subset of the routing infrastructure caused connectivity failures for customers accessing Snowsight via private endpoints.\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-07-30T04:56:55.367+00:00"
      }
    ],
    "access": {
      "plan": "public",
      "keyed": false
    }
  }
}