Skip to content
Snowflake · Data and observabilityAug 24, 2026, 16:22 UTC

INC20000173

MajorConfig changeUpdated 20h ago
Aug 24, 16:22 UTCAug 24, 18:03 UTC
Duration
1h 41m
Impact
Major
Root cause
Config change
Snowflake, 90 days
22 incidents
Affected
ApplicationsAWS - US West (Oregon) - Applications
Status page

Final update

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/INC20000173](https://community.snowflake.com/s/article/INC20000173)

Timeline

  1. Postmortem · Aug 31, 22:54 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/INC20000173](https://community.snowflake.com/s/article/INC20000173)
  2. Resolved · Aug 24, 18:03 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 have been unable to remain logged in to Snowsight, experiencing immediate logout after successful authentication. Incident start time: 14:47 UTC August 24, 2026 Incident end time: 17:21 UTC August 24, 2026 Preliminary root cause: A system configuration change caused an outdated application version to be deployed, resulting in authentication session failures. Once identified, the configuration was corrected to restore the proper application version. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.
  3. Monitoring · Aug 24, 17:37 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 remain logged in to Snowsight, experiencing immediate logout after successful authentication. Workaround: There were no available workarounds for this issue. Incident start time: 14:47 UTC August 24, 2026 Incident end time: 17:21 UTC August 24, 2026 Preliminary root cause: A system configuration change caused an outdated application version to be deployed, resulting in authentication session failures. Once identified, the configuration was corrected to restore the proper application version.
  4. Identified · Aug 24, 17:17 UTC
    Current status: We're in the process of implementing a fix for this issue. We'll provide an update within the next 60 minutes. Customer experience: Customers hosted in the specified region may be unable to remain logged in to Snowsight, experiencing immediate logout after successful authentication. An ETA is not yet available. We'll provide one as soon as possible. Workaround: There are no available workarounds for this issue. Incident start time: 15:00 UTC August 24, 2026
  5. Identified · Aug 24, 16:53 UTC
    Current status: We've identified an issue with a system configuration that is causing authentication problems in Snowsight, and we're developing and implementing a fix to restore service. We'll provide an update within 30 minutes. Customer experience: Customers hosted in the specified region may be unable to remain logged in to Snowsight, experiencing immediate logout after successful authentication. ETA: An ETA is not yet available. We'll provide one as soon as possible. Workaround: There are currently no available workarounds for this issue. Incident start time: 15:00 UTC August 24, 2026
  6. Investigating · Aug 24, 16:22 UTC
    Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 1 hour. Customer experience: Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight. Workaround: There are currently no available workarounds for this issue. Incident start time: 15:00 UTC August 24, 2026

More from Snowflake

Full history
StartedIncidentDuration
Sep 1404:48 UTCINC200002171h 21m
Sep 1107:18 UTCINC200002136h 1m
Sep 921:53 UTCINC200002111h 58m
Sep 407:34 UTCINC200001992h 36m
Sep 109:58 UTCINC200001903h 52m
Aug 3117:20 UTCINC200001882h 24m

Also caused by configuration change

All
StartedIncidentDuration
Sep 2218:20 UTCPhone Number APIs and Console Were Returning Incorrect 404 ResponsesTwilio0m
Sep 1622:30 UTCHyperdrive Elevated Origin Connection Failure RatesCloudflare0m
Sep 1211:04 UTCSome customers experiencing blurry image previews and download issuesSlack8h 56m
Sep 108:01 UTCSentry requests timing out / 504'sSentry3h 20m
Aug 2620:00 UTCFlag delivery errors in Streaming APILaunchDarkly0m
Aug 2407:19 UTCDegraded Git Operations over SSHGitHub0m

From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.

Weekly: the week's major outages, postmortems and breaches, Saturday mornings.