- Snowflake’s explanation remains preliminary.
What changed
Snowflake resolved incident INC20000217 on September 14 after affected customers experienced slow sign-ins and single sign-on loops. Its preliminary explanation links the failures to an update intended to improve authentication handling. Listed deployments span several Asia Pacific locations and Ohio across AWS and Azure.
Why it matters
The report gives operators a concrete incident to compare with their own login failures and scheduled workloads. It also illustrates an operational dependency: a service can become difficult to use when authentication fails, even without a reported storage failure.
What remains unproven
The final notice gives an earlier incident start than preceding updates. Snowflake promised a root-cause summary within five business days; the notice does not quantify affected customers or prove that every customer workload resumed successfully.
Read beyond this page.
Recorded source-check date: 15 Sep 2026. A link is not, by itself, evidence that every claim has been independently verified.
Changes & version history
Version 3 · 15 Sep 2026
Scheduled release of checksum-bound AI-assisted editorial review
Version 2 · 15 Sep 2026
Checksum-bound editorial review scheduled for release
Version 1 · 15 Sep 2026
Source-linked private review edition