INC20000158

What to do

• Check whether you use Snowflake Applications. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 2h 6m it lasted.

  Anything that failed between 2026-08-14 17:29 UTC and 2026-08-14 19:35 UTC may need a replay.

• Subscribe to Snowflake's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=snowflake works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Snowflake 5

1. investigatingAug 14, 2026, 5:29 PM UTC

   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

   provider

2. identifiedAug 14, 2026, 5:58 PM UTC

   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

   provider

3. monitoringAug 14, 2026, 6:30 PM UTC

   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.

   provider

4. resolvedAug 14, 2026, 7:35 PM UTC

   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.

   provider

5. postmortemAug 21, 2026, 9:47 PM UTC

   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)

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.