Snowflake reported this critical-impact incident on its official status page on Sep 11, 2026, 07:18 UTC. It was resolved after 6h 1m.
Right now Snowflake is degraded. Live Snowflake status →
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/INC20000213](https://community.snowflake.com/s/article/INC20000213)
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 regions may have been unable to sign in to Snowsight, and may have receive an error message such as "Something went wrong." This issue was intermittent and did not affect all users; affected users may also have experienced issues executing queries or managing data. Incident start time: 05:00 UTC September 11, 2026 Incident end time: 11:15 UTC September 11, 2026 Preliminary root cause: A configuration update to infrastructure components responsible for authorizing incoming network traffic caused the components to restrict this traffic. A root cause analysis (RCA) will be conducted and a summary will be made available within 5 business days.
Current status: We've identified additional impact in the AWS - Asia Pacific (Tokyo) region, in which we've applied the same fix for this issue. We'll continue to monitor the environment until we're confident all services are functioning properly. Customer experience: Customers hosted in the specified regions may have been unable to sign in to Snowsight, and may have receive an error message such as "Something went wrong." This issue was intermittent and did not affect all users; affected users may also have experienced issues executing queries or managing data. Incident start time: 05:00 UTC September 11, 2026 Incident end time: 11:15 UTC September 11, 2026 Preliminary root cause: A configuration update to infrastructure components responsible for authorizing incoming network traffic caused the components to restrict this traffic.
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 sign in to Snowsight, and may have receive an error message such as "Something went wrong." This issue was intermittent and did not affect all users; affected users may also have experienced issues executing queries or managing data. Incident start time: 05:00 UTC September 11, 2026 Incident end time: 08:45 UTC September 11, 2026 Preliminary root cause: A configuration update to infrastructure components responsible for authorizing incoming network traffic caused the components to restrict this traffic.
Current status: We've identified the source of the issue, and we're developing and implementing a fix to restore service. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified region may be unable to sign in to Snowsight, and may receive an error message such as "Something went wrong." This issue is intermittent and does not affect all users; affected users may also experience issues executing queries or managing data. ETA: An ETA is not yet available. We'll provide one as soon as possible. Incident start time: 05:00 UTC September 11, 2026
Current status: We're continuing to investigate the issue with Snowflake Data Cloud. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified region may be unable to sign in to Snowsight, and may receive an error message such as "Something went wrong." This issue is intermittent and does not affect all users; affected users may also experience issues executing queries or managing data. ETA: An ETA is not yet available. We'll provide one as soon as possible. Incident start time: 05:00 UTC September 11, 2026
Current status: We're continuing to investigate the issue with Snowflake Data Cloud. We'll provide another 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. Affected users may be unable to sign in, execute queries, or manage data. ETA: An ETA is not yet available. We'll provide one as soon as possible. Incident start time: 05:00 UTC September 11, 2026
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. Affected users may be unable to sign in, execute queries, or manage data. Incident start time: 05:00 UTC September 11, 2026
Overlapping incidents aren't necessarily related.
Snowflake reported 23 incidents in the last 90 days, 18 of them major or critical. A typical incident lasted 1h 56m. See Snowflake's uptime and incident history