Snowflake reported this critical-impact incident on its official status page on Aug 14, 2026, 17:29 UTC. It was resolved after 2h 6m.
Right now Snowflake is degraded. Live Snowflake status →
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/INC20000158](https://community.snowflake.com/s/article/INC20000158)
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
Our 5-minute checks didn't record a change in Snowflake's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.
Overlapping incidents aren't necessarily related.
Snowflake reported 23 incidents in the last 90 days, 18 of them major or critical. A typical incident lasted 1h 56m. See Snowflake's uptime and incident history