May <var data-var='date'>15</var>, <var data-var='time'>15:10</var> UTC Resolved - 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. Mar <var data-var='date'> 5</var>, <var data-var='time'>04:39</var> UTC Update - Current status: We continue to actively monitor the situation, and our cloud service provider affirms that meaningful progress is being made toward recovery, with several distinct services showing sustained improvement. While focused efforts continue toward full-service restoration for the region, the cloud service providers' initial advice to migrate your workloads and traffic to alternate Region(s) remains in place. We are in continuous contact with the provider and will post our next update once they confirm significant progress in restoring the site's physical environment, or when other material updates become available. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. ETA: An updated ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Affected customers should look for additional updates in their cloud service provider's personal health dashboard. Incident start time: 12:25 UTC March 01, 2026 Mar <var data-var='date'> 4</var>, <var data-var='time'>06:02</var> UTC Update - Current status: We continue to actively monitor the situation as we work with our cloud service provider to restore service following a power outage at a primary data center. Recovery efforts remain focused on foundational services, and multiple paths to restoration continue to be pursued. Work to restore the underlying infrastructure needed for full restoration is still in progress. Additionally, we've been informed that our cloud service provider will supplement their public service health updates with a targeted communications approach, delivered directly to customers through their personal health dashboards, for a more localized, relevant view of service health. We will provide our next update within 24 hours. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. ETA: An updated ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Affected customers should look for additional updates in their cloud service provider's personal health dashboard. Incident start time: 12:25 UTC March 01, 2026 Mar <var data-var='date'> 3</var>, <var data-var='time'>18:18</var> UTC Update - Current status: We're closely monitoring as coordination with our cloud service provider continues in an effort to restore service following the impacting power outage at a primary data center. They are prioritizing recovery for foundational services and pursuing multiple mitigation paths that do not depend on the underlying facilities being fully brought back online to provide some relief. However, full restoration will require that the underlying infrastructure be fully repaired, and this effort is ongoing. We're continuing to monitor for improvement, and we will provide our next update within 12 hours. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. ETA: An updated ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Affected customers should look for additional updates in their cloud service provider's personal health dashboard. Incident start time: 12:25 UTC March 01, 2026 Mar <var data-var='date'> 2</var>, <var data-var='time'>18:17</var> UTC Update - Current status: We're continuing to coordinate with our cloud service provider as they troubleshoot the impacting power outage at a primary data center. Elevated connectivity issues and error rates within the region will continue until the power issue has been resolved. While they're working to fully restore power and stabilize the environment, they now expect that this may take a day or more. We will provide our next update within 24 hours. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. ETA: The third-party platform has advised that it may take a day or more to resolve the issue. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Incident start time: 12:25 UTC March 01, 2026 Mar <var data-var='date'> 2</var>, <var data-var='time'>12:24</var> UTC Update - Current status: We continue to coordinate with our cloud provider following a power outage at a primary data center. Although we had observed early indicators of recovery, the provider has confirmed additional, ongoing impact that continues to cause elevated connectivity issues and error rates within the region. They continue to actively work on full restoration and environment stability but this is expected to take several hours. We will provide our next update within 6 hours. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. ETA: The third-party platform has advised that it may take multiple hours to resolve the issue. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Incident start time: 12:25 UTC March 01, 2026 Mar <var data-var='date'> 2</var>, <var data-var='time'>06:24</var> UTC Update - Current status: We continue to coordinate with our cloud provider following a power outage at a primary data center. While we have observed consistent signs of recovery in several key services, the provider is currently investigating a localized connectivity issues and elevated error rates within the region. Full restoration is expected to take several hours as they work to safely stabilize the environment. We will provide our next update within 6 hours. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. ETA: The third-party platform has advised that it may take multiple hours to resolve the issue. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Incident start time: 12:25 UTC March 01, 2026 Mar <var data-var='date'> 2</var>, <var data-var='time'>00:23</var> UTC Update - Current status: We continue to coordinate closely with our cloud provider as they work to resolve a major service disruption caused by a power outage at a primary data center. While we are seeing initial signs of recovery across several services, the provider expects full restoration to take multiple hours as they safely stabilize the environment. We'll provide another update within 6 hours. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. ETA: The third-party platform has advised that it may take multiple hours to resolve the issue. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Incident start time: 12:25 UTC March 01, 2026 Mar <var data-var='date'> 1</var>, <var data-var='time'>18:18</var> UTC Update - Current status: We're continuing to coordinate with our third-party cloud platform to develop and implement a fix to restore service. The provider has confirmed that the issue is due to a power disruption, and they expect full recovery to take multiple hours to complete. We'll provide another update within 6 hours. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. ETA: The third-party platform has advised that it may take multiple hours to resolve the issue. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Incident start time: 12:25 UTC March 01, 2026 Mar <var data-var='date'> 1</var>, <var data-var='time'>14:55</var> UTC Update - Current status: We're continuing to coordinate with our third-party cloud platform to develop and implement a fix to restore service. We'll provide another update within 4 hours. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. ETA: The third-party platform has advised that it may take multiple hours to resolve the issue. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Incident start time: 12:25 UTC March 01, 2026 Mar <var data-var='date'> 1</var>, <var data-var='time'>14:07</var> UTC Identified - Current status: We've identified an issue with a third-party cloud platform, and we're coordinating with the provider to develop and implement a fix to restore service. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Mar <var data-var='date'> 1</var>, <var data-var='time'>13:33</var> UTC Investigating - Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data.

AWS - Middle East (UAE): INC0152681

May <var data-var='date'>15</var>, <var data-var='time'>05:25</var> UTC Resolved - Current status: 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. Customer experience: 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. Incident start time: 22:50 UTC May 14, 2026 Incident end time: 04:05 UTC May 15, 2026 Preliminary root cause: A recent update to Cortex Code introduced a code issue that caused Cortex Code in Snowsight to incorrectly halt responses, preventing requests from completing. A root cause analysis (RCA) document will be published within five business days. May <var data-var='date'>15</var>, <var data-var='time'>04:34</var> UTC Monitoring - Current status: We've identified and rolled back a Cortex Code update to resolve this issue. We'll continue to monitor the environment until we're confident all services are functioning properly. Customer experience: 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. Incident start time: 22:50 UTC May 14, 2026 Incident end time: 04:05 UTC May 15, 2026 Preliminary root cause: A recent update to Cortex Code introduced a code issue that caused Cortex Code in Snowsight to incorrectly halt responses, preventing requests from completing. May <var data-var='date'>15</var>, <var data-var='time'>04:01</var> UTC Investigating - Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. Customer experience: Customers hosted in the specified regions may experience Cortex Code in Snowsight stopping mid-response after completing only one step of a request. The response may stop without an error message or may repeat without progressing.

INC0157230

May <var data-var='date'>14</var>, <var data-var='time'>00:19</var> UTC Resolved - Current status: 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. May <var data-var='date'>14</var>, <var data-var='time'>00:04</var> UTC Update - Current status: We're continuing to investigate and troubleshoot to determine the source of the issue. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may experience delays or failures when replicating data between accounts or regions. May <var data-var='date'>13</var>, <var data-var='time'>23:08</var> UTC Investigating - Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. Customer experience: Customers hosted in the specified regions may experience delays or failures when replicating data between accounts or regions.

INC0157155

May <var data-var='date'> 5</var>, <var data-var='time'>12:30</var> UTC Resolved - 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. Customer experience: Customers hosted in the specified region may have observed stale or delayed data in account usage views and organization usage views. Incident start time: 12:03 UTC May 04, 2026 Incident end time: 08:54 UTC May 05, 2026 Preliminary root cause: 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. A root cause analysis (RCA) document will be published within five business days. May <var data-var='date'> 5</var>, <var data-var='time'>11:30</var> UTC Monitoring - Current status: We've implemented the fix for this issue, and we'll continue to monitor the environment until we're confident all services are functioning properly. Customer experience: Customers hosted in the specified region may have observed stale or delayed data in account usage views and organization usage views. Incident start time: 12:03 UTC May 04, 2026 Incident end time: 08:54 UTC May 05, 2026 Preliminary root cause: 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. May <var data-var='date'> 5</var>, <var data-var='time'>09:27</var> UTC Identified - Current status: We've identified an issue affecting a subset of internal metering files, causing a delay in account usage updates. We have now completed changes to exclude those files, allowing processes to resume. Data freshness in this region is now improving as the processing backfill catches up. We are validating the remaining backlog and any required backfill before marking full recovery. We'll provide another update within two hours. Customer experience: Customers hosted in the specified region may observe stale or delayed data in account usage views and organization usage views. Usage reporting may not reflect activity after 16:00 UTC on May 4, 2026. ETA: Our current estimate is that service will be restored within 2 hours. Workaround: There are currently no available workarounds for this issue. Incident start time: 12:03 UTC May 04, 2026 May <var data-var='date'> 5</var>, <var data-var='time'>07:09</var> UTC Update - Current status: We've identified an issue affecting a subset of data files, which is resulting in a delay for account usage updates. We are preparing changes to safely exclude the affected files and allow processing to resume. Account Usage data in the affected region remains delayed while we finalize validation of the impacted files and complete recovery steps. We’ll provide another update within four hours. Customer experience: Customers hosted in the specified region may observe stale or delayed data in account usage views and organization usage views. Usage reporting may not reflect activity after 16:00 UTC on May 4, 2026. Workaround: There are currently no available workarounds for this issue. Incident start time: 12:03 UTC May 04, 2026 May <var data-var='date'> 5</var>, <var data-var='time'>05:10</var> UTC Update - Current status: We've identified an issue affecting a subset of data files, which is resulting in a delay for account usage updates. We're working on identifying a mitigation to restore normal processing. We'll provide another update within two hours. Customer experience: Customers hosted in the specified region may observe stale or delayed data in account usage views and organization usage views. Usage reporting may not reflect activity after 16:00 UTC on May 4, 2026. Workaround: There are currently no available workarounds for this issue. Incident start time: 16:50 UTC May 04, 2026 May <var data-var='date'> 5</var>, <var data-var='time'>04:12</var> UTC Investigating - Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. Customer experience: Customers hosted in the specified region may observe stale or delayed data in account usage views and organization usage views. Usage reporting may not reflect activity after 16:00 UTC on May 4, 2026. Workaround: There are currently no available workarounds for this issue. Incident start time: 16:50 UTC May 04, 2026

Azure - West US 2 (Washington): INC0156645

Apr <var data-var='date'>29</var>, <var data-var='time'>04:44</var> UTC Resolved - Current status: 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. Customer experience: 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. Incident start time: 02:05 UTC April 29, 2026 Incident end time: 04:11 UTC April 29, 2026 Preliminary root cause: 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. A root cause analysis (RCA) document will be published within five business days. Apr <var data-var='date'>29</var>, <var data-var='time'>04:27</var> UTC Monitoring - Current status: We've implemented the fix for this issue, and we'll continue to monitor the environment until we're confident all services are functioning properly. Customer experience: 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. Incident start time: 02:05 UTC April 29, 2026 Incident end time: 04:11 UTC April 29, 2026 Preliminary root cause: 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. Apr <var data-var='date'>29</var>, <var data-var='time'>03:53</var> UTC Update - Current status: We're continuing to investigate the issue with Snowflake Data Cloud. We'll provide another update within 30 minutes. Customer experience: 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. Incident start time: 02:05 UTC April 29, 2026 Apr <var data-var='date'>29</var>, <var data-var='time'>03:23</var> UTC Investigating - Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 30 minutes. Customer experience: 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. Incident start time: 02:05 UTC April 29, 2026

Azure - UK South (London): INC0156355

Apr <var data-var='date'>16</var>, <var data-var='time'>15:08</var> UTC Resolved - 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. Customer experience: Customers hosted in the specified regions may have been unable to access or use Snowflake services and features using Snowsight. Incident start time: 12:25 UTC April 16, 2026 Incident end time: 13:45 UTC April 16, 2026 Preliminary root cause: Some application instances entered a degraded state and were unable to handle downstream connections. Snowflake mitigated the issue by restarting the affected instances. A root cause analysis (RCA) document will be published within five business days. Apr <var data-var='date'>16</var>, <var data-var='time'>14:08</var> UTC Monitoring - Current status: We've implemented the fix for this issue, and we'll continue to monitor the environment until we're confident all services are functioning properly. Customer experience: Customers hosted in the specified regions may have been unable to access or use Snowflake services and features using Snowsight. Incident start time: 12:25 UTC April 16, 2026 Incident end time: 13:45 UTC April 16, 2026 Preliminary root cause: Some application instances entered a degraded state and were unable to handle downstream connections. Snowflake mitigated the issue by restarting the affected instances.

GCP - US Central 1 (Iowa): INC0155608

Apr <var data-var='date'> 7</var>, <var data-var='time'>20:56</var> UTC Resolved - Current status: 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. Customer experience: 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. Incident start time: 17:47 UTC April 07, 2026 Incident end time: 19:45 UTC April 07, 2026 Preliminary root cause: 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. A root cause analysis (RCA) document will be published within five business days. Apr <var data-var='date'> 7</var>, <var data-var='time'>20:08</var> UTC Monitoring - Current status: We've confirmed that our service has recovered following the routing of affected traffic to healthy infrastructure, and we're continuing to monitor as the health of Snowsight continues to improve. Other services are fully recovered, but some users who were affected during the period of impact may temporarily experience delayed or incomplete query history. Customer experience: Customers hosted in the specified regions may have been unable to access or use multiple core Snowflake services and features, and may have experienced latency when using Snowsight. Affected users may have been unable to sign in, execute queries, or manage data. Incident start time: 17:47 UTC April 07, 2026 Incident end time: 19:45 UTC April 07, 2026 Preliminary root cause: A portion of the infrastructure that supports core Snowflake services was operating below operational thresholds, which resulted in impact. Apr <var data-var='date'> 7</var>, <var data-var='time'>19:13</var> UTC Identified - Current status: We've identified the source of the issue as a portion of the infrastructure which supports core Snowflake services operating below operational thresholds. We've taken the affected portion of infrastructure out of active rotation and confirmed that Snowflake traffic is being routed to healthy infrastructure. Affected users may experience delayed query history. While the majority of impact appears to have subsided, we're working to confirm that impact to Snowsight specifically is recovering as well. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features, and may experience latency when using Snowsight. Affected users may be unable to sign in, execute queries, or manage data. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Incident start time: 17:47 UTC April 07, 2026 Apr <var data-var='date'> 7</var>, <var data-var='time'>18:26</var> UTC Investigating - Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data.

Azure - East US 2 (Virginia): INC0155020

Mar <var data-var='date'>30</var>, <var data-var='time'>21:38</var> UTC Resolved - Current status: 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. Customer experience: 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 > Database Explorer page could still be used to view and manage Native Apps. Incident start time: 00:00 UTC March 27, 2026 Incident end time: 05:55 UTC March 29, 2026 Preliminary root cause: 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. A root cause analysis (RCA) document will be published within five business days. Mar <var data-var='date'>30</var>, <var data-var='time'>17:10</var> UTC Update - Current status: We've implemented the fix for this issue across all regions except GCP - US East 4, where we're working to complete the rollout of the fix. We'll continue to monitor the environment and provide another update by 18:00 UTC on March 31, 2026. Customer experience: Customers may be unable to see or manage their Native Apps within the "Apps" page of the Snowsight UI. App execution and all other Snowflake features are not impacted. ETA: The affected functionality has been restored in all but one region. An ETA is not yet available for the remaining GCP - US East 4 (N. Virginia) region; we'll provide one as soon as possible. In the meantime, we recommend affected users in that region use the suggested workaround. Workaround: While we're focused on remediation, please use SQL commands (e.g., SHOW APPLICATIONS) or search for apps using the Catalog > Database Explorer page to view and manage Native Apps. Incident start time: 00:00 UTC March 27, 2026 Mar <var data-var='date'>28</var>, <var data-var='time'>05:30</var> UTC Update - Current status: We've determined a recent Snowsight UI update introduced a code issue that prevented Native Apps from being visible on the "Apps" page of Snowsight. The fix has finished rolling out to all but one region at 03:51 UTC on March 28, 2026. The rollout's progression is temporarily stalled in the remaining GCP - US East 4 (N. Virginia) region due to an infrastructure issue that we're investigating. Once that underlying infrastructure issue is mitigated, the fix will finish rolling out in that final region. We'll provide another update at 18:00 UTC on March 30, 2026. Customer experience: Customers may be unable to see or manage their Native Apps within the "Apps" page of the Snowsight UI. App execution and all other Snowflake features are not impacted. ETA: Service has been restored in all but one region. An ETA is not yet available for the remaining GCP - US East 4 (N. Virginia) region; we'll provide one as soon as possible. In the meantime, we recommend affected users in that region use the suggested workaround. Workaround: While we're focused on remediation, please use SQL commands (e.g., SHOW APPLICATIONS) or search for apps using the Catalog > Database Explorer page to view and manage Native Apps. Incident start time: 00:00 UTC March 27, 2026 Mar <var data-var='date'>27</var>, <var data-var='time'>18:34</var> UTC Identified - Current status: We've identified an issue affecting the visibility of Native Apps listings within Snowsight, and we're developing and implementing a fix to restore service. We'll provide another update within 12 hours. Customer experience: Customers are unable to see or manage their Native Apps within the "Apps" page of the Snowsight UI. App execution and all other Snowflake features are not impacted. ETA: Our current estimate is that service will be restored within 12 hours. Workaround: While we're focused on remediation, please use SQL commands (e.g., SHOW APPLICATIONS) or search for apps using the Catalog > Database Explorer page to view and manage Native Apps. Incident start time: 00:00 UTC March 27, 2026

INC0154408

Mar <var data-var='date'>21</var>, <var data-var='time'>07:12</var> UTC Resolved - 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. Customer 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. Users would have encountered HTTP 404 or other similar errors. Incident start time: 05:27 UTC March 21, 2026 Incident end time: 06:18 UTC March 21, 2026 Preliminary root cause: 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. A root cause analysis (RCA) document will be published within five business days. Mar <var data-var='date'>21</var>, <var data-var='time'>06:38</var> UTC Monitoring - Current status: We've implemented the fix for this issue, and we'll continue to monitor the environment until we're confident all services are functioning properly. Customer 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. Users would have encountered HTTP 404 or other similar errors. Incident start time: 05:27 UTC March 21, 2026 Incident end time: 06:18 UTC March 21, 2026 Preliminary root cause: 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. Mar <var data-var='date'>21</var>, <var data-var='time'>06:23</var> UTC Identified - 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. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. ETA: An ETA is not yet available. We'll provide one as soon as possible. Incident start time: 05:31 UTC March 21, 2026 Mar <var data-var='date'>21</var>, <var data-var='time'>06:02</var> UTC Investigating - Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. Incident start time: 05:31 UTC March 21, 2026

AWS - US West (Oregon): INC0154019

Mar <var data-var='date'>17</var>, <var data-var='time'>05:49</var> UTC Resolved - 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. Customer experience: Customers hosted in the specified regions may have been unable to create or alter Snowflake alerts. Incident start time: 14:53 UTC March 14, 2026 Incident end time: 04:39 UTC March 17, 2026 Preliminary root cause: A recent improvement to Snowflake alerts creation and alteration contained a code issue. A root cause analysis (RCA) document will be published within five business days. Mar <var data-var='date'>17</var>, <var data-var='time'>04:58</var> UTC Monitoring - Current status: We've finished rolling out the fix to restore service. We'll continue to monitor the environment until we're confident all services are functioning properly. Customer experience: Customers hosted in the specified regions may have been unable to create or alter Snowflake alerts. Incident start time: 14:53 UTC March 14, 2026 Incident end time: 04:39 UTC March 17, 2026 Preliminary root cause: A recent improvement to Snowflake alerts creation and alteration contained a code issue. Mar <var data-var='date'>16</var>, <var data-var='time'>23:45</var> UTC Identified - Current status: We've determined a recent improvement to Snowflake alerts creation and alteration contains a code issue, which is causing the impact. We've developed a fix and are rolling it out to restore service. We'll provide another update within 6 hours. Customer experience: Customers hosted in the specified regions may be unable to create or alter Snowflake alerts. ETA: Our current estimate is that service will be restored for all affected customers within 6 hours. Customers will see relief as the fix rolls out. In the meantime, affected customers using replication in an unaffected region may initiate their failover procedures as a way to bypass the issue. Workaround: There are currently no available workarounds for this issue. Incident start time: 14:53 UTC March 14, 2026 Mar <var data-var='date'>16</var>, <var data-var='time'>22:46</var> UTC Investigating - Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to create or alter Snowflake alerts. Incident start time: 14:53 UTC March 14, 2026

INC0153706

Mar <var data-var='date'>12</var>, <var data-var='time'>23:13</var> UTC Resolved - Current status: 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. Customer experience: 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. Workaround: 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. Incident start time: 16:30 UTC March 12, 2026 Incident end time: 20:39 UTC March 12, 2026 Preliminary root cause: An update intended to optimize Snowflake Intelligence introduced a code issue that caused problems with expired sessions attempting to access Snowflake Intelligence. Mar <var data-var='date'>12</var>, <var data-var='time'>21:50</var> UTC Monitoring - Current status: 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. Customer experience: 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. Workaround: 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. Incident start time: 16:30 UTC March 12, 2026 Incident end time: 20:39 UTC March 12, 2026 Preliminary root cause: An update intended to optimize Snowflake Intelligence introduced a code issue that caused problems with expired sessions attempting to access Snowflake Intelligence. Mar <var data-var='date'>12</var>, <var data-var='time'>20:18</var> UTC Update - Current status: We're continuing to monitor as the rollback of the Snowflake Intelligence update progresses. Affected customers should continue to experience relief as the rollback advances and reaches their environment. We'll provide another update within 4 hours. Customer experience: Customers hosted in the specified regions may be unable to use Snowflake Intelligence services and features. Additionally, users may experience issues with expired sessions attempting to access Snowflake Intelligence. Existing sessions should be unaffected. ETA: Our current estimate is that service will be restored within approximately 4 hours. We're continuing to monitor the rollback's progress to ensure this timeline remains accurate. Workaround: While we're focused on remediation, users may be 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. Mar <var data-var='date'>12</var>, <var data-var='time'>19:42</var> UTC Identified - Current status: We're aware of an issue affecting the Snowflake Data Cloud, and we've identified the source as a recent Snowflake Intelligence update. We're rolling back the change to restore service.  Customers should experience relief as the rollback progresses across the affected infrastructure. We'll provide another update within 2 hours. Customer experience: Customers hosted in the specified regions may be unable to use Snowflake Intelligence services and features. Additionally, users may experience issues with expired sessions attempting to access Snowflake Intelligence. Existing sessions should be unaffected. ETA: An ETA is not yet available. We'll provide one as soon as possible. Workaround: While we're focused on remediation, please access the service or content using the AI.Snowflake.com URL through a private browser tab.

INC0153465

Mar <var data-var='date'> 7</var>, <var data-var='time'>22:20</var> UTC Resolved - Current status: 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. Customer 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. Incident start time: 19:30 UTC March 07, 2026 Incident end time: 21:10 UTC March 07, 2026 Preliminary root cause: 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. A root cause analysis (RCA) document will be published within ten business days. Mar <var data-var='date'> 7</var>, <var data-var='time'>21:23</var> UTC Monitoring - Current status: We've coordinated with our third-party cloud platform to remediate this issue, and we'll continue to monitor the environment until we're confident all services are functioning properly. Customer 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. Incident start time: 19:30 UTC March 07, 2026 Incident end time: 21:10 UTC March 07, 2026 Preliminary root cause: 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. Mar <var data-var='date'> 7</var>, <var data-var='time'>20:37</var> UTC Identified - Current status: We've identified an issue with a third-party cloud platform, and we're coordinating with the provider to restore service. We're beginning to see some relief as mitigation actions take effect. We're continuing to monitor, and we'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Incident start time: 19:30 UTC March 07, 2026 Mar <var data-var='date'> 7</var>, <var data-var='time'>20:05</var> UTC Investigating - Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data.

AWS - Europe (Zürich): INC0153183

Feb <var data-var='date'>23</var>, <var data-var='time'>22:07</var> UTC Resolved - Current status: 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. Customer experience: 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. Incident start time: 19:26 UTC February 23, 2026 Incident end time: 21:11 UTC February 23, 2026 Preliminary root cause: A networking issue caused a component to be unable to process traffic and resolve DNS requests as expected. A root cause analysis (RCA) document will be published within five business days. Feb <var data-var='date'>23</var>, <var data-var='time'>21:47</var> UTC Monitoring - Current status: We identified a networking issue that caused a component to be unable to process traffic and resolve DNS requests as expected, resulting in impact. We implemented the fix for this issue, and we'll continue to monitor the environment until we're confident all services are functioning properly. Customer experience: Customers hosted in the specified regions may experience intermittent delays or failures when accessing or using Snowflake services and features. This may include slower query execution, intermittent availability, or limited feature functionality. Incident start time: 19:26 UTC February 23, 2026 Incident end time: 21:11 UTC February 23, 2026 Preliminary root cause: A networking issue caused a component to be unable to process traffic and resolve DNS requests as expected. Feb <var data-var='date'>23</var>, <var data-var='time'>21:09</var> UTC Investigating - Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. Customer experience: Customers hosted in the specified regions may experience intermittent delays or failures when accessing or using Snowflake services and features. This may include slower query execution, intermittent availability, or limited feature functionality. Incident start time: 19:28 UTC February 23, 2026

Azure - Canada Central (Toronto): INC0152309

Jan <var data-var='date'>27</var>, <var data-var='time'>19:30</var> UTC Resolved - 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. Customer 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. 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. Incident start time: 17:51 UTC January 27, 2026 Incident end time: 18:25 UTC January 27, 2026 Preliminary root cause: 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. A root cause analysis (RCA) document will be published within five business days. Jan <var data-var='date'>27</var>, <var data-var='time'>19:02</var> UTC Monitoring - Current status: We've identified a recent change to our service infrastructure that resulted in impact. We've reverted this change to remediate the issue, and we've observed that the issue has been resolved. We'll continue to monitor the environment until we're confident all services are functioning properly. Customer 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. 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. Incident start time: 17:51 UTC January 27, 2026 Incident end time: 18:25 UTC January 27, 2026 Preliminary root cause: 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. Jan <var data-var='date'>27</var>, <var data-var='time'>18:13</var> UTC Investigating - Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. Additionally, they may be unable to continuously stream data into Snowflake using Snowpipe Streaming, and may be unable to execute queries, retrieve results, or manage data objects such as tables and views.

Azure - Central US (Iowa): INC0150687

Jan <var data-var='date'>22</var>, <var data-var='time'>23:24</var> UTC Resolved - Current status: 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. Customer experience: 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. Incident start time: 19:02 UTC January 22, 2026 Incident end time: 19:30 UTC January 22, 2026 Preliminary root cause: 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. A root cause analysis (RCA) document will be published within five business days. Jan <var data-var='date'>22</var>, <var data-var='time'>20:48</var> UTC Monitoring - Current status: Our observations of service telemetry 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. Customer experience: 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. Incident start time: 19:02 UTC January 22, 2026 Incident end time: 19:30 UTC January 22, 2026 Preliminary root cause: 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. Jan <var data-var='date'>22</var>, <var data-var='time'>19:48</var> UTC Update - Current status: Our investigation has led us to focus on a potential issue with the Snowsight application-hosting layer. We're restarting the systems related to the Snowsight application-hosting layer, and our initial observation of telemetry indicates that this is providing relief. We're continuing to monitor as this trend continues to ensure the service returns to normal health. We'll provide an update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight or may experience delays. Jan <var data-var='date'>22</var>, <var data-var='time'>19:18</var> UTC Investigating - Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight or may experience delays.

AWS - US West (Oregon): INC0150440

Jan <var data-var='date'>21</var>, <var data-var='time'>21:57</var> UTC Resolved - 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. Customer experience: 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. Incident start time: 19:00 UTC January 21, 2026 Incident end time: 20:08 UTC January 21, 2026 Preliminary root cause: 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. A root cause analysis (RCA) document will be published within five business days. Jan <var data-var='date'>21</var>, <var data-var='time'>20:57</var> UTC Monitoring - Current status: We've completed a restart on systems related to the application layer. Our telemetry indicates that this issue is no longer occurring, and users should be able to successfully access the service via the Snowsight User Interface (UI). We'll continue to monitor the environment until we're confident all services are functioning properly. Customer experience: 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. Incident start time: 19:00 UTC January 21, 2026 Incident end time: 20:08 UTC January 21, 2026 Preliminary root cause: 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. Jan <var data-var='date'>21</var>, <var data-var='time'>20:14</var> UTC Update - Current status: We have refined our understanding of how this issue manifests, and determined that it is isolated to Snowsight. Our investigation is currently focused on potential issues with the Snowsight application-hosting layer and the Snowsight-specific database layer. We're in the process of restarting systems related to the application layer and reverting any recent application releases that were in progress to mitigate the issue as quickly as possible. We will provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight and may experience delays. Incident start time: 19:00 UTC January 21, 2026 Jan <var data-var='date'>21</var>, <var data-var='time'>19:33</var> UTC Update - Current status: We're continuing to investigate the issue with Snowflake Data Cloud. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. Jan <var data-var='date'>21</var>, <var data-var='time'>19:31</var> UTC Update - Current status: We're continuing to investigate the issue with Snowflake Data Cloud. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. Jan <var data-var='date'>21</var>, <var data-var='time'>19:23</var> UTC Investigating - Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data.

AWS - US West (Oregon): INC0150359

Jan <var data-var='date'> 8</var>, <var data-var='time'>20:22</var> UTC Resolved - Current status: 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. Customer experience: 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. Incident start time: 18:02 UTC January 08, 2026 Incident end time: 19:00 UTC January 08, 2026 Preliminary root cause: 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. A root cause analysis (RCA) document will be published within five business days. Jan <var data-var='date'> 8</var>, <var data-var='time'>19:22</var> UTC Monitoring - Current status: Our investigation has identified that a change within the recent Snowsight release caused this issue and resulted in errors for users with existing sessions. We've reverted the offending change and we're continuing to monitor to ensure our service remains healthy. Users with existing sessions that are still impacted should refresh their sessions to experience relief. Customer experience: Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight. This is specifically impacting users with existing sessions in Snowsight and not new sessions. Incident start time: 18:02 UTC January 08, 2026 Incident end time: 19:00 UTC January 08, 2026 Preliminary root cause: 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. Jan <var data-var='date'> 8</var>, <var data-var='time'>18:49</var> UTC Investigating - Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight. This is specifically impacting users with existing sessions in Snowsight and not new sessions.

INC0149526

Jan <var data-var='date'> 8</var>, <var data-var='time'>12:18</var> UTC Resolved - Current status: 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. Customer experience: Customers hosted in the specified regions may have been unable to access or use Snowflake services and features using Snowsight. Incident start time: 09:02 UTC January 08, 2026 Incident end time: 10:43 UTC January 08, 2026 Preliminary root cause: A third-party cloud platform experienced an as-yet-undiagnosed issue which caused underlying infrastructure for Snowsight to become unavailable. A root cause analysis (RCA) document will be published within ten business days. Jan <var data-var='date'> 8</var>, <var data-var='time'>11:15</var> UTC Monitoring - Current status: Snowflake engineers have performed recovery actions to restore Snowsight connectivity and have confirmed that service has resumed. Customer experience: Customers hosted in the specified regions may have been unable to access or use Snowflake services and features using Snowsight. Incident start time: 09:02 UTC January 08, 2026 Incident end time: 10:43 UTC January 08, 2026 Preliminary root cause: A third-party cloud platform experienced an as-yet-undiagnosed issue which caused underlying infrastructure for Snowsight to become unavailable. Jan <var data-var='date'> 8</var>, <var data-var='time'>11:06</var> UTC Update - Current status: Snowflake engineers have performed recovery actions expected to restore Snowsight connectivity and are currently confirming that service has resumed. In parallel, we remain engaged with our cloud service provider (CSP) to identify and resolve the issue. This issue has been confirmed as being restricted to Snowsight availability. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight. ETA: Although an ETA is not yet available, our initial validations indicate service is beginning to return to expected levels. Workaround: This issue impacts Snowsight availability only. Snowflake services and features remain available via all other methods of access. Incident start time: 09:02 UTC January 08, 2026 Jan <var data-var='date'> 8</var>, <var data-var='time'>10:59</var> UTC Identified - Current status: Snowflake engineers have performed recovery actions expected to restore Snowsight connectivity and are currently confirming that service has resumed. In parallel, we remain engaged with our cloud service provider (CSP) to identify and resolve the issue.This issue has been confirmed as being restricted to Snowsight availability, all other methods of We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight. ETA: Although an ETA is not yet available, our initial validations indicate service is beginning to return to expected levels. Workaround: This issue impacts Snowsight availability only. Snowflake services and features remain available via all other methods of access. Incident start time: 09:02 UTC January 08, 2026 Jan <var data-var='date'> 8</var>, <var data-var='time'>10:30</var> UTC Update - Current status: We've confirmed that this issue is restricted to Snowsight availability, all other methods of accessing Snowflake remain available. We're actively engaging with our cloud service provider (CSP) to identify and resolve the issue. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight. Workaround: This issue impacts Snowsight availability only. Snowflake services and features remain available via all other methods of access. Incident start time: 09:02 UTC January 08, 2026 Jan <var data-var='date'> 8</var>, <var data-var='time'>09:38</var> UTC Investigating - Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight.

Azure - West US 2 (Washington): INC0149493

Dec <var data-var='date'>16</var>, <var data-var='time'>17:25</var> UTC Resolved - Current status: 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. Customer experience: 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. Workaround: There were no available workarounds for this issue except for customers with replication failing over to non-impacted regions. Incident start time: 02:55 UTC December 16, 2025 Incident end time: 15:59 UTC December 16, 2025 Preliminary root cause: 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. A root cause analysis (RCA) document will be published within five business days. Dec <var data-var='date'>16</var>, <var data-var='time'>16:28</var> UTC Monitoring - Current status: We've completed the resolution steps for the Azure - East U.S. 2 (Virginia) region. We expect that the majority of the impact should be mitigated at this time; however, we are currently monitoring and assessing for any residual impact. We'll continue to monitor the environment until we're confident all services are functioning properly. Since resolution is being observed in affected regions, failing over is no longer recommended for customers with replication enabled in other regions, unless they continue to experience impact. Customer experience: 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 also 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. Workaround: There were no available workarounds for this issue outside of customers with replication failing over to non-impacted regions. Incident start time: 02:55 UTC December 16, 2025 Incident end time: 15:59 UTC December 16, 2025 Preliminary root cause: Our initial investigation has identified that our most recent release introduced a backwards-incompatible database schema update. As a result, previous release packages errantly referenced the updated fields, resulting in version mismatch errors and causing operations to fail or take an extended amount of time to complete. Dec <var data-var='date'>16</var>, <var data-var='time'>15:57</var> UTC Update - Current status: We are continuing to work through the resolution steps for the Azure - East U.S. 2 (Virginia) region. We will provide another update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to execute queries and may experience query performance degradation. Data clustering may appear to be in an unhealthy state. Additionally, users may experience delays or failures when using Snowpipe or Snowpipe Streaming to ingest files. Affected users may see a "SQL execution internal error" message or similar error messages. ETA: Our current estimated time for service resolution remains 16:30 UTC. Workaround: There are currently no available workarounds for this issue. Incident start time: 02:55 UTC December 16, 2025 Dec <var data-var='date'>16</var>, <var data-var='time'>15:29</var> UTC Update - Current status: We are continuing to work through the resolution steps for the Azure - East U.S. 2 (Virginia) region, which are taking longer than previously estimated. We will provide another update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to execute queries and may experience query performance degradation. Data clustering may appear to be in an unhealthy state. Additionally, users may experience delays or failures when using Snowpipe or Snowpipe Streaming to ingest files. Affected users may see a "SQL execution internal error" message or similar error messages. ETA: Our current estimate for service resolution has been updated to 16:30 UTC. Workaround: There are currently no available workarounds for this issue. Incident start time: 02:55 UTC December 16, 2025 Dec <var data-var='date'>16</var>, <var data-var='time'>15:00</var> UTC Update - Current status: We've successfully mitigated all affected regions except Azure - East US 2 (Virginia), where we are continuing to work through the resolution steps for the remainder of the region. We will provide another update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to execute queries and may experience query performance degradation. Data clustering may appear to be in an unhealthy state. Additionally, users may experience delays or failures when using Snowpipe or Snowpipe Streaming to ingest files. Affected users may see a "SQL execution internal error" message or similar error messages. ETA: Our current estimate remains that service will be restored by 15:00 UTC. Workaround: There are currently no available workarounds for this issue. Incident start time: 02:55 UTC December 16, 2025 Dec <var data-var='date'>16</var>, <var data-var='time'>14:44</var> UTC Update - Current status: We continue executing our mitigation efforts and continue to see improvements in the affected regions. We continue working through the resolution steps. We will provide another update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to execute queries and may experience query performance degradation. Data clustering may appear to be in an unhealthy state. Additionally, users may experience delays or failures when using Snowpipe or Snowpipe Streaming to ingest files. Affected users may see a "SQL execution internal error" message or similar error messages. ETA: Our current estimate remains that service will be restored by 15:00 UTC. Workaround: There are currently no available workarounds for this issue. Incident start time: 02:55 UTC December 16, 2025 Dec <var data-var='date'>16</var>, <var data-var='time'>14:15</var> UTC Update - Current status: We continue executing our mitigation efforts and continue to see significant improvements in the affected regions. We continue working through the resolution steps. We will provide another update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to execute queries and may experience query performance degradation. Data clustering may appear to be in an unhealthy state. Additionally, users may experience delays or failures when using Snowpipe or Snowpipe Streaming to ingest files. Affected users may see a "SQL execution internal error" message or similar error messages. ETA: Our current estimate remains that service will be restored by 15:00 UTC. Workaround: There are currently no available workarounds for this issue. Incident start time: 02:55 UTC December 16, 2025 Dec <var data-var='date'>16</var>, <var data-var='time'>13:48</var> UTC Update - Current status: We continue executing our mitigation efforts and see significant improvements in the affected regions. We continue working through the resolution steps. We will provide another update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to execute queries and may experience query performance degradation. Data clustering may appear to be in an unhealthy state. Additionally, users may experience delays or failures when using Snowpipe or Snowpipe Streaming to ingest files. Affected users may see a "SQL execution internal error" message or similar error messages. ETA: Our current estimate remains that service will be restored by 15:00 UTC. Workaround: There are currently no available workarounds for this issue. Incident start time: 02:55 UTC December 16, 2025 Dec <var data-var='date'>16</var>, <var data-var='time'>13:20</var> UTC Update - Current status: We continue executing our mitigation efforts. As progress continues, customers will experience gradual improvements as we work through the resolution steps. We will provide another update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to execute queries and may experience query performance degradation. Data clustering may appear to be in an unhealthy state. Additionally, users may experience delays or failures when using Snowpipe or Snowpipe Streaming to ingest files. Affected users may see a "SQL execution internal error" message or similar error messages. ETA: Our current estimate remains that service will be restored by 15:00 UTC. Workaround: There are currently no available workarounds for this issue. Incident start time: 02:55 UTC December 16, 2025 Dec <var data-var='date'>16</var>, <var data-var='time'>12:50</var> UTC Update - Current status: We continue executing our mitigation efforts. As mitigation continues to progress, customers might expect gradual improvements as we work through the resolution steps. We will provide another update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to execute queries and may experience query performance degradation. Data clustering may appear to be in an unhealthy state. Additionally, users may experience delays or failures when using Snowpipe or Snowpipe Streaming to ingest files. Affected users may see a "SQL execution internal error" message or similar error messages. ETA: Our current estimate remains that service will be restored by 15:00 UTC. Workaround: There are currently no available workarounds for this issue. Incident start time: 02:55 UTC December 16, 2025 Dec <var data-var='date'>16</var>, <var data-var='time'>12:21</var> UTC Update - Current status: We are executing our mitigation efforts. As mitigation progresses, customers might expect gradual improvements as we work through the resolution steps. We will provide another update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to execute queries and may experience query performance degradation. Data clustering may appear to be in an unhealthy state. Additionally, users may experience delays or failures when using Snowpipe or Snowpipe Streaming to ingest files. Affected users may see a "SQL execution internal error" message or similar error messages. ETA: Our current estimate is that service will be restored by 15:00 UTC. In the meantime, we recommend that customers using replication affected by this issue initiate their failover procedures. Workaround: There are currently no available workarounds for this issue. Incident start time: 02:55 UTC December 16, 2025 Dec <var data-var='date'>16</var>, <var data-var='time'>10:31</var> UTC Update - Current status: We've resolved the unexpected issues. We're continuing with our mitigation efforts. We will provide another update within 2 hours. Customer experience: Customers hosted in the specified regions may be unable to execute queries and may experience query performance degradation. Data clustering may appear to be in an unhealthy state. Additionally, users may experience delays or failures when using Snowpipe or Snowpipe Streaming to ingest files. Affected users may see a "SQL execution internal error" message or similar error messages. ETA: Our current estimate is that service will be restored by 14:00 UTC. In the meantime, we recommend that customers using replication affected by this issue initiate their failover procedures. Workaround: There are currently no available workarounds for this issue. Incident start time: 02:55 UTC December 16, 2025 Dec <var data-var='date'>16</var>, <var data-var='time'>08:36</var> UTC Update - Current status: Validation of our solution has encountered an unexpected issue. We've resolved these issues, and we're continuing with our mitigation efforts. We will provide another update within 2 hours. Customer experience: Customers hosted in the specified regions may be unable to execute queries and may experience query performance degradation. Data clustering may appear to be in an unhealthy state. Additionally, users may experience delays or failures when using Snowpipe or Snowpipe Streaming to ingest files. Affected users may see a "SQL execution internal error" message or similar error messages. ETA: Our current estimate is that service will be restored within 4 hours. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Workaround: There are currently no available workarounds for this issue. Incident start time: 02:55 UTC December 16, 2025 Dec <var data-var='date'>16</var>, <var data-var='time'>06:40</var> UTC Update - Current status: We're continuing our validations and will provide another update within 2 hours, after which we anticipate the fix will begin deploying. Customer experience: Customers hosted in the specified regions may be unable to execute queries and may experience query performance degradation. Data clustering may appear to be in an unhealthy state. Additionally, users may experience delays or failures when using Snowpipe or Snowpipe Streaming to ingest files. Affected users may see a "SQL execution internal error" message or similar error messages. ETA: Our current estimate is that service will be restored within 4 hours. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Workaround: There are currently no available workarounds for this issue. Incident start time: 02:55 UTC December 16, 2025 Dec <var data-var='date'>16</var>, <var data-var='time'>05:50</var> UTC Update - Current status: We're performing the final rounds of validation to ensure the fix will effectively restore service. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to execute queries and may experience query performance degradation. Data clustering may appear to be in an unhealthy state. Additionally, users may experience delays or failures when using Snowpipe or Snowpipe Streaming to ingest files. Affected users may see a "SQL execution internal error" message or similar error messages. ETA: Our current estimate is that service will be restored within 4 hours. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Workaround: There are currently no available workarounds for this issue. Incident start time: 02:55 UTC December 16, 2025 Dec <var data-var='date'>16</var>, <var data-var='time'>05:04</var> UTC Update - Current status: We've developed the fix, and we're preparing it for deployment to the affected regions. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to execute queries. Additionally, users may experience delays or failures when using Snowpipe or Snowpipe Streaming to ingest files. Affected users may see a "SQL execution internal error" message or similar error messages. ETA: Our current estimate is that service will be restored within 5 hours. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Workaround: There are currently no available workarounds for this issue. Incident start time: 02:55 UTC December 16, 2025 Dec <var data-var='date'>16</var>, <var data-var='time'>04:34</var> UTC Identified - Current status: We've identified the source of the issue, and we're developing a fix to resolve the impact. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to execute queries. Affected users may see a "SQL execution internal error" message or similar error messages. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Workaround: There are currently no available workarounds for this issue. Incident start time: 02:55 UTC December 16, 2025 Dec <var data-var='date'>16</var>, <var data-var='time'>03:48</var> UTC Investigating - Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to execute queries. Affected users may see a "SQL execution internal error" message or similar error messages. Incident start time: 02:55 UTC December 16, 2025

INC0148543

Dec <var data-var='date'>10</var>, <var data-var='time'>01:59</var> UTC Resolved - 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. Customer experience: 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. Incident start time: 23:45 UTC December 09, 2025 Incident end time: 00:23 UTC December 10, 2025 Preliminary root cause: The metadata database infrastructure experienced an increase in workload, resulting in degraded query performance for a subset of customers. A root cause analysis (RCA) document will be published within five business days. Dec <var data-var='date'>10</var>, <var data-var='time'>01:12</var> UTC Monitoring - Current status: We've implemented the fix for this issue, and we'll continue to monitor the environment until we're confident all services are functioning properly. Customer experience: 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. Incident start time: 23:45 UTC December 09, 2025 Incident end time: 00:23 UTC December 10, 2025 Preliminary root cause: The metadata database infrastructure experienced an increase in workload, resulting in degraded query performance for a subset of customers. Dec <var data-var='date'>10</var>, <var data-var='time'>00:23</var> UTC Investigating - Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. Customer experience: 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.

AWS - US West (Oregon): INC0148166

Nov <var data-var='date'>20</var>, <var data-var='time'>23:01</var> UTC Resolved - 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. Customer 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. Incident start time: 19:50 UTC November 20, 2025 Incident end time: 21:15 UTC November 20, 2025 Preliminary root cause: 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. A root cause analysis (RCA) document will be published within five business days. Nov <var data-var='date'>20</var>, <var data-var='time'>22:15</var> UTC Monitoring - Current status: We've implemented the fix for this issue, and we'll continue to monitor the environment until we're confident all services are functioning properly. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. Incident start time: 19:50 UTC November 20, 2025 Incident end time: 21:15 UTC November 20, 2025 Preliminary root cause: 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. Nov <var data-var='date'>20</var>, <var data-var='time'>21:13</var> UTC Update - Current status: We're continuing to investigate the issue with Snowflake Data Cloud. In the meantime, we recommend that affected customers using replication initiate their failover procedures. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. Incident start time: 19:50 UTC November 20, 2025 Nov <var data-var='date'>20</var>, <var data-var='time'>20:19</var> UTC Investigating - Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. Incident start time: 19:50 UTC November 20, 2025

Azure - Australia East (New South Wales): INC0147071

Nov <var data-var='date'>19</var>, <var data-var='time'>06:49</var> UTC Resolved - Current status: 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. Customer experience: 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. Workaround: Affected customers could have worked around the issue by bypassing Transport Layer Security (TLS) verification. Incident start time: 04:13 UTC November 19, 2025 Incident end time: 06:18 UTC November 19, 2025 Preliminary root cause: A configuration change for optimizing our infrastructure was incorrectly implemented, which caused a certificate error. A root cause analysis (RCA) document will be published within five business days.

AWS - US East (N. Virginia): INC0146924

Nov <var data-var='date'> 5</var>, <var data-var='time'>20:10</var> UTC Resolved - Current status: 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. Customer experience: Customers hosted in the specified regions may have been unable to access or use Snowflake services and features using Snowsight. Incident start time: 15:27 UTC November 05, 2025 Incident end time: 18:36 UTC November 05, 2025 Preliminary root cause: 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. A root cause analysis (RCA) document will be published within five business days. Nov <var data-var='date'> 5</var>, <var data-var='time'>19:49</var> UTC Monitoring - Current status: We've disabled the background maintenance process that we've identified is contributing to the periodic contention and degraded performance of our service. We're closely monitoring our service health to ensure that this continues to provide relief and impact does not return. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may have been unable to access or use Snowflake services and features using Snowsight. Incident start time: 15:27 UTC November 05, 2025 Incident end time: 18:36 UTC November 05, 2025 Preliminary root cause: A background maintenance process was contributing to periodic contention and degraded performance, resulting in elevated load on a backend database. This caused intermittent errors and timeouts in Snowsight. Nov <var data-var='date'> 5</var>, <var data-var='time'>18:14</var> UTC Update - Current status: While our service health metrics indicate that impact may be occurring with less frequency, we're working to disable the background maintenance process that we've identified is contributing to the periodic contention and degraded performance of our service. We're closely monitoring our service health, and we'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight. ETA: We anticipate that our mitigation action to disable the background maintenance process contributing to impact should be complete in approximately two hours. Incident start time: 15:27 UTC November 05, 2025 Nov <var data-var='date'> 5</var>, <var data-var='time'>17:12</var> UTC Identified - Current status: We've observed elevated load on a backend database that is causing intermittent errors and timeouts in Snowsight. We've identified a background maintenance process that is contributing to periodic contention and degraded performance, and we're working on a mitigation to provide relief. Customer experience: Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Incident start time: 15:27 UTC November 05, 2025 Nov <var data-var='date'> 5</var>, <var data-var='time'>15:58</var> UTC Investigating - Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight.

Azure - East US 2 (Virginia): INC0146178

Nov <var data-var='date'> 3</var>, <var data-var='time'>21:23</var> UTC Resolved - Current status: 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. Customer 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. Incident start time: 20:00 UTC November 03, 2025 Incident end time: 20:39 UTC November 03, 2025 Preliminary root cause: A third-party cloud platform experienced a resource issue, which caused intermittent delays or failures when resuming or managing virtual warehouses. A root cause analysis (RCA) document will be published within ten business days. Nov <var data-var='date'> 3</var>, <var data-var='time'>21:05</var> UTC Monitoring - Current status: We have confirmed that our third-party cloud platform has implemented the fix for this issue, and we'll continue to monitor the environment until we're confident all services are functioning properly. Customer experience: Customers hosted in the specified regions may experience delays or intermittent failures when resuming or managing virtual warehouses. Existing warehouses that are already running may be unaffected. Incident start time: 20:00 UTC November 03, 2025 Incident end time: 20:39 UTC November 03, 2025 Preliminary root cause: A third-party cloud platform experienced a resource issue, which caused intermittent delays or failures when resuming or managing virtual warehouses. Nov <var data-var='date'> 3</var>, <var data-var='time'>20:44</var> UTC Investigating - Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. Customer experience: Customers hosted in the specified regions may experience delays or intermittent failures when resuming or managing virtual warehouses. Existing warehouses that are already running may be unaffected. Incident start time: 20:00 UTC November 03, 2025

Azure - Australia East (New South Wales): INC0146060

Oct <var data-var='date'>22</var>, <var data-var='time'>21:30</var> UTC Resolved - 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. Customer experience: A subset of customers hosted in the specified regions may have experienced intermittent delays when using Snowpipe and may have experienced delayed query execution. Incident start time: 19:00 UTC October 22, 2025 Incident end time: 20:45 UTC October 22, 2025 Preliminary root cause: 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. A root cause analysis (RCA) document will be published within five business days. Oct <var data-var='date'>22</var>, <var data-var='time'>21:01</var> UTC Monitoring - Current status: We've implemented the fix for this issue, and we'll continue to monitor the environment until we're confident all services are functioning properly. Customer experience: A subset of customers hosted in the specified regions may have experienced intermittent delays when using Snowpipe and may have experienced delayed query execution. Incident start time: 19:00 UTC October 22, 2025 Incident end time: 20:45 UTC October 22, 2025 Preliminary root cause: 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. Oct <var data-var='date'>22</var>, <var data-var='time'>20:23</var> UTC Investigating - Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. Customer experience: A subset of customers hosted in the specified regions may experience intermittent delays when using Snowpipe and may experience delayed query execution. Incident start time: 19:00 UTC October 22, 2025

Is Snowflake down?

Snowflake status is UP

Lastest published events

AWS - Middle East (UAE): INC0152681

INC0157230

INC0157155

Snowflake Services, Components and Regions

Recent Snowflake events

AWS - Middle East (UAE): INC0152681

INC0157230

INC0157155

Azure - West US 2 (Washington): INC0156645

Azure - UK South (London): INC0156355

GCP - US Central 1 (Iowa): INC0155608

Get your FREE account now,
5 monitors included!

Is Snowflake down?

Snowflake status is UP

Lastest published events

AWS - Middle East (UAE): INC0152681

INC0157230

INC0157155

Snowflake Services, Components and Regions

Recent Snowflake events

AWS - Middle East (UAE): INC0152681

INC0157230

INC0157155

Azure - West US 2 (Washington): INC0156645

Azure - UK South (London): INC0156355

GCP - US Central 1 (Iowa): INC0155608

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!