Provider
SnowflakeIncident detail
INC20000158
Resolved incidentCritical
Timeline window
to
Outage alerts
Get alerted the next time Snowflake breaks
Free email alerts for up to 5 providers. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.
Timeline
Incident updates
Every update Snowflake posted, oldest to newest, exactly as it appeared on their official status page.
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
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
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.
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.
Keep exploring
More from Snowflake
Neighboring incidents on Snowflake's timeline and the rest of their record on OutageDeck.