Aug <var data-var='date'>20</var>, <var data-var='time'>15:43</var> UTC Resolved - Current status: The third-party cloud platform confirmed that the mitigation was complete, and its automated recovery system appears to have initiated. We independently monitored the environment and verified that service was restored. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight. Customer experience: Customers hosted in the specified regions may have been unable to connect to Snowflake via private connectivity solutions, such as PrivateLink. Other connection methods were unaffected. Incident start time: 13:25 UTC August 20, 2026 Incident end time: 14:10 UTC August 20, 2026 Preliminary root cause: A third-party cloud platform experienced a virtual networking infrastructure issue, preventing customers from connecting to Snowflake via private connectivity solutions, such as PrivateLink. While we suspect that this issue may be a recurrence of a third-party cloud platform virtual networking problem, we remain closely engaged with our third-party cloud platform as they perform their own investigation into the underlying root cause of the issue. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 10 business days. Aug <var data-var='date'>20</var>, <var data-var='time'>14:39</var> UTC Monitoring - Current status: We've coordinated with our third-party cloud platform, which has implemented a mitigation for this issue. We will continue to monitor the environment until we're confident that all services are functioning properly. Customer experience: Customers hosted in the specified regions may have been unable to connect to Snowflake via private connectivity solutions, such as PrivateLink. Other connection methods were unaffected. Incident start time: 13:25 UTC August 20, 2026 Incident end time: 14:10 UTC August 20, 2026 Preliminary root cause: A third-party cloud platform experienced a virtual networking infrastructure issue, preventing customers from connecting to Snowflake via private connectivity solutions, such as PrivateLink. Aug <var data-var='date'>20</var>, <var data-var='time'>14:19</var> UTC Identified - Current status: We're investigating an issue with Snowflake Data Cloud. We've engaged the associated Cloud Service Provider to investigate and troubleshoot this issue further. We'll provide an update within 30 minutes. Customer experience: Customers hosted in the specified regions may have been unable to connect to Snowflake via private connectivity solutions, such as PrivateLink. ETA: An ETA is not yet available. We'll provide one as soon as possible. Incident start time: 13:25 UTC August 20, 2026 Aug <var data-var='date'>20</var>, <var data-var='time'>13:47</var> UTC Investigating - Current status: We're investigating an issue with Snowflake Data Cloud. We've engaged the associated Cloud Service Provider to investigate and troubleshoot this issue further. We'll provide an update within 60 minutes. Customer experience: Customers hosted in the specified regions may have been unable to connect to Snowflake via private connectivity solutions, such as PrivateLink. 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: 13:25 UTC August 20, 2026

INC20000168

Aug <var data-var='date'>18</var>, <var data-var='time'>14:51</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 experienced issues with AI and ML functionality. Specifically, when using Cortex Code in Snowsight, customers may have seen the following: “Internal Server error: You may need to start a new chat.” All other Snowflake features were not impacted. Incident start time: 11:20 UTC August 18, 2026 Incident end time: 13:45 UTC August 18, 2026 Preliminary root cause: Resource exhaustion in the compute infrastructure caused container scheduling failures, resulting in AI and ML functionality becoming unavailable. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days. Aug <var data-var='date'>18</var>, <var data-var='time'>13:55</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. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified region may have been unable to use Cortex Code in Snowsight and may have seen the following error message: "Internal Server error: You may need to start a new chat." All other Snowflake features are not impacted. Incident start time: 11:20 UTC August 18, 2026 Incident end time: 13:45 UTC August 18, 2026 Preliminary root cause: Resource exhaustion in the compute infrastructure caused container scheduling failures, resulting in AI and ML functionality becoming unavailable. Aug <var data-var='date'>18</var>, <var data-var='time'>13:33</var> UTC Identified - Current status: We've identified an issue with container scheduling in our compute infrastructure that is affecting AI and ML functionality, and we're implementing a fix to restore service. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified region may be unable to use Cortex Code in Snowsight and may see the following error message: "Internal Server error: You may need to start a new chat." All other Snowflake features are not impacted. ETA: Our current estimate is that service will be restored within 30 minutes. Incident start time: 11:20 UTC August 18, 2026 Preliminary root cause: Resource exhaustion in the compute infrastructure caused container scheduling failures, resulting in AI and ML functionality becoming unavailable. Aug <var data-var='date'>18</var>, <var data-var='time'>12:58</var> UTC Investigating - Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 1 hour. Customer experience: Customers hosted in the specified regions may experience issues with AI and ML functionality. Specifically, when using Cortex Code in Snowsight, customer may see the following: “Internal Server error: You may need to start a new chat.”. All other Snowflake features are not impacted. 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: 11:10 UTC August 18, 2026

INC20000163

Aug <var data-var='date'>14</var>, <var data-var='time'>19:35</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 be unable to access or use Snowsight and may observe "503 Service Unavailable" errors. Incident start time: 17:05 UTC August 14, 2026 Incident end time: 18:12 UTC August 14, 2026 Preliminary root cause: A routine system configuration change intended to optimize performance caused elevated latency in the metadata layer, resulting in service disruptions. Once identified, the configuration was reverted and affected service infrastructure was restarted to restore service. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days. Aug <var data-var='date'>14</var>, <var data-var='time'>18: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 been unable to access or use Snowsight and may have seen "503 Service Unavailable" errors. Incident start time: 17:05 UTC August 14, 2026 Incident end time: 18:12 UTC August 14, 2026 Preliminary root cause: A routine system configuration change intended to optimize performance caused elevated latency in the metadata layer, resulting in service disruptions. Once identified, the configuration was reverted and affected service infrastructure was restarted to restore service. Aug <var data-var='date'>14</var>, <var data-var='time'>17:58</var> UTC Identified - Current status: We've identified a system configuration issue affecting Snowsight, and we're implementing a fix to restore service. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified region may be unable to access or use Snowsight and may observe "503 Service Unavailable" errors. ETA: Our current estimate is that service will be restored within 30 minutes. Workaround: There are currently no available workarounds for this issue. Incident start time: 17:05 UTC August 14, 2026 Aug <var data-var='date'>14</var>, <var data-var='time'>17:29</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 using Snowsight. Affected users may be unable to sign in and may observe "503 Service Unavailable" errors. Incident start time: 17:05 UTC August 14, 2026

INC20000158

Aug <var data-var='date'>14</var>, <var data-var='time'>16:28</var> UTC Resolved - Current status: We've monitored the environment to confirm that service was restored. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight. Customer experience: Customers hosted in the specified region may have experienced intermittent authentication failures and "service unavailable" errors between approximately 14:20 and 14:45 UTC. Incident start time: 14:20 UTC August 14, 2026 Incident end time: 14:45 UTC August 14, 2026 Preliminary root cause: A service infrastructure layer supporting authentication and session initiation for Snowsight entered an unhealthy state, causing login failures and service disruptions. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days. Aug <var data-var='date'>14</var>, <var data-var='time'>15:19</var> UTC Monitoring - Current status: We've identified an issue that caused elevated error rates for Snowsight availability, and we've validated that service health has returned to normal following action by automated recovery systems. 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 experienced intermittent authentication failures and "service unavailable" errors between approximately 14:20 and 14:45 UTC. Incident start time: 14:20 UTC August 14, 2026 Incident end time: 14:45 UTC August 14, 2026 Preliminary root cause: A service infrastructure layer supporting authentication and session initiation for Snowsight entered an unhealthy state, causing login failures and service disruptions.

INC20000157

Aug <var data-var='date'> 5</var>, <var data-var='time'>15:49</var> UTC Resolved - Current status: We've confirmed that this issue has been resolved, and we have monitored the environment to confirm that the affected functionality is now working as expected. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight. Customer experience: Customers hosted in the specified region may have been intermittently unable to use CoCo services through Snowsight. Users may have seen an "Internal Server Error" when interacting with the service. All other Snowflake features were not impacted. Incident start time: 11:40 UTC August 05, 2026 Incident end time: 15:00 UTC August 05, 2026 Preliminary root cause: An underlying system component supporting Cortex services experienced failures due to connectivity issues with the file system, resulting in intermittent customer impact. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days. Aug <var data-var='date'> 5</var>, <var data-var='time'>15:14</var> UTC Monitoring - Current status: We've completed implementing our fix for this issue, and we'll continue to monitor the environment until we're confident all services are functioning properly. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified region may have been intermittently unable to use CoCo services through Snowsight. Users may have received an "Internal Server Error" when interacting with the service. All other Snowflake features were not impacted. Incident start time: 11:40 UTC August 05, 2026 Incident end time: 15:00 UTC August 05, 2026 Preliminary root cause: An underlying system component supporting Cortex services experienced failures due to connectivity issues with the file system, resulting in intermittent customer impact. Aug <var data-var='date'> 5</var>, <var data-var='time'>15:00</var> UTC Identified - Current status: We've identified an issue with the underlying infrastructure supporting CoCo services, and we're implementing a fix to restore service. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified region may be unable to use CoCo services through Snowsight. Users may receive an "Internal Server Error" when interacting with the service. All other Snowflake features are not impacted. ETA: Our current estimate is that service will be restored within 30 minutes. Incident start time: 11:40 UTC August 05, 2026 Preliminary root cause: An underlying system component supporting CoCo services experienced failures, resulting in customer impact. Aug <var data-var='date'> 5</var>, <var data-var='time'>14:41</var> UTC Investigating - Current status: We're continuing to investigate the issue with Snowflake Data Cloud. We're investigating a portion of infrastructure that appears unhealthy to develop a mitigation plan. We'll provide another update within 1 hour. Customer experience: Customers hosted in the specified regions may be experiencing issues using CoCo through Snowsight. Users may receive an "Internal Server Error," when interacting with the service.

INC20000139

Aug <var data-var='date'> 3</var>, <var data-var='time'>20:58</var> UTC Resolved - Current status: We've confirmed that this issue has been resolved, and we have monitored the environment to confirm that the affected functionality is now working as expected. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight. Customer experience: Customers hosted in the specified region may have been unable to start, resume, or manage virtual warehouses. The impact occurred during the periods of 13:33 to 15:20 UTC, and 16:05 to 16:36 UTC on August 03, 2026. Virtual warehouses may have appeared as stuck in the associated state. Existing warehouses that were already running may have been unaffected. Customers may also have seen queued or delayed queries for workloads running on affected warehouses. Additionally, some serverless tasks may have experienced residual queuing or failures until the backlog of requests which accumulated during the impact windows was processed. Incident start time: 13:33 UTC August 03, 2026 Incident end time: 16:36 UTC August 03, 2026 Preliminary root cause: A Cloud Services component responsible for virtual warehouse management became unhealthy. This caused failures in the internal workflows used to allocate and manage compute resources for warehouse start and resume operations, resulting in customer impact. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days. Aug <var data-var='date'> 3</var>, <var data-var='time'>18:15</var> UTC Update - Current status: We've confirmed that our service has remained stable since 16:35 UTC, following our mitigation action; however, we're continuing to monitor the environment to confirm that the affected functionality continues to work as expected. Customer experience: Customers hosted in the specified region may have been unable to start, resume, or manage virtual warehouses. Virtual warehouses may have appeared as stuck in the associated state. Existing warehouses that were already running may have been unaffected. Customers may also have seen queued or delayed queries for workloads running on affected warehouses. Workaround: There were no available workarounds for this issue. Incident start time: 13:35 UTC August 03, 2026 Incident end time: 16:36 UTC August 03, 2026 Preliminary root cause: A Cloud Services component responsible for virtual warehouse management became unhealthy. This caused failures in the internal workflows used to allocate and manage compute resources for warehouse start and resume operations, resulting in customer impact. Aug <var data-var='date'> 3</var>, <var data-var='time'>17:17</var> UTC Monitoring - Current status: We have identified that the previously affected Cloud Services component became unhealthy again, which is preventing virtual warehouses from starting or resuming. We've implemented an additional fix and we're continuing to monitor to confirm that we have fully recovered. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified region may be unable to start, resume, or manage virtual warehouses. Virtual warehouses may appear as stuck in the associated state. Existing warehouses that were already running may be unaffected. Customers may also see queued or delayed queries for workloads running on affected warehouses. Workaround: There were no available workarounds for this issue. Incident start time: 13:35 UTC August 03, 2026 Incident end time: 16:36 UTC August 03, 2026 Preliminary root cause: An internal system component became unhealthy, causing virtual warehouse management operations to fail, resulting in customer impact. Aug <var data-var='date'> 3</var>, <var data-var='time'>16:42</var> UTC Investigating - Current status: While we observed a period of recovery, our telemetry identified a recurrence of impact. We are implementing a mitigation to restore warehouse functionality, and we’ll provide another update within 30 minutes. Customer experience: Customers hosted in the specified region may be unable to start, resume, or manage virtual warehouses. Virtual warehouses may appear as stuck in the associated state. Existing warehouses that were already running may be unaffected. Customers may also see queued or delayed queries for workloads running on affected warehouses. ETA: An ETA is not yet available. We'll provide one as soon as possible. Workaround: There are no available workarounds for this issue. Incident start time: 13:35 UTC August 03, 2026 Aug <var data-var='date'> 3</var>, <var data-var='time'>15:46</var> UTC Monitoring - Current status: We have identified an unhealthy Cloud Services component that is preventing virtual warehouses from starting or resuming. We are implementing a fix and will continue to monitor to confirm that we have fully recovered. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to start, resume, or manage virtual warehouses. Virtual warehouses may appear as stuck in the associated state. Existing warehouses that are already running may be unaffected. Customers may also see queued or delayed queries for workloads running on affected warehouses. ETA: We are actively monitoring recovery, and customers should be starting to see improvement. Workaround: There were no available workarounds for this issue. Incident start time: 13:35 UTC August 03, 2026 Incident end time: 15:20 UTC August 03, 2026 Preliminary root cause: An internal system component became unhealthy, causing virtual warehouse management operations to fail, resulting in customer impact. Aug <var data-var='date'> 3</var>, <var data-var='time'>15:15</var> UTC Update - Current status: We have so far not identified any recent changes directly contributing to this problem and are currently focused on investigating performance issues affecting the system that controls virtual warehouse management. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to start, resume, or manage virtual warehouses. Virtual warehouses may appear as stuck in the associated state. Existing warehouses that are already running may be unaffected. Customers may also see queued or delayed queries for workloads running on affected warehouses. 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: 13:35 UTC August 03, 2026 Aug <var data-var='date'> 3</var>, <var data-var='time'>14:39</var> UTC Update - Current status: We're continuing to investigate the issue with Snowflake Data Cloud, and we're analyzing recent changes and telemetry to determine a mitigation plan. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to start, resume, or manage virtual warehouses. Virtual warehouses may appear as stuck in the associated state. Existing warehouses that are already running may be unaffected. 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: 13:35 UTC August 03, 2026 Aug <var data-var='date'> 3</var>, <var data-var='time'>14:11</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 start, resume, or manage virtual warehouses. Virtual warehouses may appear as stuck in the associated state. Existing warehouses that are already running may be unaffected. Incident start time: 13:35 UTC August 03, 2026

INC20000129

Aug <var data-var='date'> 3</var>, <var data-var='time'>08:15</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 experienced intermittent Snowsight login failures, elevated page load times, or session timeouts when accessing the web interface. Affected users may encounter errors such as "Failed to fetch" and "Execution failed", or HTTP 503 Service Unavailable messages. The issue was intermittent and did not affect all users or login attempts simultaneously; retrying failed requests generally results in successful connection. Although initial indications were that this issue was affecting multiple deployments, subsequent investigation demonstrated the issue was restricted to the AWS - Asia Pacific (Tokyo) region. Incident start time: 00:53 UTC August 03, 2026 Incident end time: 06:15 UTC August 03, 2026 Preliminary root cause: An update intended to improve the efficiency of connection handling at the network routing layer was identified and rolled back to restore service. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days. Aug <var data-var='date'> 3</var>, <var data-var='time'>06:59</var> UTC Update - 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 experienced intermittent Snowsight login failures, elevated page load times, or session timeouts when accessing the web interface. Affected users may encounter errors such as "Failed to fetch" and "Execution failed", or HTTP 503 Service Unavailable messages. The issue was intermittent and did not affect all users or login attempts simultaneously; retrying failed requests generally results in successful connection. Although initial indications were that this issue was affecting multiple deployments, subsequent investigation demonstrated the issue was restricted to the AWS - Asia Pacific (Tokyo) region. Incident start time: 00:53 UTC August 03, 2026 Incident end time: 06:15 UTC August 03, 2026 Preliminary root cause: An update intended to improve the efficiency of connection handling at the network routing layer was identified and rolled back to restore service. Aug <var data-var='date'> 3</var>, <var data-var='time'>06:58</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 experienced intermittent Snowsight login failures, elevated page load times, or session timeouts when accessing the web interface. Affected users may encounter errors such as "Failed to fetch" and "Execution failed", or HTTP 503 Service Unavailable messages. The issue was intermittent and did not affect all users or login attempts simultaneously; retrying failed requests generally results in successful connection. Although initial indications were that this issue was affecting multiple deployments, subsequent investigation demonstrated the issue was restricted to the AWS - Asia Pacific (Tokyo) region. Incident start time: 00:53 UTC August 03, 2026 Incident end time: 06:15 UTC August 03, 2026 Preliminary root cause: An update intended to improve the efficiency of connection handling at the network routing layer was identified and rolled back to restore service. Aug <var data-var='date'> 3</var>, <var data-var='time'>06:47</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 1 hour. Customer experience: Customers hosted in the specified region may experience intermittent Snowsight login failures, elevated page load times, or session timeouts when accessing the web interface. Affected users may encounter errors such as "Failed to fetch" and "Execution failed", or HTTP 503 Service Unavailable messages. The issue is intermittent and does not affect all users or login attempts simultaneously; retrying failed requests generally results in successful connection. Please note that further investigation has demonstrated this issue is restricted to the AWS - Asia Pacific (Tokyo) region. 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 beyond retrying failed requests. Incident start time: 00:53 UTC August 03, 2026 Aug <var data-var='date'> 3</var>, <var data-var='time'>05:53</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 Snowsight login failures, elevated page load times, or session timeouts when accessing the web interface. Affected users may encounter errors such as "Failed to fetch" and "Execution failed", or HTTP 503 Service Unavailable messages. The issue is intermittent and does not affect all users or login attempts simultaneously; retrying failed requests generally results in successful connection. 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 beyond retrying failed requests. Incident start time: 00:53 UTC August 03, 2026

INC20000128

Jul <var data-var='date'>30</var>, <var data-var='time'>04:56</var> UTC Resolved - Current status: We've monitored the environment and confirmed that reverting the configuration change restored service. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight. Customer experience: Customers hosted in the specified regions may have been unable to log in to Snowsight. Affected users may have encountered HTTP 404 errors or "Incoming request with IP/Token is not allowed to access Snowflake" errors when attempting to access Snowsight via private endpoints. Workaround: There were no available workarounds for this issue. Incident start time: 00:18 UTC July 30, 2026 Incident end time: 03:52 UTC July 30, 2026 Preliminary root cause: A recent configuration change to a subset of the routing infrastructure caused connectivity failures for customers accessing Snowsight via private endpoints. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days. Jul <var data-var='date'>30</var>, <var data-var='time'>04:17</var> UTC Monitoring - Current status: We've reverted a recent configuration change and confirmed that service has been restored. We'll continue to monitor the environment until we're confident all services are functioning properly. Customer experience: Customers hosted in the specified regions may have been unable to log in to Snowsight. Affected users may have encountered HTTP 404 errors or "Incoming request with IP/Token is not allowed to access Snowflake" errors when attempting to access Snowsight via private endpoints. Workaround: There were no available workarounds for this issue. Incident start time: 00:18 UTC July 30, 2026 Incident end time: 03:52 UTC July 30, 2026 Preliminary root cause: A recent configuration change to a subset of the routing infrastructure caused connectivity failures for customers accessing Snowsight via private endpoints. Jul <var data-var='date'>30</var>, <var data-var='time'>03:30</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 log in to Snowsight. Affected users may encounter HTTP 404 errors or "Incoming request with IP/Token is not allowed to access Snowflake" errors when attempting to access Snowsight via private endpoints. ETA: Our current estimate is that service will be restored within 1 hour. Workaround: There are currently no available workarounds for this issue. Jul <var data-var='date'>30</var>, <var data-var='time'>03:00</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 log in to Snowsight. Affected users may encounter HTTP 404 errors or "Incoming request with IP/Token is not allowed to access Snowflake" errors when attempting to access Snowsight via private endpoints.

INC20000115

Jul <var data-var='date'>25</var>, <var data-var='time'>16:01</var> UTC Resolved - Current status: We've confirmed that this issue has been resolved, and we have monitored the environment to confirm that the affected functionality is now working as expected. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight. Customer experience: Customers hosted in the specified region may have been unable to resume warehouses or may have experienced significant delays with serverless tasks and other workloads that required compute resources. Queries may have queued for extended periods instead of executing immediately, with some customers experiencing delays of several hours. Workaround: There were no available workarounds for this issue. Incident start time: 07:45 UTC July 25, 2026 Incident end time: 15:05 UTC July 25, 2026 Preliminary root cause: Unexpected demand from a large-scale workload exceeded available network capacity in the affected region, causing resource exhaustion that prevented new compute resources from being provisioned. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days. Jul <var data-var='date'>25</var>, <var data-var='time'>15:28</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 been unable to resume warehouses or may have experienced significant delays with serverless tasks and other workloads that required compute resources. Queries may have queued for extended periods instead of executing immediately, with some customers experiencing delays of several hours. Workaround: There were no available workarounds for this issue. Incident start time: 07:45 UTC July 25, 2026 Incident end time: 15:05 UTC July 25, 2026 Preliminary root cause: Unexpected demand from a large-scale workload exceeded available network capacity in the affected region, causing resource exhaustion that prevented new compute resources from being provisioned. Jul <var data-var='date'>25</var>, <var data-var='time'>14:38</var> UTC Update - Current status: We've identified that IP address exhaustion in the affected region is preventing new compute resources from being provisioned, and we're implementing additional network capacity to restore service. We'll provide another update within 2 hours. Customer experience: Customers hosted in the specified region may be unable to resume warehouses or may experience significant delays with serverless tasks and other workloads that require compute resources. Queries may queue for extended periods instead of executing immediately, with some customers experiencing delays of several hours. ETA: We've implemented additional network capacity to resolve the IP address exhaustion. Service restoration is dependent on additional workload adjustments affecting resource consumption. An ETA is not yet available. We'll provide one as soon as possible. Workaround: There are currently no available workarounds for this issue. Incident start time: 07:45 UTC July 25, 2026 Preliminary root cause: Unexpected demand from a large-scale workload exceeded available network capacity in the affected region, causing IP address exhaustion that prevents new compute resources from being provisioned. Jul <var data-var='date'>25</var>, <var data-var='time'>12:45</var> UTC Update - Current status: We've identified that IP address exhaustion in the affected region is preventing new compute resources from being provisioned, and we're implementing additional network capacity to restore service. We'll provide another update within 2 hours. Customer experience: Customers hosted in the specified region may be unable to resume warehouses or may experience significant delays with serverless tasks and other workloads that require compute resources. Queries may queue for extended periods instead of executing immediately, with some customers experiencing delays of several hours. ETA: We're implementing additional network capacity to resolve the IP address exhaustion. An ETA is not yet available. We'll provide one as soon as possible. Workaround: There are currently no available workarounds for this issue. Incident start time: 07:45 UTC July 25, 2026 Preliminary root cause: Unexpected demand from a large-scale workload exceeded available network capacity in the affected region, causing IP address exhaustion that prevents new compute resources from being provisioned. Jul <var data-var='date'>25</var>, <var data-var='time'>10:52</var> UTC Update - 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 2 hours. Customer experience: Customers hosted in the specified region may be unable to resume warehouses or may experience delays with serverless tasks and other workloads that require compute resources. Queries may queue instead of executing immediately. ETA: We're working with a third-party cloud platform to remove throttling limits. An ETA is not yet available. We'll provide one as soon as possible. Workaround: There are currently no available workarounds for this issue. Incident start time: 07:45 UTC July 25, 2026 Preliminary root cause: Unexpected demand exceeded available capacity in the affected region, causing the third-party cloud platform to throttle provisioning requests. Jul <var data-var='date'>25</var>, <var data-var='time'>09:57</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 1 hour. 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. ETA: We're working with a third-party cloud platform to increase capacity limits. An ETA is not yet available. We'll provide one as soon as possible. Workaround: There are currently no available workarounds for this issue. Incident start time: 07:45 UTC July 25, 2026 Preliminary root cause: Unexpected demand exceeded available capacity in the affected region, causing the third-party cloud platform to throttle provisioning requests. Jul <var data-var='date'>25</var>, <var data-var='time'>09:05</var> UTC Investigating - Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 1 hour. Customer experience: Customers hosted in the specified regions may experience longer than expected warehouse resume and spin-up times for standard warehouses. All other Snowflake features are not impacted. 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: 07:45 UTC July 25, 2026

INC20000106

Jul <var data-var='date'>11</var>, <var data-var='time'>19:36</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 experienced delays or intermittent failures when resuming or managing virtual warehouses. Existing warehouses that were already running may have been unaffected. Incident start time: 16:35 UTC July 11, 2026 Incident end time: 18:10 UTC July 11, 2026 Preliminary root cause: Resource exhaustion in the binary download service caused delays when virtual warehouses attempted to download required software components during startup. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days. Jul <var data-var='date'>11</var>, <var data-var='time'>18:37</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 experienced delays or intermittent failures when resuming or managing virtual warehouses. Existing warehouses that were already running may have been unaffected. Incident start time: 16:35 UTC July 11, 2026 Incident end time: 18:10 UTC July 11, 2026 Preliminary root cause: Resource exhaustion in the binary download service caused delays when virtual warehouses attempted to download required software components during startup. Jul <var data-var='date'>11</var>, <var data-var='time'>17:41</var> UTC Investigating - Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 1 hour. 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. 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: 16:30 UTC July 11, 2026

INC20000085

Jul <var data-var='date'>10</var>, <var data-var='time'>16:28</var> UTC Resolved - Current status: We've monitored the environment to confirm that service was restored. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight. Customer experience: Customers hosted in the specified regions may have been unable to connect to Snowflake via private connectivity solutions, such as PrivateLink. Users may have encountered connection errors or timeouts. Additionally, all customers using public connectivity may have been unable to access Snowsight between July 10, 2026, at 13:26 and 13:40 UTC. Incident start time: 13:26 UTC July 10, 2026 Incident end time: 14:33 UTC July 10, 2026 Preliminary root cause: Our preliminary root cause analysis identified that the load balancing infrastructure responsible for managing connections to Snowsight temporarily entered a degraded state, preventing requests from being processed successfully. We've engaged the associated Cloud Service Provider to investigate and troubleshoot this issue further. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days. Jul <var data-var='date'>10</var>, <var data-var='time'>15:58</var> UTC Monitoring - Current status: We've confirmed PrivateLink connectivity health has recovered, 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 connect to Snowflake via private connectivity solutions, such as PrivateLink. Users may have encountered connection errors or timeouts. Additionally, all customers using public connectivity may have been unable to access Snowsight between July 10, 2026, at 13:26 and 13:40 UTC. Incident start time: 13:26 UTC July 10, 2026 Incident end time: 14:33 UTC July 10, 2026 Preliminary root cause: Our preliminary root cause analysis identified that the load balancing infrastructure responsible for managing connections to Snowsight temporarily entered a degraded state, preventing requests from being processed successfully. We've engaged the associated Cloud Service Provider to investigate and troubleshoot this issue further. Jul <var data-var='date'>10</var>, <var data-var='time'>15:13</var> UTC Identified - Current status: Our telemetry indicates the PrivateLink connectivity health has recovered on July 10, 2026, at approximately 14:33 UTC, mitigating the impact for a majority of customers. We're continuing to investigate to isolate and address the source of the issue. Customer experience: Customers hosted in the specified regions may be unable to connect to Snowflake via private connectivity solutions, such as PrivateLink. Users may encounter connection errors or timeouts. ETA: An ETA is not yet available. We'll provide one as soon as possible. Incident start time: 13:26 UTC July 10, 2026 Jul <var data-var='date'>10</var>, <var data-var='time'>14:30</var> UTC Investigating - Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 1 hour. Customer experience: Customers hosted in the specified regions may be unable to connect to Snowflake via private connectivity solutions, such as PrivateLink. Users may encounter connection errors or timeouts. 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. This may require DNS configuration changes for PrivateLink functionality.

INC20000082

Jun <var data-var='date'>30</var>, <var data-var='time'>23:34</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 been unable to access Snowsight or may have experienced being logged out unexpectedly. All other Snowflake features were not impacted. Workaround: While we were focused on remediation, customers who were logged out needed to log back in to Snowsight. Incident start time: 21:47 UTC June 30, 2026 Incident end time: 22:03 UTC June 30, 2026 Preliminary root cause: A routine system configuration change caused authentication issues with Snowsight. Once identified, the configuration was reverted. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days. Jun <var data-var='date'>30</var>, <var data-var='time'>22:39</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. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified region may have been unable to access Snowsight or may have experienced being logged out unexpectedly. All other Snowflake features were not impacted. Workaround: While we were focused on remediation, customers who were logged out needed to log back in to Snowsight. Incident start time: 21:47 UTC June 30, 2026 Incident end time: 22:03 UTC June 30, 2026 Preliminary root cause: A routine system configuration change caused authentication issues with Snowsight. Once identified, the configuration was reverted. Jun <var data-var='date'>30</var>, <var data-var='time'>22:34</var> UTC Identified - Current status: We're investigating an issue with Snowsight authentication. We are seeing recovery as of 22:03 UTC and are continuing to monitor. We'll provide an update within 60 minutes. Customer experience: Customers may be unable to access Snowsight or may experience being logged out unexpectedly. All other Snowflake features are not impacted. ETA: We have taken action to address the issue and expect it to be resolved as of 22:03 UTC. Incident start time: 21:47 UTC June 30, 2026

INC20000063

Jun <var data-var='date'>24</var>, <var data-var='time'>17:22</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 been unable to access or use Snowflake services and features using Snowsight. A subset of affected users in the region may also have been unable to execute queries, manage data, or may have experienced increased latency or performance issues with database operations. Incident start time: 15:10 UTC June 24, 2026 Incident end time: 15:50 UTC June 24, 2026 Preliminary root cause: A configuration issue caused an unexpected increase in load on our metadata database layer, resulting in cascading impact to dependent services like Snowsight and database operations. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days. Jun <var data-var='date'>24</var>, <var data-var='time'>16:44</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 been unable to access or use Snowflake services and features using Snowsight. A subset of affected users in the region may also have been unable to execute queries, manage data, or may have experienced increased latency or performance issues with database operations. Incident start time: 15:10 UTC June 24, 2026 Incident end time: 15:50 UTC June 24, 2026 Preliminary root cause: A configuration issue caused an unexpected increase in load on our metadata database layer, resulting in cascading impact to dependent services like Snowsight and database operations. Jun <var data-var='date'>24</var>, <var data-var='time'>16:06</var> UTC Update - Current status: We've identified the source of the issue, and we've implemented a fix to restore service. We're assessing the recovery of affected components and we'll provide another update within 30 minutes. 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. Following initial recovery actions, sign in functionality has been restored, but customers may observe some increased latency or performance issues until service has fully recovered. ETA: Our current estimate is that service is recovering and will be fully restored within the next 30 minutes. Incident start time: 15:10 UTC June 24, 2026 Jun <var data-var='date'>24</var>, <var data-var='time'>15:38</var> UTC Identified - 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.

INC20000052

Jun <var data-var='date'>24</var>, <var data-var='time'>07: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 been intermittently unable to access or launch Streamlit apps, or may have experienced issues with other services and features that rely on Snowpark Container Services, such as Notebooks. Users may have experienced connection timeouts and received a "Connection error" when interacting with affected services. Workaround: There were no available workarounds for this issue. Incident start time: 15:20 UTC June 23, 2026 Incident end time: 05:10 UTC June 24, 2026 Preliminary root cause: A subset of infrastructure responsible for processing service requests experienced degraded performance, which prevented requests from completing and caused connectivity failures for services that rely on Snowpark Container Services. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days. Jun <var data-var='date'>24</var>, <var data-var='time'>06:01</var> UTC Monitoring - Current status: We restarted the affected infrastructure and confirmed it fully restored the remaining affected services. We'll continue to monitor the environment until we're confident all services are functioning properly. We'll provide another update within 1 hour. Customer experience: Customers hosted in the specified region may have been intermittently unable to access or launch Streamlit apps, or may have experienced issues with other services and features that rely on Snowpark Container Services, such as Notebooks. Users may have experienced connection timeouts and received a "Connection error" when interacting with affected services. Workaround: There were no available workarounds for this issue. Incident start time: 15:20 UTC June 23, 2026 Incident end time: 05:10 UTC June 24, 2026 Preliminary root cause: A subset of infrastructure responsible for processing service requests experienced degraded performance, which prevented requests from completing and caused connectivity failures for services that rely on Snowpark Container Services. Jun <var data-var='date'>24</var>, <var data-var='time'>04:16</var> UTC Update - Current status: We're continuing to validate recovery and address residual impact. We'll provide another update within 2 hours. Customer experience: Customers hosted in the specified region may be intermittently unable to access or launch Streamlit apps, or may experience issues with other services and features that rely on Snowpark Container Services, such as Notebooks. Users may experience connection timeouts and receive a "Connection error" when interacting with affected services. ETA: An ETA is not yet available. We'll provide one as soon as possible. Workaround: There are currently no available workarounds for this issue. Incident start time: 15:20 UTC June 23, 2026 Jun <var data-var='date'>24</var>, <var data-var='time'>02:20</var> UTC Update - Current status: We've identified the issue and deployed a two-part mitigation to address it, which included adding resources to the affected infrastructure and reverting a change. Affected services are recovering, and we're working to confirm full restoration. We'll provide another update within 2 hours. Customer experience: Customers hosted in the specified region may be intermittently unable to access or launch Streamlit apps, or may experience issues with other services and features that rely on Snowpark Container Services, such as Notebooks. Users may experience connection timeouts and receive a "Connection error" when interacting with affected services. ETA: An ETA is not yet available. We'll provide one as soon as possible. Workaround: There are currently no available workarounds for this issue. Incident start time: 15:20 UTC June 23, 2026 Jun <var data-var='date'>23</var>, <var data-var='time'>23:20</var> UTC Identified - Current status: We've narrowed the issue to the request handling and authentication path for the affected services, and we're now applying and testing mitigation actions to restore service. We'll provide another update within 3 hours. Customer experience: Customers hosted in the specified region may be intermittently unable to access or launch Streamlit apps, or may experience issues with other services and features that rely on Snowpark Container Services, such as Notebooks. Users may experience connection timeouts and receive a "Connection error" when interacting with affected services. ETA: An ETA is not yet available. We'll provide one as soon as possible. Workaround: There are currently no available workarounds for this issue. Incident start time: 15:20 UTC June 23, 2026 Jun <var data-var='date'>23</var>, <var data-var='time'>21:15</var> UTC Update - Current status: We have narrowed the investigation to a request handling and authentication path for affected services. While the exact root cause is still under investigation, our teams have ruled out some earlier hypotheses and are actively evaluating potential mitigation actions. We'll provide another update within 2 hours. Customer experience: Customers hosted in the specified region may be intermittently unable to access or launch Streamlit apps, or may experience issues with other services and features that rely on Snowpark Container Services, such as Notebooks. Users may experience connection timeouts and receive a "Connection error" when interacting with affected services. ETA: An ETA is not yet available. We'll provide one as soon as possible. Workaround: There are currently no available workarounds for this issue. Incident start time: 15:20 UTC June 23, 2026 Jun <var data-var='date'>23</var>, <var data-var='time'>19:02</var> UTC Update - Current status: We've narrowed our investigation and remained focused on identifying a mitigation to address the impact to Snowpark Container Services. We'll provide another update within 2 hours. Customer experience: Customers hosted in the specified region may be unable to access or launch Streamlit apps or may experience connection timeouts and receive a "Connection error" when interacting with other services and features that rely on Snowpark Container Services. ETA: An ETA is not yet available. We'll provide one as soon as possible. Workaround: There are currently no available workarounds for this issue. Incident start time: 15:20 UTC June 23, 2026 Jun <var data-var='date'>23</var>, <var data-var='time'>17:50</var> UTC Update - Current status: We're continuing to investigate the issue affecting Snowpark Container Services to determine its source. We'll provide another update within 1 hour. Customer experience: Customers hosted in the specified region may be intermittently unable to access or launch Streamlit apps or may experience issues with other services and features that rely on Snowpark Container Services. Incident start time: 15:20 UTC June 23, 2026 Jun <var data-var='date'>23</var>, <var data-var='time'>17:01</var> UTC Investigating - Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 1 hour. Customer experience: Customers hosted in the specified region may be unable to access or launch Streamlit apps or other services and features that rely on Snowpark Container Services. Incident start time: 15:20 UTC June 23, 2026

INC20000047

Jun <var data-var='date'>23</var>, <var data-var='time'>02:35</var> UTC Resolved - Current status: We've monitored the environment to confirm that reverting the configuration change restored service. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight. Customer experience: Customers hosted in the specified region may have been unable to access Snowpark Container Services, and may have intermittently been unable to sign in to Snowsight. Affected users may have seen HTTP 500 errors. Workaround: There were no available workarounds for this issue. Incident start time: 22:38 UTC June 22, 2026 Incident end time: 01:28 UTC June 23, 2026 Preliminary root cause: A recent configuration change affected DNS resolution in the region, which caused connectivity failures for Snowpark Container Services and Snowsight. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days. Jun <var data-var='date'>23</var>, <var data-var='time'>01:43</var> UTC Monitoring - Current status: We identified and reverted a recent configuration change to resolve the impact. We'll continue to monitor the environment until we're confident all services are functioning properly. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified region may have been unable to access Snowpark Container Services, and may have intermittently been unable to sign in to Snowsight. Affected users may have seen HTTP 500 errors. Workaround: There were no available workarounds for this issue. Incident start time: 22:38 UTC June 22, 2026 Incident end time: 01:28 UTC June 23, 2026 Preliminary root cause: A recent configuration change affected DNS resolution in the region, which caused connectivity failures for Snowpark Container Services and Snowsight. Jun <var data-var='date'>23</var>, <var data-var='time'>01:05</var> UTC Investigating - Current status: We're investigating an issue with Snowpark Container Services and Snowsight. We'll provide an update within 60 minutes. Customer experience: Customers hosted in the specified region may be unable to access Snowpark Container Services, and may intermittently be unable to sign in to Snowsight. Affected users may see HTTP 500 errors. Incident start time: 22:38 UTC June 22, 2026

INC20000046

Jun <var data-var='date'>23</var>, <var data-var='time'>00:26</var> UTC Resolved - Current status: We've monitored the environment to confirm our actions have restored service. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight. 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 delays or failures with replication or when using Snowpipe to ingest files. Affected users may have been unable to execute queries and tasks or manage data, and may have seen a "Processing aborted due to error" SQL execution internal error. Incident start time: 20:12 UTC June 22, 2026 Incident end time: 21:45 UTC June 22, 2026 Preliminary root cause: Elevated load in a critical internal coordination service affected request processing for a subset of workloads. The underlying cause of the issue remains under investigation. A root cause analysis (RCA) document will be published within five business days. Jun <var data-var='date'>22</var>, <var data-var='time'>22:16</var> UTC Monitoring - Current status: We've completed actions to improve processing efficiency on the affected infrastructure and are seeing relief. We anticipate some customers may continue to experience latency as processing queues are 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 execute queries and tasks, or manage data. Users may have experienced delays or failures with replication or when using Snowpipe to ingest files. Affected users may have seen a SQL execution internal error: Processing aborted due to error. Incident start time: 20:12 UTC June 22, 2026 Incident end time: 21:45 UTC June 22, 2026 Preliminary root cause: Elevated load in a critical internal coordination service affected request processing for a subset of workloads. The underlying cause of the issue remains under investigation. Jun <var data-var='date'>22</var>, <var data-var='time'>21:48</var> UTC Update - Current status: We are continuing to investigate the underlying source of the issue. In parallel, we are working to improve processing efficiency in a portion of our service infrastructure as a potential mitigation for the increased downstream load affecting related services. 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 execute queries and tasks, or manage data. Users may experience delays or failures with replication or when using Snowpipe to ingest files. Affected users may see a SQL execution internal error: Processing aborted due to error. Workaround: There are currently no available workarounds for this issue. An ETA is not yet available. We'll provide one as soon as possible. Incident start time: 20:12 UTC June 22, 2026 Jun <var data-var='date'>22</var>, <var data-var='time'>21:10</var> UTC Update - Current status: We've confirmed that this issue impacts service, and we're continuing to investigate to determine the source of 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 multiple core Snowflake services and features. Affected users may be unable to execute queries and tasks, or manage data. Users may may experience delays or failures when using Snowpipe to ingest files. Affected users may see a SQL execution internal error: Processing aborted due to error. Incident start time: 20:12 UTC June 22, 2026 Jun <var data-var='date'>22</var>, <var data-var='time'>20:41</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 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. Users may may experience delays or failures when using Snowpipe to ingest files. Jun <var data-var='date'>22</var>, <var data-var='time'>20:35</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): INC0159680

Jun <var data-var='date'>16</var>, <var data-var='time'>21:15</var> UTC Resolved - Current status: We've validated the fix for this issue with our third-party provider and monitored the environment to confirm that service was restored. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight. Customer experience: Customers hosted in the specified region may have been unable to access or use Snowflake services and features using Snowsight. The most significant periods of impact for most customers were between 14:05-14:35 and 16:27-16:46 UTC, during which customers could not authenticate or access Snowsight. After initial recovery actions, customers were able to access Snowsight but may have been unable to perform operations within the UI or experienced intermittent periods of significant performance issues. Customers may have seen "something went wrong" or "no healthy upstream" error messages. Incident start time: 14:15 UTC June 15, 2026 Incident end time: 21:45 UTC June 15, 2026 Preliminary root cause: Backend infrastructure that supports authentication to the Snowsight service experienced a degradation due to a third-party cloud platform infrastructure issue. This triggered a cascade of connectivity issues in backend components supporting the Snowsight platform, resulting in service disruptions and intermittent access problems. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 10 business days. Jun <var data-var='date'>16</var>, <var data-var='time'>04:00</var> UTC Update - Current status: Our third-party cloud platform has confirmed that the underlying infrastructure issue was resolved as of 21:45 UTC. Service health remains stable, and out of an abundance of caution, we will continue to actively monitor the environment before posting our final update. We'll provide another update within 18 hours. Customer experience: Customers hosted in the specified region may have been unable to access or use Snowflake services and features using Snowsight, or may have experienced short periods of intermittent impact. The most significant periods of impact for most customers were between 14:05-14:35 and 16:27-16:46 UTC, during which customers could not authenticate or access Snowsight. After initial recovery actions, customers were able to access Snowsight but were unable to perform operations within the UI or experienced significant performance issues. Customers may have seen "something went wrong" or "no healthy upstream" error messages. ETA: Service is currently healthy and the underlying infrastructure issue has been resolved; however, we're continuing to validate recovery. For affected customers using replication that have initiated their failover procedures, we don't currently recommend failback to the region until after we have finished validating recovery. Incident start time: 14:15 UTC June 15, 2026 Incident end time: 21:45 UTC June 15, 2026 Preliminary root cause: Backend infrastructure that supports authentication to the Snowsight service experienced a degradation due to a third-party cloud platform infrastructure issue. This triggered a cascade of connectivity issues in backend components supporting the Snowsight platform, resulting in service disruptions and intermittent access problems. Jun <var data-var='date'>15</var>, <var data-var='time'>21:55</var> UTC Update - Current status: We are continuing to coordinate with our third-party cloud provider on addressing the underlying infrastructure issue while we closely monitor the environment. Service health has remained stable after implementing our previous mitigation actions; however, customers may continue to experience intermittent periods of degraded service performance until the issue is fully resolved. We'll provide another update in the next 4 hours. Customer experience: Customers hosted in the specified regions may experience short periods of intermittent impact to Snowflake services and features using Snowsight. The most significant periods of impact for most customers were between 14:05-14:35 UTC and 16:27-16:46, during which customers could not authenticate or access Snowsight. After initial recovery actions, customers were able to access Snowsight but were unable to perform operations within the UI or experienced significant performance issues. Customers may have seen "something went wrong" or "no healthy upstream" error messages. ETA: Service is currently healthy; however an ETA for confirming resolution of the underlying infrastructure issue is not yet available. We’ll provide one as soon as possible. For affected customers using replication that have initiated their failover procedures, we don’t currently recommend failback to the region until after we have finished validating recovery. Incident start time: 14:15 UTC June 15, 2026 Incident end time: 17:05 UTC June 15, 2026 Preliminary root cause: Backend infrastructure that supports authentication to the Snowsight service experienced a degradation due to a third-party cloud platform infrastructure issue. This triggered a cascade of connectivity issues in backend components supporting the Snowsight platform, resulting in service disruptions and intermittent access problems. Jun <var data-var='date'>15</var>, <var data-var='time'>19:22</var> UTC Monitoring - Current status: Services remain stable following our previously implemented mitigation actions; however, customers could experience performance issues until the underlying issue is resolved. We are closely monitoring the environment while we continue to collaborate with the third-party cloud provider to ensure the underlying infrastructure remains healthy. We'll provide another update in the next 2 hours. Customer experience: Customers hosted in the specified regions may have been unable to access or use Snowflake services and features using Snowsight. The most significant periods of impact for most customers were between 14:05-14:35 UTC and 16:27-16:46, during which customers could not authenticate or access Snowsight. After initial recovery actions, customers were able to access Snowsight but were unable to perform operations within the UI or experienced significant performance issues. Customers may have seen "something went wrong" or "no healthy upstream" error messages. ETA: Service is currently healthy; however an ETA for confirming resolution of the underlying infrastructure issue is not yet available. We’ll provide one as soon as possible. For affected customers using replication that have initiated their failover procedures, we don’t currently recommend failback to the region until after we have finished validating recovery. Incident start time: 14:15 UTC June 15, 2026 Incident end time: 17:05 UTC June 15, 2026 Preliminary root cause: Backend infrastructure that supports authentication to the Snowsight service experienced a degradation due to a third-party cloud platform infrastructure issue. This triggered a cascade of connectivity issues in backend components supporting the Snowsight platform, resulting in service disruptions and intermittent access problems. Jun <var data-var='date'>15</var>, <var data-var='time'>17:43</var> UTC Update - Current status: We have implemented recovery actions and telemetry indicates that service health has currently returned to normal. However, we are continuing to coordinate with our cloud provider to address the underlying issue affecting backend infrastructure health that may result in periods of intermittent performance impact. We are actively monitoring health and network connectivity of the affected components and 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. Customers may see "something went wrong" or "no healthy upstream" error messages. Some customers may be able to access Snowsight but are unable to perform operations within the UI. Recovery may be inconsistent as different parts of Snowsight are restored. ETA: Service is currently healthy; however an ETA for confirming resolution of the underlying infrastructure issue is not yet available. We’ll provide one as soon as possible. For affected customers using replication that have initiated their failover procedures, we don’t currently recommend failback to the region until after we have finished validating recovery. Incident start time: 14:15 UTC June 15, 2026 Jun <var data-var='date'>15</var>, <var data-var='time'>16:19</var> UTC Update - Current status: Following our initial recovery actions, authentication and basic navigation have been restored for most customers; however, other core Snowsight features are continuing to experience failures or degraded performance. We have identified a network connectivity issue affecting infrastructure components used by Snowsight's backend infrastructure, and we are attempting to recover the affected components. 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. Customers may see "something went wrong" or "no healthy upstream" error messages. Some customers may be able to access Snowsight but are unable to perform operations within the UI. Recovery may be inconsistent as different parts of Snowsight are restored. ETA: An ETA is not yet available. We'll provide one as soon as possible. Workaround: While we're focused on remediation, we recommend that affected customers using replication initiate their failover procedures. Incident start time: 14:15 UTC June 15, 2026 Jun <var data-var='date'>15</var>, <var data-var='time'>15:13</var> UTC Identified - Current status: We've identified an issue affecting Snowsight backend infrastructure, and we're attempting to restart affected components 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 Snowflake services and features using Snowsight. Customers may see "something went wrong" or "no healthy upstream" error messages. Some customers may be able to access Snowsight but are unable to perform operations within the UI. 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: 14:15 UTC June 15, 2026 Jun <var data-var='date'>15</var>, <var data-var='time'>14:30</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.

INC20000034

Jun <var data-var='date'>16</var>, <var data-var='time'>20:20</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 use Git repository functionality in Workspaces, including pulling changes from a connected Git repository and performing related Git operations in a Git-synced workspace. Affected customers may have seen an error message: "Workspace feature disabled: Internal only system function." Incident start time: 00:03 UTC June 16, 2026 Incident end time: 17:29 UTC June 16, 2026 Preliminary root cause: A recent Snowsight Workspaces software update changed how certain Workspace Git operations were routed and classified. Due to a code issue, some customer Git repository actions were tagged with an incorrect internal classification, causing those operations to fail. A root cause analysis (RCA) document will be published within five business days. Jun <var data-var='date'>16</var>, <var data-var='time'>18:30</var> UTC Monitoring - Current status: We've implemented the fix for this issue. Any customers still encountering the error condition may need to refresh their browser session. 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 Git repository functionality in Workspaces, including pulling changes from a connected Git repository and performing related Git operations in a Git-synced workspace. Affected customers may have seen an error message: "Workspace feature disabled: Internal only system function." Incident start time: 00:03 UTC June 16, 2026 Incident end time: 17:29 UTC June 16, 2026 Preliminary root cause: A recent Snowsight Workspaces software update changed how certain Workspace Git operations were routed and classified. Due to a code issue, some customer Git repository actions were tagged with an incorrect internal classification, causing those operations to fail. Jun <var data-var='date'>16</var>, <var data-var='time'>14:36</var> UTC Update - Current status: We're continuing to roll back a recent software release affecting Git repository functionality in Snowsight Workspaces. The rollback of the affected release is approximately 70% completed. We will provide another update within four hours. Customer experience: Customers hosted in the specified regions may be unable to use Git repository functionality in Workspaces, including pulling changes from a connected Git repository and performing related Git operations in a Git-synced workspace. Affected customers may see an error message: "Workspace feature disabled: Internal only system function." ETA: Based on current progress, we expect the rollback to complete within the next four hours. Workaround: While we're focused on remediation, please open a support case if you need immediate restoration of this functionality so we can apply a temporary account-level configuration change. Incident start time: 00:03 UTC June 16, 2026 Jun <var data-var='date'>16</var>, <var data-var='time'>12:29</var> UTC Update - Current status: We've identified a recent release issue affecting Git repository functionality in Workspaces. The rollback of the affected release is continuing and is approximately halfway completed. We will provide another update within two hours. Customer experience: Customers hosted in the specified regions may be unable to use Git repository functionality in Workspaces, including pulling changes from a connected Git repository and performing related Git operations in a Git-synced workspace. Affected customers may see an error message: "Workspace feature disabled: Internal only system function." ETA: An ETA is not yet available. We'll provide one as soon as possible. Workaround: While we're focused on remediation, please open a support case if you need immediate restoration of this functionality so we can apply a temporary account-level configuration change. Incident start time: 00:03 UTC June 16, 2026 Jun <var data-var='date'>16</var>, <var data-var='time'>11:29</var> UTC Identified - Current status: We've identified a recent release issue affecting Git repository functionality in Workspaces. The rollback of the affected release is proceeding as expected across the environment. We will provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to use Git repository functionality in Workspaces, including pulling changes from a connected Git repository and performing related Git operations in a Git-synced workspace. Affected customers may see an error message: "Workspace feature disabled: Internal only system function." ETA: An ETA is not yet available. We'll provide one as soon as possible. Workaround: While we're focused on remediation, please open a support case if you need immediate restoration of this functionality so we can apply a temporary account-level configuration change. Incident start time: 00:03 UTC June 16, 2026 Jun <var data-var='date'>16</var>, <var data-var='time'>10:29</var> UTC Investigating - Current status: We've identified a recent release issue affecting Git repository functionality in Workspaces. We're rolling back the affected release across the environment and will provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to use Git repository functionality in Workspaces, including pulling changes from a connected Git repository and performing related Git operations in a Git-synced workspace. Affected customers may see an error message: "Workspace feature disabled: Internal only system function." Workaround: While we're focused on remediation, please open a support case if you need immediate restoration of this functionality so we can apply a temporary account-level configuration change. Incident start time: 00:03 UTC June 16, 2026

INC0159144

Jun <var data-var='date'>12</var>, <var data-var='time'>20: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 seen that stored procedures that use Snowpark external access integrations failed with the following SQL execution internal error: 300010:4004234085. Incident start time: 15:10 UTC June 12, 2026 Incident end time: 19:15 UTC June 12, 2026 Preliminary root cause: A misconfiguration introduced by a recent network configuration change affecting outbound connectivity for stored procedures that use Snowpark external access integrations resulted in impact. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days. Jun <var data-var='date'>12</var>, <var data-var='time'>19:53</var> UTC Monitoring - Current status: We've fully reverted the impacting network configuration change, and our telemetry indicates that service health is recovering. 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 seen that stored procedures that use Snowpark external access integrations failed with the following SQL execution internal error: 300010:4004234085. Incident start time: 15:10 UTC June 12, 2026 Incident end time: 19:15 UTC June 12, 2026 Preliminary root cause: A misconfiguration introduced by a recent network configuration change affecting outbound connectivity for stored procedures that use Snowpark external access integrations resulted in impact. Jun <var data-var='date'>12</var>, <var data-var='time'>19:14</var> UTC Identified - Current status: Our investigation indicates the issue is related to a recent network configuration change affecting outbound connectivity for stored procedures that use Snowpark external access integrations. We are reverting the suspected change and manually correcting the affected network configuration to restore service as quickly as possible. We'll provide an update within 1 hour. Customer experience: Customers hosted in the specified regions may see that stored procedures that use Snowpark external access integrations may fail with the following SQL execution internal error: 300010:4004234085. ETA: Our current estimate is that service will be restored within 1 hour. Incident start time: 15:10 UTC June 12, 2026 Jun <var data-var='date'>12</var>, <var data-var='time'>18:21</var> UTC Investigating - Current status: We're investigating an issue with stored procedures that use Snowpark External Access integrations. We'll provide an update within 1 hour. Customer experience: Customers hosted in the specified regions may see that stored procedures that use Snowpark External Access integrations may fail with the following SQL execution internal error: 300010:4004234085. Incident start time: 15:10 UTC June 12, 2026

INC20000033

Jun <var data-var='date'>11</var>, <var data-var='time'>00:30</var> UTC Resolved - Current status: We identified and reverted a misconfigured change, and monitored the environment to confirm that service was restored. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight. Customer experience: Customers hosted in the specified region may have been unable to access or use multiple core Snowflake services and features. For example, affected users may have been unable to access Snowsight, Snowflake Openflow, Snowpark Container Services, or Cortex AI services (such as Cortex LLM functions, Agents, Analyst, and Search). Workaround: There were no available workarounds for this issue. Incident start time: 23:23 UTC June 10, 2026 Incident end time: 23:58 UTC June 10, 2026 Preliminary root cause: A misconfiguration during a system maintenance operation caused connectivity failures in the affected region. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.

INC20000032

Jun <var data-var='date'> 8</var>, <var data-var='time'>16:40</var> UTC Resolved - Current status: We've monitored the environment and confirmed that service was restored. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight. Customer experience: Customers hosted in the specified regions may have been unable to access or use Snowflake services and features using Snowsight. Customers may have experienced page not found errors or general login failures. Incident start time: 14:58 UTC June 08, 2026 Incident end time: 15:20 UTC June 08, 2026 Preliminary root cause: An internal system degradation occurred within backend database infrastructure that supports Snowsight in the affected region, causing Snowsight request failures. The issue was detected by system health monitoring, and automated recovery systems performed scaling and targeted infrastructure restart operations that helped to restore service. We’re continuing to investigate to confirm the underlying root cause details and the contributing factors. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days. Jun <var data-var='date'> 8</var>, <var data-var='time'>15:42</var> UTC Monitoring - Current status: During our investigation, the service self-recovered. 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. Customers may have experienced page not found errors or general login failures. Workaround: There are currently no available workarounds for this issue. Incident start time: 14:58 UTC June 08, 2026 Jun <var data-var='date'> 8</var>, <var data-var='time'>15: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 be unable to access or use Snowflake services and features using Snowsight.

INC20000030

May <var data-var='date'>29</var>, <var data-var='time'>22:28</var> UTC Resolved - Current status: Our third-party cloud platform has confirmed that the impact to their infrastructure has been mitigated, and we've observed that the impact to Snowflake customers has been resolved. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight. Customer experience: Customers hosted in the specified regions may have been unable to start, resume, or manage virtual warehouses. Virtual warehouses may have appeared to be stuck in the associated state. The majority of the impact occurred during the period of 05:15 UTC to 07:24 UTC on May 29, 2026. Incident start time: 04:24 UTC May 29, 2026 Incident end time: 07:24 UTC May 29, 2026 Preliminary root cause: A third-party cloud platform experienced a power outage in its data center, which affected the underlying infrastructure and caused increased latency and intermittent connectivity for some resources on which Snowflake depends. A root cause analysis (RCA) document will be published within ten business days. May <var data-var='date'>29</var>, <var data-var='time'>12:40</var> UTC Update - Current status: Although the broadest impact has been remediated by our third-party cloud platform, customers may still experience performance latency or degradation as our service provider continues to work on full restoration. As an ETA from them is unavailable, our service provider has advised these customers to enact failover to other regions where possible. We will 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 start, resume, or manage virtual warehouses. Virtual warehouses may have appeared stuck in the associated state. At this time, there should be no further impact on virtual warehouses. Incident start time: 05:15 UTC May 29, 2026 Incident end time: 07:24 UTC May 29, 2026 Preliminary root cause: A third-party cloud platform experienced a power outage in its data center, affecting the underlying infrastructure and causing increased latency and intermittent connectivity for some resources Snowflake depends on. May <var data-var='date'>29</var>, <var data-var='time'>09:36</var> UTC Monitoring - Current status: We've coordinated with our third-party cloud platform to implement 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 start, resume, or manage virtual warehouses. Virtual warehouses may appear as stuck in the associated state. Existing warehouses that are already running may be unaffected. Incident start time: 05:15 UTC May 29, 2026 Incident end time: 07:24 UTC May 29, 2026 Preliminary root cause: A third-party cloud platform experienced a power outage in its data center, affecting the underlying infrastructure and causing increased latency and intermittent connectivity for some resources Snowflake depends on. May <var data-var='date'>29</var>, <var data-var='time'>08:45</var> UTC Update - Current status: We're seeing services recover as our third-party provider continues its efforts to restore its environment, and we're actively monitoring recovery as these actions progress. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to start, resume, or manage virtual warehouses. Virtual warehouses may appear as stuck in the associated state. Existing warehouses that are already running may be unaffected. ETA: An ETA is not yet available. We'll provide one as soon as possible. Workaround: There are currently no available workarounds for this issue. Incident start time: 05:15 UTC May 29, 2026 May <var data-var='date'>29</var>, <var data-var='time'>07:45</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 start, resume, or manage virtual warehouses. Virtual warehouses may appear as stuck in the associated state. Existing warehouses that are already running may be unaffected. ETA: An ETA is not yet available. We'll provide one as soon as possible. Workaround: There are currently no available workarounds for this issue. Incident start time: 05:15 UTC May 29, 2026 May <var data-var='date'>29</var>, <var data-var='time'>06:47</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 start, resume, or manage virtual warehouses. Virtual warehouses may appear as stuck in the associated state. Existing warehouses that are already running may be unaffected. Incident start time: 05:15 UTC May 29, 2026

Azure - West US 2 (Washington): INC0157956

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.

Is Snowflake down?

Snowflake status is UP

Lastest published events

INC20000168

INC20000163

INC20000158

Snowflake Services, Components and Regions

Recent Snowflake events

INC20000168

INC20000163

INC20000158

INC20000157

INC20000139

INC20000129