Snapshot 14743
Normalized text
Scripts and page chrome removed; this is what change detection compares.
{
"pages": [
{
"end_time": "2026-09-30T23:59:59Z",
"months": [
{
"incidents": [
{
"code": "3ykqqwk3s758",
"impact": "critical",
"message": "Current status: We've coordinated with our third-party cloud platform to implement the fix for this issue, and 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 regions may have been unable to access or use multiple core Snowflake services and features. Affected users may have been unable to sign in, execute queries, or manage data.\n\nIncident start time: 00:25 UTC September 27, 2026\nIncident end time: 01:00 UTC September 27, 2026\n\nPreliminary root cause: An issue with our third-party cloud platform caused impact to multiple Snowflake services and features. We have engaged with our third-party for further details.\n\nA root cause analysis (RCA) will be conducted and a summary will be made available within 10 business days.",
"name": "INC20000239",
"timestamp": "Sep \u003cvar data-var='date'\u003e27\u003c/var\u003e, \u003cvar data-var='time'\u003e02:15\u003c/var\u003e - \u003cvar data-var='time'\u003e03:16\u003c/var\u003e UTC"
},
{
"code": "g8td4vy3qjk7",
"impact": "critical",
"message": "Current status: We've implemented the fix for this issue and monitored the environment to confirm that service was restored. Most impact was resolved by 22:59 UTC, with the remaining backlog for scheduled and serverless task execution fully clearing by 23:43 UTC. 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 access or use multiple core Snowflake services and features. Affected users may have been unable to sign in, execute queries, or manage data, and may have been unable to connect to Snowflake via private connectivity, such as AWS PrivateLink. Additionally, they may have been unable to continuously stream data into Snowflake using Snowpipe Streaming, and customers using scheduled or serverless tasks may have experienced delayed task execution.\n\nIncident start time: 22:35 UTC September 25, 2026\nIncident end time: 23:43 UTC September 25, 2026\n\nPreliminary root cause: Our internal metadata database infrastructure in the affected region became unavailable, resulting in connectivity failures across multiple Snowflake services.\n\nA root cause analysis (RCA) will be conducted and a summary will be made available within 5 business days.",
"name": "INC20000237",
"timestamp": "Sep \u003cvar data-var='date'\u003e25\u003c/var\u003e, \u003cvar data-var='time'\u003e23:00\u003c/var\u003e - Sep \u003cvar data-var='date'\u003e26\u003c/var\u003e, \u003cvar data-var='time'\u003e00:20\u003c/var\u003e UTC"
},
{
"code": "8c1snlr8gskb",
"impact": "major",
"message": "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 affected deployments may have experienced performance degradation or issues logging into Snowflake, including delayed sign-ins, and SSO login loops.\n\nIncident start time: 22:22 UTC September 13, 2026\nIncident end time: 05:18 UTC September 14, 2026\n\nPreliminary root cause: An update intended to improve authentication handling caused a subset of single sign-on (SSO) sign-in attempts across multiple regions to fail or loop, preventing affected users from logging in to Snowflake.\n\nA root cause analysis (RCA) will be conducted and a summary will be made available within 5 business days.",
"name": "INC20000217",
"timestamp": "Sep \u003cvar data-var='date'\u003e14\u003c/var\u003e, \u003cvar data-var='time'\u003e04:48\u003c/var\u003e - \u003cvar data-var='time'\u003e06:09\u003c/var\u003e UTC"
},
{
"code": "x3f2pxm6l9zw",
"impact": "critical",
"message": "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 been unable to sign in to Snowsight, and may have receive an error message such as \"Something went wrong.\" This issue was intermittent and did not affect all users; affected users may also have experienced issues executing queries or managing data.\n\nIncident start time: 05:00 UTC September 11, 2026\nIncident end time: 11:15 UTC September 11, 2026\n\nPreliminary root cause: A configuration update to infrastructure components responsible for authorizing incoming network traffic caused the components to restrict this traffic.\n\nA root cause analysis (RCA) will be conducted and a summary will be made available within 5 business days.",
"name": "INC20000213",
"timestamp": "Sep \u003cvar data-var='date'\u003e11\u003c/var\u003e, \u003cvar data-var='time'\u003e07:18\u003c/var\u003e - \u003cvar data-var='time'\u003e13:19\u003c/var\u003e UTC"
},
{
"code": "wkhkwq8lfmb2",
"impact": "critical",
"message": "Current status: We've monitored the environment and confirmed that service has been 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 been unable to access or use multiple core Snowflake services and features. Affected users may have been unable to sign in, execute queries, or manage data.\n\nWorkaround: There were no available workarounds for this issue.\n\nIncident start time: 21:26 UTC September 09, 2026\nIncident end time: 21:55 UTC September 09, 2026\n\nPreliminary root cause: A subset of our metadata database infrastructure became unavailable, resulting in failures across multiple Snowflake services.\n\nA root cause analysis (RCA) will be conducted and a summary will be made available within 5 business days.",
"name": "INC20000211",
"timestamp": "Sep \u003cvar data-var='date'\u003e9\u003c/var\u003e, \u003cvar data-var='time'\u003e21:53\u003c/var\u003e - \u003cvar data-var='time'\u003e23:51\u003c/var\u003e UTC"
},
{
"code": "fl9tkpj8d7hk",
"impact": "critical",
"message": "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 been unable to access or use Snowflake services and features using Snowsight.\n\nWorkaround: There were no available workarounds for this issue.\n\nIncident start time: 07:00 UTC September 04, 2026\nIncident end time: 08:30 UTC September 04, 2026\n\nPreliminary root cause: A configuration update to infrastructure components responsible for authorizing incoming network traffic caused the components to restrict this traffic.\n\nA root cause analysis (RCA) will be conducted and a summary will be made available within 5 business days.",
"name": "INC20000199",
"timestamp": "Sep \u003cvar data-var='date'\u003e4\u003c/var\u003e, \u003cvar data-var='time'\u003e07:34\u003c/var\u003e - \u003cvar data-var='time'\u003e10:10\u003c/var\u003e UTC"
},
{
"code": "847dlygl25yb",
"impact": "major",
"message": "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 been unable to sign in to Snowflake Cowork, and may have seen a message indicating that sign-in was unsuccessful. All other Snowflake features were not impacted.\n\nWorkaround: There were no available workarounds for this issue.\n\nIncident start time: 00:00 UTC September 01, 2026\nIncident end time: 11:55 UTC September 01, 2026\n\nPreliminary root cause: An update to the underlying database objects responsible for managing CoWork sign-on mechanisms experienced a configuration error which resulted in the symptoms observed.\n\nA root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.",
"name": "INC20000190",
"timestamp": "Sep \u003cvar data-var='date'\u003e1\u003c/var\u003e, \u003cvar data-var='time'\u003e09:58\u003c/var\u003e - \u003cvar data-var='time'\u003e13:50\u003c/var\u003e UTC"
}
],
"name": "September",
"year": 2026
},
{
"incidents": [
{
"code": "09f44bx0y6lj",
"impact": "critical",
"message": "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.",
"name": "INC20000188",
"timestamp": "Aug \u003cvar data-var='date'\u003e31\u003c/var\u003e, \u003cvar data-var='time'\u003e17:20\u003c/var\u003e - \u003cvar data-var='time'\u003e19:44\u003c/var\u003e UTC"
},
{
"code": "9p16kxkml7v2",
"impact": "minor",
"message": "Current status: We've received an update from our third-party cloud provider that improvement for resource availability in this region is now projected by the end of October. In the meantime, we’re continuing our efforts to reduce virtual warehouse provisioning times, building on measures that have already shown improvement. In parallel, we’re preserving available compute resources and continuing to closely coordinate with our third-party cloud provider on resource availability updates in the specified region. Resource availability continues to vary with demand, and provisioning delays or failures may still occur. We’ll provide another update within 7 days.\n\nCustomer experience: Over the past few weeks, we've seen periods of fewer failures as we continue working to preserve available compute resources. However, resource availability at our third-party cloud provider remains constrained. Customers in the specified region may still encounter failures, timeouts, or delays when running Snowpark Container Services workloads, including starting or resuming Notebooks and provisioning or resuming compute pools.\n\nCreating additional workloads in new accounts adds to demand for these limited resources. Customers setting up Snowpark Container Services services or jobs, or Openflow runtimes, in those accounts may therefore encounter more frequent provisioning failures or be unable to complete setup.\n\nCustomers using second generation (Gen2) warehouses may also continue to experience delays or intermittent failures when starting or resuming their warehouses, which can extend query run times or delay completion of data pipelines.\n\nETA: Our third-party cloud platform provider remains committed to making additional compute resources available, which are now projected to be ready by late-October. We'll provide an updated ETA if that timeline changes.\n\nWorkaround: Customers running Notebooks on virtual warehouses can delay migrating to Snowpark Container Services until this issue is resolved.\n\nCustomers experiencing virtual warehouse resume delays can migrate affected warehouses to first generation (Gen1) using ALTER WAREHOUSE SET GENERATION = '1';. Gen1 warehouses are not affected by this capacity constraint. This is a short-term mitigation; Gen1 capacity is limited and performance characteristics may differ.\n\nThere are currently no general workarounds available for Snowpark Container Services compute pool impact. Customers with specific compute pool failures should contact Snowflake Support for case-by-case assistance.\n\nIncident start time: 08:41 UTC August 09, 2026\n\nPreliminary root cause: A third-party cloud platform experienced constrained compute capacity, causing limited availability of compute resources for Snowpark Container Services and delays or failures when provisioning or resuming virtual warehouses in the specified region.",
"name": "INC20000150",
"timestamp": "Aug \u003cvar data-var='date'\u003e28\u003c/var\u003e, \u003cvar data-var='time'\u003e00:07\u003c/var\u003e UTC"
},
{
"code": "7wg7mlfgzdyr",
"impact": "major",
"message": "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 connectivity issues when attempting to connect to Snowflake via private connectivity solutions, such as PrivateLink. Affected users may have encountered connection errors or timeouts.\n\nIncident start time: 18:21 UTC August 27, 2026\nIncident end time: 19:34 UTC August 27, 2026\n\nPreliminary root cause: A recent change intended to improve load balancer infrastructure health checks inadvertently introduced a configuration issue, which affected how private connectivity traffic was processed and resulted in connection failures. Once identified, we cycled the unhealthy infrastructure, restoring 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.",
"name": "INC20000182",
"timestamp": "Aug \u003cvar data-var='date'\u003e27\u003c/var\u003e, \u003cvar data-var='time'\u003e19:05\u003c/var\u003e - \u003cvar data-var='time'\u003e20:26\u003c/var\u003e UTC"
},
{
"code": "3s0hdzy30jww",
"impact": "critical",
"message": "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 have been unable to access Snowflake services due to infrastructure connectivity issues. All other Snowflake features in other regions were not impacted.\n\nWorkaround: There were no available workarounds for this issue.\n\nIncident start time: 03:09 UTC August 25, 2026\nIncident end time: 04:05 UTC August 25, 2026\n\nPreliminary root cause: A third-party cloud platform experienced a virtual machine service issue, which caused infrastructure connectivity problems affecting Snowflake services in the region.\n\nA root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.",
"name": "INC20000175",
"timestamp": "Aug \u003cvar data-var='date'\u003e25\u003c/var\u003e, \u003cvar data-var='time'\u003e03:53\u003c/var\u003e - \u003cvar data-var='time'\u003e04:35\u003c/var\u003e UTC"
},
{
"code": "mhntf8gmn065",
"impact": "major",
"message": "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 have been unable to remain logged in to Snowsight, experiencing immediate logout after successful authentication.\n\nIncident start time: 14:47 UTC August 24, 2026\nIncident end time: 17:21 UTC August 24, 2026\n\nPreliminary root cause: A system configuration change caused an outdated application version to be deployed, resulting in authentication session failures. Once identified, the configuration was corrected to restore the proper application version.\n\nA root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.",
"name": "INC20000173",
"timestamp": "Aug \u003cvar data-var='date'\u003e24\u003c/var\u003e, \u003cvar data-var='time'\u003e16:22\u003c/var\u003e - \u003cvar data-var='time'\u003e18:03\u003c/var\u003e UTC"
},
{
"code": "n54hrszdq7h7",
"impact": "major",
"message": "Current status: The third-party cloud platform confirmed that the mitigation was complete, and its automated recovery system appears to have initiated. We independently monitored the environment and verified 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 been unable to connect to Snowflake via private connectivity solutions, such as PrivateLink. Other connection methods were unaffected.\n\nIncident start time: 13:25 UTC August 20, 2026\nIncident end time: 14:10 UTC August 20, 2026\n\nPreliminary root cause: A third-party cloud platform experienced a virtual networking infrastructure issue, preventing customers from connecting to Snowflake via private connectivity solutions, such as PrivateLink. While we suspect that this issue may be a recurrence of a third-party cloud platform virtual networking problem, we remain closely engaged with our third-party cloud platform as they perform their own investigation into the underlying root cause of the issue.\n\nA root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 10 business days.",
"name": "INC20000168",
"timestamp": "Aug \u003cvar data-var='date'\u003e20\u003c/var\u003e, \u003cvar data-var='time'\u003e13:47\u003c/var\u003e - \u003cvar data-var='time'\u003e15:43\u003c/var\u003e UTC"
},
{
"code": "yk5sqhcjp266",
"impact": "major",
"message": "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.",
"name": "INC20000163",
"timestamp": "Aug \u003cvar data-var='date'\u003e18\u003c/var\u003e, \u003cvar data-var='time'\u003e12:58\u003c/var\u003e - \u003cvar data-var='time'\u003e14:51\u003c/var\u003e UTC"
},
{
"code": "v8nyb5fhd95v",
"impact": "critical",
"message": "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.",
"name": "INC20000158",
"timestamp": "Aug \u003cvar data-var='date'\u003e14\u003c/var\u003e, \u003cvar data-var='time'\u003e17:29\u003c/var\u003e - \u003cvar data-var='time'\u003e19:35\u003c/var\u003e UTC"
},
{
"code": "ylfhrtlppdlt",
"impact": "critical",
"message": "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 experienced intermittent authentication failures and \"service unavailable\" errors between approximately 14:20 and 14:45 UTC.\n\nIncident start time: 14:20 UTC August 14, 2026\nIncident end time: 14:45 UTC August 14, 2026\n\nPreliminary root cause: A service infrastructure layer supporting authentication and session initiation for Snowsight entered an unhealthy state, causing login failures and service disruptions.\n\nA root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.",
"name": "INC20000157",
"timestamp": "Aug \u003cvar data-var='date'\u003e14\u003c/var\u003e, \u003cvar data-var='time'\u003e15:19\u003c/var\u003e - \u003cvar data-var='time'\u003e16:28\u003c/var\u003e UTC"
},
{
"code": "j7drswl3ssy7",
"impact": "minor",
"message": "Current status: We've confirmed that this issue has been resolved, and we have monitored the environment to confirm that the affected functionality is now working as expected. 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 intermittently unable to use CoCo services through Snowsight. Users may have seen an \"Internal Server Error\" when interacting with the service. All other Snowflake features were not impacted.\n\nIncident start time: 11:40 UTC August 05, 2026\nIncident end time: 15:00 UTC August 05, 2026\n\nPreliminary root cause: An underlying system component supporting Cortex services experienced failures due to connectivity issues with the file system, resulting in intermittent customer impact.\n\nA root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.",
"name": "INC20000139",
"timestamp": "Aug \u003cvar data-var='date'\u003e5\u003c/var\u003e, \u003cvar data-var='time'\u003e14:41\u003c/var\u003e - \u003cvar data-var='time'\u003e15:49\u003c/var\u003e UTC"
},
{
"code": "xfv4kdj30rcb",
"impact": "critical",
"message": "Current status: We've confirmed that this issue has been resolved, and we have monitored the environment to confirm that the affected functionality is now working as expected. 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 start, resume, or manage virtual warehouses. The impact occurred during the periods of 13:33 to 15:20 UTC, and 16:05 to 16:36 UTC on August 03, 2026. Virtual warehouses may have appeared as stuck in the associated state. Existing warehouses that were already running may have been unaffected. Customers may also have seen queued or delayed queries for workloads running on affected warehouses. Additionally, some serverless tasks may have experienced residual queuing or failures until the backlog of requests which accumulated during the impact windows was processed.\n\nIncident start time: 13:33 UTC August 03, 2026\nIncident end time: 16:36 UTC August 03, 2026\n\nPreliminary root cause: A Cloud Services component responsible for virtual warehouse management became unhealthy. This caused failures in the internal workflows used to allocate and manage compute resources for warehouse start and resume operations, resulting in customer impact.\n\nA root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.",
"name": "INC20000129",
"timestamp": "Aug \u003cvar data-var='date'\u003e3\u003c/var\u003e, \u003cvar data-var='time'\u003e14:11\u003c/var\u003e - \u003cvar data-var='time'\u003e20:58\u003c/var\u003e UTC"
},
{
"code": "ns7hfk8pbqfy",
"impact": "minor",
"message": "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 have experienced intermittent Snowsight login failures, elevated page load times, or session timeouts when accessing the web interface. Affected users may encounter errors such as \"Failed to fetch\" and \"Execution failed\", or HTTP 503 Service Unavailable messages. The issue was intermittent and did not affect all users or login attempts simultaneously; retrying failed requests generally results in successful connection. \n\nAlthough initial indications were that this issue was affecting multiple deployments, subsequent investigation demonstrated the issue was restricted to the AWS - Asia Pacific (Tokyo) region.\n\nIncident start time: 00:53 UTC August 03, 2026\nIncident end time: 06:15 UTC August 03, 2026\n\nPreliminary root cause: An update intended to improve the efficiency of connection handling at the network routing layer was identified and rolled back 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.",
"name": "INC20000128",
"timestamp": "Aug \u003cvar data-var='date'\u003e3\u003c/var\u003e, \u003cvar data-var='time'\u003e05:53\u003c/var\u003e - \u003cvar data-var='time'\u003e08:15\u003c/var\u003e UTC"
}
],
"name": "August",
"year": 2026
},
{
"incidents": [
{
"code": "0js22rxjm66q",
"impact": "critical",
"message": "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.",
"name": "INC20000115",
"timestamp": "Jul \u003cvar data-var='date'\u003e30\u003c/var\u003e, \u003cvar data-var='time'\u003e03:00\u003c/var\u003e - \u003cvar data-var='time'\u003e04:56\u003c/var\u003e UTC"
},
{
"code": "0yt2v05n42gz",
"impact": "minor",
"message": "Current status: We've confirmed that this issue has been resolved, and we have monitored the environment to confirm that the affected functionality is now working as expected. 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 resume warehouses or may have experienced significant delays with serverless tasks and other workloads that required compute resources. Queries may have queued for extended periods instead of executing immediately, with some customers experiencing delays of several hours.\n\nWorkaround: There were no available workarounds for this issue.\n\nIncident start time: 07:45 UTC July 25, 2026\nIncident end time: 15:05 UTC July 25, 2026\n\nPreliminary root cause: Unexpected demand from a large-scale workload exceeded available network capacity in the affected region, causing resource exhaustion that prevented new compute resources from being provisioned.\n\nA root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.",
"name": "INC20000106",
"timestamp": "Jul \u003cvar data-var='date'\u003e25\u003c/var\u003e, \u003cvar data-var='time'\u003e09:05\u003c/var\u003e - \u003cvar data-var='time'\u003e16:01\u003c/var\u003e UTC"
},
{
"code": "46l87jjm2m5f",
"impact": "minor",
"message": "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 delays or intermittent failures when resuming or managing virtual warehouses. Existing warehouses that were already running may have been unaffected.\n\nIncident start time: 16:35 UTC July 11, 2026\nIncident end time: 18:10 UTC July 11, 2026\n\nPreliminary root cause: Resource exhaustion in the binary download service caused delays when virtual warehouses attempted to download required software components during startup.\n\nA root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.",
"name": "INC20000085",
"timestamp": "Jul \u003cvar data-var='date'\u003e11\u003c/var\u003e, \u003cvar data-var='time'\u003e17:41\u003c/var\u003e - \u003cvar data-var='time'\u003e19:36\u003c/var\u003e UTC"
},
{
"code": "kw59fjhlv3jq",
"impact": "major",
"message": "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 regions may have been unable to connect to Snowflake via private connectivity solutions, such as PrivateLink. Users may have encountered connection errors or timeouts. Additionally, all customers using public connectivity may have been unable to access Snowsight between July 10, 2026, at 13:26 and 13:40 UTC.\n\nIncident start time: 13:26 UTC July 10, 2026\nIncident end time: 14:33 UTC July 10, 2026\n\nPreliminary root cause: Our preliminary root cause analysis identified that the load balancing infrastructure responsible for managing connections to Snowsight temporarily entered a degraded state, preventing requests from being processed successfully. We've engaged the associated Cloud Service Provider to investigate and troubleshoot this issue further.\n\nA root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.",
"name": "INC20000082",
"timestamp": "Jul \u003cvar data-var='date'\u003e10\u003c/var\u003e, \u003cvar data-var='time'\u003e14:30\u003c/var\u003e - \u003cvar data-var='time'\u003e16:28\u003c/var\u003e UTC"
}
],
"name": "July",
"year": 2026
}
],
"start_time": "2026-07-01T00:00:00Z",
"time_zone": "UTC"
},
{
"end_time": "2026-06-30T23:59:59Z",
"months": [
{
"incidents": [
{
"code": "rqkrpr2hf7f7",
"impact": "critical",
"message": "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 have been unable to access Snowsight or may have experienced being logged out unexpectedly. All other Snowflake features were not impacted.\n\nWorkaround: While we were focused on remediation, customers who were logged out needed to log back in to Snowsight.\n\nIncident start time: 21:47 UTC June 30, 2026\nIncident end time: 22:03 UTC June 30, 2026\n\nPreliminary root cause: A routine system configuration change caused authentication issues with Snowsight. Once identified, the configuration was reverted.\n\nA root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.",
"name": "INC20000063",
"timestamp": "Jun \u003cvar data-var='date'\u003e30\u003c/var\u003e, \u003cvar data-var='time'\u003e22:34\u003c/var\u003e - \u003cvar data-var='time'\u003e23:34\u003c/var\u003e UTC"
},
{
"code": "w9qjc26y18rn",
"impact": "critical",
"message": "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 have been unable to access or use Snowflake services and features using Snowsight. A subset of affected users in the region may also have been unable to execute queries, manage data, or may have experienced increased latency or performance issues with database operations.\n\nIncident start time: 15:10 UTC June 24, 2026\nIncident end time: 15:50 UTC June 24, 2026\n\nPreliminary root cause: A configuration issue caused an unexpected increase in load on our metadata database layer, resulting in cascading impact to dependent services like Snowsight and database operations.\n\nA root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.",
"name": "INC20000052",
"timestamp": "Jun \u003cvar data-var='date'\u003e24\u003c/var\u003e, \u003cvar data-var='time'\u003e15:38\u003c/var\u003e - \u003cvar data-var='time'\u003e17:22\u003c/var\u003e UTC"
},
{
"code": "j3xz9wrt22vp",
"impact": "major",
"message": "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 have been intermittently unable to access or launch Streamlit apps, or may have experienced issues with other services and features that rely on Snowpark Container Services, such as Notebooks. Users may have experienced connection timeouts and received a \"Connection error\" when interacting with affected services.\n\nWorkaround: There were no available workarounds for this issue.\n\nIncident start time: 15:20 UTC June 23, 2026\nIncident end time: 05:10 UTC June 24, 2026\n\nPreliminary root cause: A subset of infrastructure responsible for processing service requests experienced degraded performance, which prevented requests from completing and caused connectivity failures for services that rely on Snowpark Container Services.\n\nA root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.",
"name": "INC20000047",
"timestamp": "Jun \u003cvar data-var='date'\u003e23\u003c/var\u003e, \u003cvar data-var='time'\u003e17:01\u003c/var\u003e - Jun \u003cvar data-var='date'\u003e24\u003c/var\u003e, \u003cvar data-var='time'\u003e07:30\u003c/var\u003e UTC"
},
{
"code": "0nxtj28g9ycc",
"impact": "major",
"message": "Current status: We've monitored the environment to confirm 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 region may have been unable to access Snowpark Container Services, and may have intermittently been unable to sign in to Snowsight. Affected users may have seen HTTP 500 errors.\n\nWorkaround: There were no available workarounds for this issue.\n\nIncident start time: 22:38 UTC June 22, 2026\nIncident end time: 01:28 UTC June 23, 2026\n\nPreliminary root cause: A recent configuration change affected DNS resolution in the region, which caused connectivity failures for Snowpark Container Services and Snowsight.\n\nA root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.",
"name": "INC20000046",
"timestamp": "Jun \u003cvar data-var='date'\u003e23\u003c/var\u003e, \u003cvar data-var='time'\u003e01:05\u003c/var\u003e - \u003cvar data-var='time'\u003e02:35\u003c/var\u003e UTC"
},
{
"code": "zn8xxp2qzpr1",
"impact": "critical",
"message": "\u003cb\u003eCurrent status:\u003c/b\u003e We've monitored the environment to confirm our actions have 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\n\u003cb\u003eCustomer experience:\u003c/b\u003e Customers hosted in the specified regions may have been unable to access or use multiple core Snowflake services and features, and may have experienced delays or failures with replication or when using Snowpipe to ingest files. Affected users may have been unable to execute queries and tasks or manage data, and may have seen a \"Processing aborted due to error\" SQL execution internal error.\n\n\u003cb\u003eIncident start time:\u003c/b\u003e 20:12 UTC June 22, 2026\n\u003cb\u003eIncident end time:\u003c/b\u003e 21:45 UTC June 22, 2026\n\n\u003cb\u003ePreliminary root cause:\u003c/b\u003e Elevated load in a critical internal coordination service affected request processing for a subset of workloads. The underlying cause of the issue remains under investigation. \n\nA root cause analysis (RCA) document will be published within five business days.",
"name": "AWS - US West (Oregon): INC0159680",
"timestamp": "Jun \u003cvar data-var='date'\u003e22\u003c/var\u003e, \u003cvar data-var='time'\u003e20:35\u003c/var\u003e - Jun \u003cvar data-var='date'\u003e23\u003c/var\u003e, \u003cvar data-var='time'\u003e00:26\u003c/var\u003e UTC"
},
{
"code": "x9085gh79r3x",
"impact": "critical",
"message": "Current status: We've validated the fix for this issue with our third-party provider 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 have been unable to access or use Snowflake services and features using Snowsight. The most significant periods of impact for most customers were between 14:05-14:35 and 16:27-16:46 UTC, during which customers could not authenticate or access Snowsight. After initial recovery actions, customers were able to access Snowsight but may have been unable to perform operations within the UI or experienced intermittent periods of significant performance issues. Customers may have seen \"something went wrong\" or \"no healthy upstream\" error messages.\n\nIncident start time: 14:15 UTC June 15, 2026\nIncident end time: 21:45 UTC June 15, 2026\n\nPreliminary root cause: Backend infrastructure that supports authentication to the Snowsight service experienced a degradation due to a third-party cloud platform infrastructure issue. This triggered a cascade of connectivity issues in backend components supporting the Snowsight platform, resulting in service disruptions and intermittent access problems.\n\nA root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 10 business days.",
"name": "INC20000034",
"timestamp": "Jun \u003cvar data-var='date'\u003e15\u003c/var\u003e, \u003cvar data-var='time'\u003e14:30\u003c/var\u003e - Jun \u003cvar data-var='date'\u003e16\u003c/var\u003e, \u003cvar data-var='time'\u003e21:15\u003c/var\u003e UTC"
},
{
"code": "dt63jcq37152",
"impact": "major",
"message": "\u003cb\u003eCurrent status:\u003c/b\u003e 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\n\u003cb\u003eCustomer experience:\u003c/b\u003e Customers hosted in the specified regions may have been unable to use Git repository functionality in Workspaces, including pulling changes from a connected Git repository and performing related Git operations in a Git-synced workspace. Affected customers may have seen an error message: \"Workspace feature disabled: Internal only system function.\"\n\n\u003cb\u003eIncident start time:\u003c/b\u003e 00:03 UTC June 16, 2026\n\u003cb\u003eIncident end time:\u003c/b\u003e 17:29 UTC June 16, 2026\n\n\u003cb\u003ePreliminary root cause:\u003c/b\u003e A recent Snowsight Workspaces software update changed how certain Workspace Git operations were routed and classified. Due to a code issue, some customer Git repository actions were tagged with an incorrect internal classification, causing those operations to fail.\n\nA root cause analysis (RCA) document will be published within five business days.",
"name": "INC0159144",
"timestamp": "Jun \u003cvar data-var='date'\u003e16\u003c/var\u003e, \u003cvar data-var='time'\u003e10:29\u003c/var\u003e - \u003cvar data-var='time'\u003e20:20\u003c/var\u003e UTC"
},
{
"code": "g4d0vxhf0tns",
"impact": "minor",
"message": "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 seen that stored procedures that use Snowpark external access integrations failed with the following SQL execution internal error: 300010:4004234085.\n\nIncident start time: 15:10 UTC June 12, 2026\nIncident end time: 19:15 UTC June 12, 2026\n\nPreliminary root cause: A misconfiguration introduced by a recent network configuration change affecting outbound connectivity for stored procedures that use Snowpark external access integrations resulted in impact.\n\nA root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.",
"name": "INC20000033",
"timestamp": "Jun \u003cvar data-var='date'\u003e12\u003c/var\u003e, \u003cvar data-var='time'\u003e18:21\u003c/var\u003e - \u003cvar data-var='time'\u003e20:57\u003c/var\u003e UTC"
},
{
"code": "980k6ghp4qwb",
"impact": "critical",
"message": "Current status: We identified and reverted a misconfigured change, 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 have been unable to access or use multiple core Snowflake services and features. For example, affected users may have been unable to access Snowsight, Snowflake Openflow, Snowpark Container Services, or Cortex AI services (such as Cortex LLM functions, Agents, Analyst, and Search).\n\nWorkaround: There were no available workarounds for this issue.\n\nIncident start time: 23:23 UTC June 10, 2026\nIncident end time: 23:58 UTC June 10, 2026\n\nPreliminary root cause: A misconfiguration during a system maintenance operation caused connectivity failures in the affected region.\n\nA root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.",
"name": "INC20000032",
"timestamp": "Jun \u003cvar data-var='date'\u003e11\u003c/var\u003e, \u003cvar data-var='time'\u003e00:30\u003c/var\u003e - \u003cvar data-var='time'\u003e00:30\u003c/var\u003e UTC"
},
{
"code": "655fr2b9cl57",
"impact": "critical",
"message": "Current status: We've monitored the environment and confirmed 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 been unable to access or use Snowflake services and features using Snowsight. Customers may have experienced page not found errors or general login failures.\n\nIncident start time: 14:58 UTC June 08, 2026\nIncident end time: 15:20 UTC June 08, 2026\n\nPreliminary root cause: An internal system degradation occurred within backend database infrastructure that supports Snowsight in the affected region, causing Snowsight request failures. The issue was detected by system health monitoring, and automated recovery systems performed scaling and targeted infrastructure restart operations that helped to restore service. We’re continuing to investigate to confirm the underlying root cause details and the contributing factors.\n\nA root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.",
"name": "INC20000030",
"timestamp": "Jun \u003cvar data-var='date'\u003e8\u003c/var\u003e, \u003cvar data-var='time'\u003e15:23\u003c/var\u003e - \u003cvar data-var='time'\u003e16:40\u003c/var\u003e UTC"
}
],
"name": "June",
"year": 2026
},
{
"incidents": [
{
"code": "4w8gm09dsr8p",
"impact": "major",
"message": "\u003cb\u003eCurrent status:\u003c/b\u003e Our third-party cloud platform has confirmed that the impact to their infrastructure has been mitigated, and we've observed that the impact to Snowflake customers has been resolved. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight.\n\n\u003cb\u003eCustomer experience:\u003c/b\u003e Customers hosted in the specified regions may have been unable to start, resume, or manage virtual warehouses. Virtual warehouses may have appeared to be stuck in the associated state. The majority of the impact occurred during the period of 05:15 UTC to 07:24 UTC on May 29, 2026. \n\n\u003cb\u003eIncident start time:\u003c/b\u003e 04:24 UTC May 29, 2026\n\u003cb\u003eIncident end time:\u003c/b\u003e 07:24 UTC May 29, 2026\n\n\u003cb\u003ePreliminary root cause:\u003c/b\u003e A third-party cloud platform experienced a power outage in its data center, which affected the underlying infrastructure and caused increased latency and intermittent connectivity for some resources on which Snowflake depends. \n\nA root cause analysis (RCA) document will be published within ten business days.",
"name": "Azure - West US 2 (Washington): INC0157956",
"timestamp": "May \u003cvar data-var='date'\u003e29\u003c/var\u003e, \u003cvar data-var='time'\u003e06:47\u003c/var\u003e - \u003cvar data-var='time'\u003e22:28\u003c/var\u003e UTC"
},
{
"code": "rby2mg3mxmvp",
"impact": "critical",
"message": "To ensure the best possible service for our customers amid the persistent issues in the AWS Middle East (UAE) region and following the cloud service provider’s advice to transition workloads to other regions, we have decided to remove this region from our available listings until further notice.",
"name": "AWS - Middle East (UAE): INC0152681",
"timestamp": "Mar \u003cvar data-var='date'\u003e1\u003c/var\u003e, \u003cvar data-var='time'\u003e13:33\u003c/var\u003e - May \u003cvar data-var='date'\u003e15\u003c/var\u003e, \u003cvar data-var='time'\u003e15:10\u003c/var\u003e UTC"
},
{
"code": "mkbgc4vgdhdb",
"impact": "minor",
"message": "\u003cb\u003eCurrent status:\u003c/b\u003e We've monitored the environment and confirmed the rollback 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\n\u003cb\u003eCustomer experience:\u003c/b\u003e Customers hosted in the specified regions may have experienced Cortex Code in Snowsight stopping mid-response after completing only one step of a request. The response may have stopped without an error message or may have repeated without progressing.\n\n\u003cb\u003eIncident start time:\u003c/b\u003e 22:50 UTC May 14, 2026\n\u003cb\u003eIncident end time:\u003c/b\u003e 04:05 UTC May 15, 2026\n\n\u003cb\u003ePreliminary root cause:\u003c/b\u003e A recent update to Cortex Code introduced a code issue that caused Cortex Code in Snowsight to incorrectly halt responses, preventing requests from completing.\n\nA root cause analysis (RCA) document will be published within five business days.",
"name": "INC0157230",
"timestamp": "May \u003cvar data-var='date'\u003e15\u003c/var\u003e, \u003cvar data-var='time'\u003e04:01\u003c/var\u003e - \u003cvar data-var='time'\u003e05:25\u003c/var\u003e UTC"
},
{
"code": "mz5w4kshds0w",
"impact": "none",
"message": "\u003cb\u003eCurrent status:\u003c/b\u003e After investigating, we've determined this to be a false positive. There were no customer replication refresh operations impacted. We've confirmed replication services are functioning normally. If you experience issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight.",
"name": "INC0157155",
"timestamp": "May \u003cvar data-var='date'\u003e13\u003c/var\u003e, \u003cvar data-var='time'\u003e23:08\u003c/var\u003e - May \u003cvar data-var='date'\u003e14\u003c/var\u003e, \u003cvar data-var='time'\u003e00:19\u003c/var\u003e UTC"
},
{
"code": "z2h7mnkrxdxh",
"impact": "minor",
"message": "\u003cb\u003eCurrent status:\u003c/b\u003e 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\n\u003cb\u003eCustomer experience:\u003c/b\u003e Customers hosted in the specified region may have observed stale or delayed data in account usage views and organization usage views. \n\n\u003cb\u003eIncident start time:\u003c/b\u003e 12:03 UTC May 04, 2026\n\u003cb\u003eIncident end time:\u003c/b\u003e 08:54 UTC May 05, 2026\n\n\u003cb\u003ePreliminary root cause:\u003c/b\u003e We identified an issue affecting a small number of internal metering files in this region. When Snowflake attempted to read these files as part of metering and account usage processing, the reads failed, blocking downstream processing.\n\nA root cause analysis (RCA) document will be published within five business days.",
"name": "Azure - West US 2 (Washington): INC0156645",
"timestamp": "May \u003cvar data-var='date'\u003e5\u003c/var\u003e, \u003cvar data-var='time'\u003e04:12\u003c/var\u003e - \u003cvar data-var='time'\u003e12:30\u003c/var\u003e UTC"
}
],
"name": "May",
"year": 2026
},
{
"incidents": [
{
"code": "3g6k24d9ws1k",
"impact": "critical",
"message": "\u003cb\u003eCurrent status:\u003c/b\u003e We identified a subset of infrastructure that was unhealthy. We restarted that infrastructure and monitored the environment to confirm that the service has been restored. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight.\n\n\u003cb\u003eCustomer experience:\u003c/b\u003e Customers hosted in the specified regions may experience errors or connectivity issues when using Snowpark Container Services. Openflow users may be unable to access their runtimes, and Openflow Connectors may fail to pull data from sources or push data to Snowflake.\n\n\u003cb\u003eIncident start time:\u003c/b\u003e 02:05 UTC April 29, 2026\n\u003cb\u003eIncident end time:\u003c/b\u003e 04:11 UTC April 29, 2026\n\n\u003cb\u003ePreliminary root cause:\u003c/b\u003e A subset of infrastructure that processes DNS requests in the affected region became unhealthy, which caused service connectivity failures for Snowpark Container Services and Openflow.\n\nA root cause analysis (RCA) document will be published within five business days.",
"name": "Azure - UK South (London): INC0156355",
"timestamp": "Apr \u003cvar data-var='date'\u003e29\u003c/var\u003e, \u003cvar data-var='time'\u003e03:23\u003c/var\u003e - \u003cvar data-var='time'\u003e04:44\u003c/var\u003e UTC"
},
{
"code": "0lj68wp0lphb",
"impact": "major",
"message": "\u003cb\u003eCurrent status:\u003c/b\u003e 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\n\u003cb\u003eCustomer experience:\u003c/b\u003e Customers hosted in the specified regions may have been unable to access or use Snowflake services and features using Snowsight.\n\n\u003cb\u003eIncident start time:\u003c/b\u003e 12:25 UTC April 16, 2026\n\u003cb\u003eIncident end time:\u003c/b\u003e 13:45 UTC April 16, 2026\n\n\u003cb\u003ePreliminary root cause:\u003c/b\u003e Some application instances entered a degraded state and were unable to handle downstream connections. Snowflake mitigated the issue by restarting the affected instances.\n\nA root cause analysis (RCA) document will be published within five business days.",
"name": "GCP - US Central 1 (Iowa): INC0155608",
"timestamp": "Apr \u003cvar data-var='date'\u003e16\u003c/var\u003e, \u003cvar data-var='time'\u003e14:08\u003c/var\u003e - \u003cvar data-var='time'\u003e15:08\u003c/var\u003e UTC"
},
{
"code": "g47n1w0d9v90",
"impact": "critical",
"message": "\u003cb\u003eCurrent status:\u003c/b\u003e We've rerouted Snowflake traffic to healthy infrastructure to address this issue, and we've monitored the environment to confirm that service has been restored. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight.\n\n\u003cb\u003eCustomer experience:\u003c/b\u003e Customers hosted in the specified regions may have been unable to access or use Snowflake services and features using Snowsight. A subset of affected customers were also unable to use other core Snowflake services and features, such as executing queries or tasks.\n\n\u003cb\u003eIncident start time:\u003c/b\u003e 17:47 UTC April 07, 2026\n\u003cb\u003eIncident end time:\u003c/b\u003e 19:45 UTC April 07, 2026\n\n\u003cb\u003ePreliminary root cause:\u003c/b\u003e A subset of our metadata database infrastructure in this region became degraded, which impacted the overall availability of the service for affected customers. Concurrently, Snowsight infrastructure experienced a period of increased latency and failures, which correlated specifically to Snowsight availability issues in the region.\n\nA root cause analysis (RCA) document will be published within five business days.",
"name": "Azure - East US 2 (Virginia): INC0155020",
"timestamp": "Apr \u003cvar data-var='date'\u003e7\u003c/var\u003e, \u003cvar data-var='time'\u003e18:26\u003c/var\u003e - \u003cvar data-var='time'\u003e20:56\u003c/var\u003e UTC"
}
],
"name": "April",
"year": 2026
}
],
"start_time": "2026-04-01T00:00:00Z",
"time_zone": "UTC"
},
{
"end_time": "2026-03-31T23:59:59Z",
"months": [
{
"incidents": [
{
"code": "xj5gygqqc5w8",
"impact": "major",
"message": "\u003cb\u003eCurrent status:\u003c/b\u003e We've confirmed that the infrastructure issue delaying deployment of the fix to the GCP - US East 4 (N. Virginia) region was resolved, and we have monitored the environment to confirm that the affected functionality is now working as expected. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight.\n\n\u003cb\u003eCustomer experience:\u003c/b\u003e Customers may have been unable to see or manage their Native Apps within the \"Apps\" page of the Snowsight UI. App execution and all other Snowflake features were not impacted. SQL commands (e.g., SHOW APPLICATIONS) or searching for apps using the Catalog \u0026gt; Database Explorer page could still be used to view and manage Native Apps.\n\n\u003cb\u003eIncident start time:\u003c/b\u003e 00:00 UTC March 27, 2026\n\u003cb\u003eIncident end time:\u003c/b\u003e 05:55 UTC March 29, 2026\n\n\u003cb\u003ePreliminary root cause:\u003c/b\u003e A recent Snowsight release introduced a code issue that caused an error to occur when attempting to load application metadata within the Apps page. This prevented the page from rendering the list of installed applications as expected.\n\nA root cause analysis (RCA) document will be published within five business days.",
"name": "INC0154408",
"timestamp": "Mar \u003cvar data-var='date'\u003e27\u003c/var\u003e, \u003cvar data-var='time'\u003e18:34\u003c/var\u003e - Mar \u003cvar data-var='date'\u003e30\u003c/var\u003e, \u003cvar data-var='time'\u003e21:38\u003c/var\u003e UTC"
},
{
"code": "p3x136d3mcsp",
"impact": "critical",
"message": "\u003cb\u003eCurrent status:\u003c/b\u003e 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\n\u003cb\u003eCustomer experience:\u003c/b\u003e Customers hosted in the specified regions may have been unable to access or use multiple core Snowflake services and features. Affected users may have been unable to sign in, execute queries, or manage data. Users would have encountered HTTP 404 or other similar errors.\n\n\u003cb\u003eIncident start time:\u003c/b\u003e 05:27 UTC March 21, 2026\n\u003cb\u003eIncident end time:\u003c/b\u003e 06:18 UTC March 21, 2026\n\n\u003cb\u003ePreliminary root cause:\u003c/b\u003e The investigation determined that infrastructure responsible for high-level traffic routing and name resolution became degraded, which caused customers to encounter HTTP 404 errors when attempting to access or use certain Snowflake services.\n\nA root cause analysis (RCA) document will be published within five business days.",
"name": "AWS - US West (Oregon): INC0154019",
"timestamp": "Mar \u003cvar data-var='date'\u003e21\u003c/var\u003e, \u003cvar data-var='time'\u003e06:02\u003c/var\u003e - \u003cvar data-var='time'\u003e07:12\u003c/var\u003e UTC"
},
{
"code": "cy1j8q1htyy9",
"impact": "minor",
"message": "\u003cb\u003eCurrent status:\u003c/b\u003e 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\n\u003cb\u003eCustomer experience:\u003c/b\u003e Customers hosted in the specified regions may have been unable to create or alter Snowflake alerts.\n\n\u003cb\u003eIncident start time:\u003c/b\u003e 14:53 UTC March 14, 2026\n\u003cb\u003eIncident end time:\u003c/b\u003e 04:39 UTC March 17, 2026\n\n\u003cb\u003ePreliminary root cause:\u003c/b\u003e A recent improvement to Snowflake alerts creation and alteration contained a code issue.\n\nA root cause analysis (RCA) document will be published within five business days.",
"name": "INC0153706",
"timestamp": "Mar \u003cvar data-var='date'\u003e16\u003c/var\u003e, \u003cvar data-var='time'\u003e22:46\u003c/var\u003e - Mar \u003cvar data-var='date'\u003e17\u003c/var\u003e, \u003cvar data-var='time'\u003e05:49\u003c/var\u003e UTC"
},
{
"code": "kpkc19wpf1m0",
"impact": "major",
"message": "\u003cb\u003eCurrent status:\u003c/b\u003e We've confirmed that the rollback of the impacting Snowflake Intelligence update has completed, and we'll continue to monitor the environment until we're confident all services are functioning properly.\n\n\u003cb\u003eCustomer experience:\u003c/b\u003e Customers hosted in the specified regions may have been unable to use Snowflake Intelligence services and features. Additionally, users may have experienced issues with expired sessions attempting to access Snowflake Intelligence. Existing sessions should have been unaffected. \n\n\u003cb\u003eWorkaround:\u003c/b\u003e While we were focused on remediation, users may have been able to work around the issue by accessing the service directly via the non-account-specific URL, AI.Snowflake.com, in a private browser tab.\n\n\u003cb\u003eIncident start time:\u003c/b\u003e 16:30 UTC March 12, 2026\n\u003cb\u003eIncident end time:\u003c/b\u003e 20:39 UTC March 12, 2026\n\n\u003cb\u003ePreliminary root cause:\u003c/b\u003e An update intended to optimize Snowflake Intelligence introduced a code issue that caused problems with expired sessions attempting to access Snowflake Intelligence.",
"name": "INC0153465",
"timestamp": "Mar \u003cvar data-var='date'\u003e12\u003c/var\u003e, \u003cvar data-var='time'\u003e19:42\u003c/var\u003e - \u003cvar data-var='time'\u003e23:13\u003c/var\u003e UTC"
},
{
"code": "6ghqh8nfw4wc",
"impact": "major",
"message": "\u003cb\u003eCurrent status:\u003c/b\u003e We've coordinated with our third-party cloud platform to confirm that the fix for this issue was successfully implemented, and we've monitored the environment to confirm that service has been fully restored. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight.\n\n\u003cb\u003eCustomer experience:\u003c/b\u003e Customers hosted in the specified regions may have been unable to access or use multiple core Snowflake services and features. Affected users may have been unable to sign in, execute queries, or manage data.\n\n\u003cb\u003eIncident start time:\u003c/b\u003e 19:30 UTC March 07, 2026\n\u003cb\u003eIncident end time:\u003c/b\u003e 21:10 UTC March 07, 2026\n\n\u003cb\u003ePreliminary root cause:\u003c/b\u003e A third-party cloud platform experienced an issue with part of their storage service, which temporarily prevented some Snowflake services and features from working for a subset of customers in this region.\n\nA root cause analysis (RCA) document will be published within ten business days.",
"name": "AWS - Europe (Zürich): INC0153183",
"timestamp": "Mar \u003cvar data-var='date'\u003e7\u003c/var\u003e, \u003cvar data-var='time'\u003e20:05\u003c/var\u003e - \u003cvar data-var='time'\u003e22:20\u003c/var\u003e UTC"
}
],
"name": "March",
"year": 2026
},
{
"incidents": [
{
"code": "8mj6n9xzhc96",
"impact": "minor",
"message": "\u003cb\u003eCurrent status:\u003c/b\u003e Our observations of service telemetry continue to indicate that our service has recovered following our mitigation. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight.\n\n\u003cb\u003eCustomer experience:\u003c/b\u003e Customers hosted in the specified regions may have experienced intermittent delays or failures when accessing or using Snowflake services and features. This may have included slower query execution, intermittent availability, or limited feature functionality.\n\n\u003cb\u003eIncident start time:\u003c/b\u003e 19:26 UTC February 23, 2026\n\u003cb\u003eIncident end time:\u003c/b\u003e 21:11 UTC February 23, 2026\n\n\u003cb\u003ePreliminary root cause:\u003c/b\u003e A networking issue caused a component to be unable to process traffic and resolve DNS requests as expected. \n\nA root cause analysis (RCA) document will be published within five business days.",
"name": "Azure - Canada Central (Toronto): INC0152309",
"timestamp": "Feb \u003cvar data-var='date'\u003e23\u003c/var\u003e, \u003cvar data-var='time'\u003e21:09\u003c/var\u003e - \u003cvar data-var='time'\u003e22:07\u003c/var\u003e UTC"
}
],
"name": "February",
"year": 2026
},
{
"incidents": [
{
"code": "r32lgfpkzw0y",
"impact": "critical",
"message": "\u003cb\u003eCurrent status:\u003c/b\u003e 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\n\u003cb\u003eCustomer experience:\u003c/b\u003e Customers hosted in the specified regions may have been unable to access or use multiple core Snowflake services and features. Affected users may have been unable to sign in, execute queries, or manage data. Additionally, they may have been unable to continuously stream data into Snowflake using Snowpipe Streaming, or ingest data using Snowpipe, and may have been unable to execute queries, retrieve results, or manage data objects such as tables and views.\n\n\u003cb\u003eIncident start time:\u003c/b\u003e 17:51 UTC January 27, 2026\n\u003cb\u003eIncident end time:\u003c/b\u003e 18:25 UTC January 27, 2026\n\n\u003cb\u003ePreliminary root cause:\u003c/b\u003e A recent change to our service infrastructure experienced an incompatibility issue on a subset of instances in the metadata database layer, causing requests to fail.\n\nA root cause analysis (RCA) document will be published within five business days.",
"name": "Azure - Central US (Iowa): INC0150687",
"timestamp": "Jan \u003cvar data-var='date'\u003e27\u003c/var\u003e, \u003cvar data-var='time'\u003e18:13\u003c/var\u003e - \u003cvar data-var='time'\u003e19:30\u003c/var\u003e UTC"
},
{
"code": "0w11t7x10rzg",
"impact": "critical",
"message": "\u003cb\u003eCurrent status:\u003c/b\u003e Our observations of service telemetry continue to indicate that our service has recovered following the restart of the systems related to the Snowsight application-hosting layer. We'll continue to monitor the environment until we're confident all services are functioning properly.\n\n\u003cb\u003eCustomer experience:\u003c/b\u003e Customers hosted in the specified regions may have been unable to access or use Snowflake services and features using Snowsight or may have experienced delays. A subset of customers may have encountered errors while executing queries and other related operations.\n\n\u003cb\u003eIncident start time:\u003c/b\u003e 19:02 UTC January 22, 2026\n\u003cb\u003eIncident end time:\u003c/b\u003e 19:30 UTC January 22, 2026\n\n\u003cb\u003ePreliminary root cause:\u003c/b\u003e While we're continuing to investigate to determine the underlying root cause of this issue, we suspect that a recent change made to our internal monitoring systems may have resulted in the problem with the Snowsight application-hosting layer.\n\nA root cause analysis (RCA) document will be published within five business days.",
"name": "AWS - US West (Oregon): INC0150440",
"timestamp": "Jan \u003cvar data-var='date'\u003e22\u003c/var\u003e, \u003cvar data-var='time'\u003e19:18\u003c/var\u003e - \u003cvar data-var='time'\u003e23:24\u003c/var\u003e UTC"
},
{
"code": "s2j1bnnjshl4",
"impact": "critical",
"message": "\u003cb\u003eCurrent status:\u003c/b\u003e 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\n\u003cb\u003eCustomer experience:\u003c/b\u003e Customers hosted in the specified regions may have been unable to access or use Snowflake services and features via Snowsight and may have experienced delays.\n\n\u003cb\u003eIncident start time:\u003c/b\u003e 19:00 UTC January 21, 2026\n\u003cb\u003eIncident end time:\u003c/b\u003e 20:08 UTC January 21, 2026\n\n\u003cb\u003ePreliminary root cause:\u003c/b\u003e Our preliminary investigation identified that the Snowsight application-hosting layer and the Snowsight-specific database layer experienced an issue that led to an unexpected surge in requests, leading to high resource utilization and preventing the service from processing the associated traffic, resulting in suspended login attempts.\n\nA root cause analysis (RCA) document will be published within five business days.",
"name": "AWS - US West (Oregon): INC0150359",
"timestamp": "Jan \u003cvar data-var='date'\u003e21\u003c/var\u003e, \u003cvar data-var='time'\u003e19:23\u003c/var\u003e - \u003cvar data-var='time'\u003e21:57\u003c/var\u003e UTC"
},
{
"code": "zkz78zszy9wc",
"impact": "major",
"message": "\u003cb\u003eCurrent status:\u003c/b\u003e We've confirmed after a period of monitoring that our reversal of the offending change has remediated the issue, and our service is healthy. Users with existing sessions that are still impacted should refresh their sessions to experience relief. If you experience additional issues or have questions, please open a support case via Snowflake Community.\n\n\u003cb\u003eCustomer experience:\u003c/b\u003e Customers hosted in the specified regions may have been unable to access or use Snowflake services and features using Snowsight. This specifically impacted users with existing sessions in Snowsight and not new sessions.\n\n\u003cb\u003eIncident start time:\u003c/b\u003e 18:02 UTC January 08, 2026\n\u003cb\u003eIncident end time:\u003c/b\u003e 19:00 UTC January 08, 2026\n\n\u003cb\u003ePreliminary root cause:\u003c/b\u003e A change contained within the recent Snowsight release related to a network policy check caused issues with session deserialization, which resulted in errors for users with active sessions. \n\nA root cause analysis (RCA) document will be published within five business days.",
"name": "INC0149526",
"timestamp": "Jan \u003cvar data-var='date'\u003e8\u003c/var\u003e, \u003cvar data-var='time'\u003e18:49\u003c/var\u003e - \u003cvar data-var='time'\u003e20:22\u003c/var\u003e UTC"
},
{
"code": "2659vjbnzcld",
"impact": "critical",
"message": "\u003cb\u003eCurrent status:\u003c/b\u003e Snowflake engineers have performed recovery actions to restore Snowsight availability and monitored the environment to confirm that service has resumed. We remain engaged with our third-party cloud platform provider as they work to identify root cause and follow-up actions. If you experience additional issues or have questions, please open a support case via Snowflake Community.\n\n\u003cb\u003eCustomer experience:\u003c/b\u003e Customers hosted in the specified regions may have been unable to access or use Snowflake services and features using Snowsight.\n\n\u003cb\u003eIncident start time:\u003c/b\u003e 09:02 UTC January 08, 2026\n\u003cb\u003eIncident end time:\u003c/b\u003e 10:43 UTC January 08, 2026\n\n\u003cb\u003ePreliminary root cause:\u003c/b\u003e A third-party cloud platform experienced an as-yet-undiagnosed issue which caused underlying infrastructure for Snowsight to become unavailable.\n\nA root cause analysis (RCA) document will be published within ten business days.",
"name": "Azure - West US 2 (Washington): INC0149493",
"timestamp": "Jan \u003cvar data-var='date'\u003e8\u003c/var\u003e, \u003cvar data-var='time'\u003e09:38\u003c/var\u003e - \u003cvar data-var='time'\u003e12:18\u003c/var\u003e UTC"
}
],
"name": "January",
"year": 2026
}
],
"start_time": "2026-01-01T00:00:00Z",
"time_zone": "UTC"
},
{
"end_time": "2025-12-31T23:59:59Z",
"months": [
{
"incidents": [
{
"code": "xdxj4klf7sc5",
"impact": "critical",
"message": "\u003cb\u003eCurrent status:\u003c/b\u003e We've implemented the fix for this issue and monitored the environment to confirm that the service was restored. Some customers may experience delays in ingestion as the backlog of requests is cleared. If you experience additional issues or have questions, please open a support case via Snowflake Community.\n\n\u003cb\u003eCustomer experience:\u003c/b\u003e Customers hosted in the specified regions may have been unable to execute queries and may have experienced query performance degradation. Additionally, data clustering may have appeared to be in an unhealthy state. Users may have experienced delays or failures when using Snowpipe or Snowpipe Streaming to ingest files, and users may have seen a \"SQL execution internal error\" message or similar error messages.\n\n\u003cb\u003eWorkaround:\u003c/b\u003e There were no available workarounds for this issue except for customers with replication failing over to non-impacted regions. \n\n\u003cb\u003eIncident start time:\u003c/b\u003e 02:55 UTC December 16, 2025\n\u003cb\u003eIncident end time:\u003c/b\u003e 15:59 UTC December 16, 2025\n\n\u003cb\u003ePreliminary root cause:\u003c/b\u003e Our initial investigation has identified that our most recent release introduced a backwards-incompatible database schema update. As a result, previous release packages incorrectly referenced the updated fields, resulting in version mismatch errors and causing operations to fail or take an extended amount of time to complete.\n\nA root cause analysis (RCA) document will be published within five business days.",
"name": "INC0148543",
"timestamp": "Dec \u003cvar data-var='date'\u003e16\u003c/var\u003e, \u003cvar data-var='time'\u003e03:48\u003c/var\u003e - \u003cvar data-var='time'\u003e17:25\u003c/var\u003e UTC"
},
{
"code": "b66r9g23j04m",
"impact": "minor",
"message": "\u003cb\u003eCurrent status:\u003c/b\u003e 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.\n\n\u003cb\u003eCustomer experience:\u003c/b\u003e Customers hosted in the specified regions may experience degraded performance or delayed query results when managing or querying data. Queries may take longer than usual to complete, and affected users may see timeout errors.\n\n\u003cb\u003eIncident start time:\u003c/b\u003e 23:45 UTC December 09, 2025\n\u003cb\u003eIncident end time:\u003c/b\u003e 00:23 UTC December 10, 2025\n\n\u003cb\u003ePreliminary root cause:\u003c/b\u003e The metadata database infrastructure experienced an increase in workload, resulting in degraded query performance for a subset of customers.\n\nA root cause analysis (RCA) document will be published within five business days.",
"name": "AWS - US West (Oregon): INC0148166",
"timestamp": "Dec \u003cvar data-var='date'\u003e10\u003c/var\u003e, \u003cvar data-var='time'\u003e00:23\u003c/var\u003e - \u003cvar data-var='time'\u003e01:59\u003c/var\u003e UTC"
}
],
"name": "December",
"year": 2025
},
{
"incidents": [
{
"code": "z78t3ckmgrc6",
"impact": "critical",
"message": "\u003cb\u003eCurrent status:\u003c/b\u003e 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.\n\n\u003cb\u003eCustomer experience:\u003c/b\u003e Customers hosted in the specified regions may have been unable to access or use multiple core Snowflake services and features. Affected users may have been unable to sign in, execute queries, or manage data.\n\n\u003cb\u003eIncident start time:\u003c/b\u003e 19:50 UTC November 20, 2025\n\u003cb\u003eIncident end time:\u003c/b\u003e 21:15 UTC November 20, 2025\n\n\u003cb\u003ePreliminary root cause:\u003c/b\u003e Our investigation identified that a recent configuration change to our firewall rules resulted in a communication issue between our Cloud Services and Storage layer infrastructure. As a result, customer requests were unable to be processed successfully.\n\nA root cause analysis (RCA) document will be published within five business days.",
"name": "Azure - Australia East (New South Wales): INC0147071",
"timestamp": "Nov \u003cvar data-var='date'\u003e20\u003c/var\u003e, \u003cvar data-var='time'\u003e20:19\u003c/var\u003e - \u003cvar data-var='time'\u003e23:01\u003c/var\u003e UTC"
},
{
"code": "tc0rx4jmzyqs",
"impact": "none",
"message": "\u003cb\u003eCurrent status:\u003c/b\u003e We've rolled back the configuration change 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.\n\n\u003cb\u003eCustomer experience:\u003c/b\u003e Customers hosted in the specified regions may have been unable to access Snowpark Container Services services that expose public ingress endpoints. Affected customers saw a certificate error.\n\n\u003cb\u003eWorkaround:\u003c/b\u003e Affected customers could have worked around the issue by bypassing Transport Layer Security (TLS) verification.\n\n\u003cb\u003eIncident start time:\u003c/b\u003e 04:13 UTC November 19, 2025\n\u003cb\u003eIncident end time:\u003c/b\u003e 06:18 UTC November 19, 2025\n\n\u003cb\u003ePreliminary root cause:\u003c/b\u003e A configuration change for optimizing our infrastructure was incorrectly implemented, which caused a certificate error.\n\nA root cause analysis (RCA) document will be published within five business days.",
"name": "AWS - US East (N. Virginia): INC0146924",
"timestamp": "Nov \u003cvar data-var='date'\u003e19\u003c/var\u003e, \u003cvar data-var='time'\u003e06:49\u003c/var\u003e - \u003cvar data-var='time'\u003e06:49\u003c/var\u003e UTC"
},
{
"code": "ybgs43g1d3cc",
"impact": "critical",
"message": "\u003cb\u003eCurrent status:\u003c/b\u003e We've monitored our service health metrics after disabling the background maintenance process, and we've confirmed that this has resolved the issue. If you experience additional issues or have questions, please open a support case via Snowflake Community.\n\n\u003cb\u003eCustomer experience:\u003c/b\u003e Customers hosted in the specified regions may have been unable to access or use Snowflake services and features using Snowsight.\n\n\u003cb\u003eIncident start time:\u003c/b\u003e 15:27 UTC November 05, 2025\n\u003cb\u003eIncident end time:\u003c/b\u003e 18:36 UTC November 05, 2025\n\n\u003cb\u003ePreliminary root cause:\u003c/b\u003e A background maintenance process was contributing to periodic contention and degraded performance, which resulted in elevated load on a backend database. This caused intermittent errors and timeouts in Snowsight.\n\nA root cause analysis (RCA) document will be published within five business days.",
"name": "Azure - East US 2 (Virginia): INC0146178",
"timestamp": "Nov \u003cvar data-var='date'\u003e5\u003c/var\u003e, \u003cvar data-var='time'\u003e15:58\u003c/var\u003e - \u003cvar data-var='time'\u003e20:10\u003c/var\u003e UTC"
},
{
"code": "fp29113n10dm",
"impact": "minor",
"message": "\u003cb\u003eCurrent status:\u003c/b\u003e We've monitored the environment to confirm that all services are functioning properly after our third-party cloud platform implemented the fix for this issue. If you experience additional issues or have questions, please open a support case via Snowflake Community.\n\n\u003cb\u003eCustomer experience:\u003c/b\u003e Customers hosted in the specified regions may have experienced delays or intermittent failures when resuming or managing virtual warehouses. Existing warehouses that were already running may have been unaffected.\n\n\u003cb\u003eIncident start time:\u003c/b\u003e 20:00 UTC November 03, 2025\n\u003cb\u003eIncident end time:\u003c/b\u003e 20:39 UTC November 03, 2025\n\n\u003cb\u003ePreliminary root cause:\u003c/b\u003e A third-party cloud platform experienced a resource issue, which caused intermittent delays or failures when resuming or managing virtual warehouses. \n\nA root cause analysis (RCA) document will be published within ten business days.",
"name": "Azure - Australia East (New South Wales): INC0146060",
"timestamp": "Nov \u003cvar data-var='date'\u003e3\u003c/var\u003e, \u003cvar data-var='time'\u003e20:44\u003c/var\u003e - \u003cvar data-var='time'\u003e21:23\u003c/var\u003e UTC"
}
],
"name": "November",
"year": 2025
},
{
"incidents": [
{
"code": "bnwxc6yl0xvm",
"impact": "minor",
"message": "\u003cb\u003eCurrent status:\u003c/b\u003e 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.\n\n\u003cb\u003eCustomer experience:\u003c/b\u003e A subset of customers hosted in the specified regions may have experienced intermittent delays when using Snowpipe and may have experienced delayed query execution.\n\n\u003cb\u003eIncident start time:\u003c/b\u003e 19:00 UTC October 22, 2025\n\u003cb\u003eIncident end time:\u003c/b\u003e 20:45 UTC October 22, 2025\n\n\u003cb\u003ePreliminary root cause:\u003c/b\u003e Our investigation identified that this issue was related to a configuration change that unexpectedly increased compilation times, leading to delayed query execution and Snowpipe ingestion. \n\nA root cause analysis (RCA) document will be published within five business days.",
"name": "INC0145420",
"timestamp": "Oct \u003cvar data-var='date'\u003e22\u003c/var\u003e, \u003cvar data-var='time'\u003e20:23\u003c/var\u003e - \u003cvar data-var='time'\u003e21:30\u003c/var\u003e UTC"
},
{
"code": "gvmvnx7lyxjj",
"impact": "critical",
"message": "\u003cb\u003eCurrent status:\u003c/b\u003e We've coordinated with our third-party cloud platform to implement the fix for this issue, and we've monitored the environment to confirm that service was restored. We have observed stable and healthy performance across the Snowflake service since 21:18 UTC. Failback operations to origin regions may now be initiated by customers who previously failed over. In light of the recent operational severity, we provide guidance for customers to cautiously evaluate their failback criticality and determine the appropriate timing. If the failback is not strictly time-sensitive or immediately critical to your business operations, postponing the procedure until the next business day will minimize potential transition risks. If you experience additional issues or have questions, please open a support case via Snowflake Community.\n\n\u003cb\u003eCustomer experience:\u003c/b\u003e Customers hosted in the specified regions may have been unable to access or use multiple core Snowflake services and features. Affected users may have been unable to sign in, execute queries, or manage data.\n\n\u003cb\u003eIncident start time:\u003c/b\u003e 07:20 UTC October 20, 2025\n\u003cb\u003eIncident end time:\u003c/b\u003e 21:18 UTC October 20, 2025\n\n\u003cb\u003ePreliminary root cause:\u003c/b\u003e A third-party cloud platform experienced networking issues, which were traced to the failure of an underlying internal subsystem responsible for monitoring the health of its network load balancers. This ultimately caused access issues for Snowflake services and features, impacting customers hosted in the specified regions.\n\nA root cause analysis (RCA) document will be published within ten business days.",
"name": "INC0145263",
"timestamp": "Oct \u003cvar data-var='date'\u003e20\u003c/var\u003e, \u003cvar data-var='time'\u003e08:36\u003c/var\u003e - Oct \u003cvar data-var='date'\u003e21\u003c/var\u003e, \u003cvar data-var='time'\u003e01:57\u003c/var\u003e UTC"
},
{
"code": "875qk74tj33f",
"impact": "critical",
"message": "\u003cb\u003eCurrent status:\u003c/b\u003e 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.\n\n\u003cb\u003eCustomer experience:\u003c/b\u003e 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\n\u003cb\u003eIncident start time:\u003c/b\u003e 20:35 UTC October 14, 2025\n\u003cb\u003eIncident end time:\u003c/b\u003e 22:31 UTC October 14, 2025\n\n\u003cb\u003ePreliminary root cause:\u003c/b\u003e An investigation determined that, following a recent infrastructure update, a subset of newly added machines experienced connectivity issues and were unable to communicate with other components.\n\nA root cause analysis (RCA) document will be published within five business days.",
"name": "AWS - GovCloud (US-East): INC0144987",
"timestamp": "Oct \u003cvar data-var='date'\u003e14\u003c/var\u003e, \u003cvar data-var='time'\u003e21:14\u003c/var\u003e - \u003cvar data-var='time'\u003e23:31\u003c/var\u003e UTC"
},
{
"code": "q1bwmtqq46wb",
"impact": "minor",
"message": "\u003cb\u003eCurrent status:\u003c/b\u003e 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.\n\n\u003cb\u003eCustomer experience:\u003c/b\u003e Customers hosted in the specified regions may have experienced failures when attempting to create support cases via the Support Portal in Snowsight. Affected users may also have seen a message advising: \"Something went wrong: We are unable to load the page. Please use the Snowflake community portal or directly contact us on our support phone lines to get assistance\". During this incident, all other Snowsight functionality remained available and customers would have been able to raise support cases via the Community portal or by calling our Support line.\n\n\u003cb\u003eIncident start time:\u003c/b\u003e 06:40 UTC October 03, 2025\n\u003cb\u003eIncident end time:\u003c/b\u003e 10:57 UTC October 03, 2025\n\n\u003cb\u003ePreliminary root cause:\u003c/b\u003e An update to an internal profile used to route integrations between Snowsight and applications underpinning the management of support cases resulted in a subset of functionality becoming available.\n\nA root cause analysis (RCA) document will be published within five business days.",
"name": "INC0144343",
"timestamp": "Oct \u003cvar data-var='date'\u003e3\u003c/var\u003e, \u003cvar data-var='time'\u003e10:32\u003c/var\u003e - \u003cvar data-var='time'\u003e12:29\u003c/var\u003e UTC"
},
{
"code": "672tf82761p8",
"impact": "major",
"message": "\u003cb\u003eCurrent status:\u003c/b\u003e We've monitored the environment and confirmed that the service has been restored. If you experience additional issues or have questions, please open a support case via Snowflake Community.\n\n\u003cb\u003eCustomer experience:\u003c/b\u003e Customers hosted in the specified regions may have intermittently experienced degraded performance or failures when executing SQL queries leveraging Cortex services and features, such as Snowflake Cortex AISQL, Cortex REST API, Cortex Analyst, Snowflake Copilot, Cortex Agent API, and Snowflake Intelligence. Users may have received a 500 error upon failed requests. \n\n\u003cb\u003eIncident start time:\u003c/b\u003e 18:05 UTC October 02, 2025\n\u003cb\u003eIncident end time:\u003c/b\u003e 21:28 UTC October 02, 2025\n\n\u003cb\u003ePreliminary root cause:\u003c/b\u003e A configuration issue prevented service components from establishing successful sessions, resulting in connection failures and customer impact. \n\nA root cause analysis (RCA) document will be published within five business days.",
"name": "INC0144309",
"timestamp": "Oct \u003cvar data-var='date'\u003e2\u003c/var\u003e, \u003cvar data-var='time'\u003e19:12\u003c/var\u003e - \u003cvar data-var='time'\u003e22:14\u003c/var\u003e UTC"
}
],
"name": "October",
"year": 2025
}
],
"start_time": "2025-10-01T00:00:00Z",
"time_zone": "UTC"
}
]
}