Is Snowflake Down?

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 remain logged in to Snowsight, experiencing immediate logout after successful authentication. Incident start time: 14:47 UTC August 24, 2026 Incident end time: 17:21 UTC August 24, 2026 Preliminary root cause: A system configuration change caused an outdated application version to be deployed, resulting in authentication session failures. Once identified, the configuration was corrected to restore the proper application version. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days. --- [2026-08-24T17:37:24.740Z] (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 remain logged in to Snowsight, experiencing immediate logout after successful authentication. Workaround: There were no available workarounds for this issue. Incident start time: 14:47 UTC August 24, 2026 Incident end time: 17:21 UTC August 24, 2026 Preliminary root cause: A system configuration change caused an outdated application version to be deployed, resulting in authentication session failures. Once identified, the configuration was corrected to restore the proper application version. --- [2026-08-24T17:18:29.480Z] (identified) Current status: We're in the process of implementing a fix for this issue. We'll provide an update within the next 60 minutes. Customer experience: Customers hosted in the specified region may be unable to remain logged in to Snowsight, experiencing immediate logout after successful authentication. 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: 15:00 UTC August 24, 2026 --- [2026-08-24T16:53:33.643Z] (identified) Current status: We've identified an issue with a system configuration that is causing authentication problems in Snowsight, and we're developing and implementing a fix to restore service. We'll provide an update within 30 minutes. Customer experience: Customers hosted in the specified region may be unable to remain logged in to Snowsight, experiencing immediate logout after successful authentication. 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:00 UTC August 24, 2026 --- [2026-08-24T16:22:05.520Z] (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 access or use Snowflake services and features using Snowsight. Workaround: There are currently no available workarounds for this issue. Incident start time: 15:00 UTC August 24, 2026

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. --- [2026-08-20T14:39:33.083Z] (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. --- [2026-08-20T14:19:22.251Z] (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 --- [2026-08-20T13:47:11.514Z] (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

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. --- [2026-08-18T13:55:12.871Z] (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. --- [2026-08-18T13:33:15.008Z] (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. --- [2026-08-18T12:58:11.233Z] (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