What visitors reported during this incident
No visitor reports were filed for this incident.
Having problems with Snowflake now? Check the current statusAffected services
Updates (5)
- Aug 21, 2026, 09:47 PMINC20000158
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)
Snowflake ↗ - Aug 14, 2026, 07:35 PMINC20000158
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 perf
Snowflake ↗ - Aug 14, 2026, 06:30 PMINC20000158
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. On
Snowflake ↗ - Aug 14, 2026, 05:58 PMINC20000158
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
Snowflake ↗ - Aug 14, 2026, 05:29 PMINC20000158
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 ↗
What to do next
- Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
- Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
- Watch the provider going forward. Follow Snowflake's status feed →
GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.