**Snowflake Snowsight Outage – August 14, 2026** A routine performance optimization configuration change caused elevated latency in Snowflake's metadata layer, resulting in a ~1 hour 7 minute outage (17:05–18:12 UTC) during which customers were unable to access Snowsight and received "503 Service Unavailable" errors. The misconfiguration was identified, reverted, and affected infrastructure was restarted to restore service. Total incident duration, including monitoring, was approximately 2.2 hours.
Trusted by 1,000+ teams
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
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
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with