Snowflake reports multiple service issues

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.

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.

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

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

Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site: [https://community.snowflake.com/s/article/INC20000139](https://community.snowflake.com/s/article/INC20000139)

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.

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.

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.

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.