INC0149526
Jan 8, 18:49 UTCJan 8, 20:22 UTC
Duration
1h 33m
Impact
Major
Root cause
Deployment
Snowflake, 90 days
22 incidents
Affected
ApplicationsAzure - West Europe (Netherlands) - ApplicationsAWS - Asia Pacific (Sydney) - ApplicationsAWS - Europe (Frankfurt) - ApplicationsAWS - Europe (Ireland) - ApplicationsAWS - Asia Pacific (Singapore) - ApplicationsAzure - Australia East (New South Wales) - ApplicationsAWS - Canada (Central) - ApplicationsAzure - Canada Central (Toronto) - ApplicationsAzure - Southeast Asia (Singapore) - ApplicationsAWS - US East (Ohio) - ApplicationsAWS - Asia Pacific (Tokyo) - ApplicationsAzure - West US 2 (Washington) - ApplicationsGCP - US Central 1 (Iowa) - Applications
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/INC0149526](https://community.snowflake.com/s/article/INC0149526)
Timeline
- Postmortem · Jan 15, 20:56 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/INC0149526](https://community.snowflake.com/s/article/INC0149526)
- Resolved · Jan 8, 20:22 UTC
Current status: We've confirmed after a period of monitoring that our reversal of the offending change has remediated the issue, and our service is healthy. Users with existing sessions that are still impacted should refresh their sessions to experience relief. If you experience additional issues or have questions, please open a support case via Snowflake Community. Customer experience: Customers hosted in the specified regions may have been unable to access or use Snowflake services and features using Snowsight. This specifically impacted users with existing sessions in Snowsight and not new sessions. Incident start time: 18:02 UTC January 08, 2026 Incident end time: 19:00 UTC January 08, 2026 Preliminary root cause: A change contained within the recent Snowsight release related to a network policy check caused issues with session deserialization, which resulted in errors for users with active sessions. A root cause analysis (RCA) document will be published within five business days.
- Monitoring · Jan 8, 19:22 UTC
Current status: Our investigation has identified that a change within the recent Snowsight release caused this issue and resulted in errors for users with existing sessions. We've reverted the offending change and we're continuing to monitor to ensure our service remains healthy. Users with existing sessions that are still impacted should refresh their sessions to experience relief. Customer experience: Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight. This is specifically impacting users with existing sessions in Snowsight and not new sessions. Incident start time: 18:02 UTC January 08, 2026 Incident end time: 19:00 UTC January 08, 2026 Preliminary root cause: A change contained within the recent Snowsight release related to a network policy check caused issues with session deserialization, which resulted in errors for users with active sessions.
- Investigating · Jan 8, 18:49 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 Snowflake services and features using Snowsight. This is specifically impacting users with existing sessions in Snowsight and not new sessions.
More from Snowflake
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 1404:48 UTC | INC20000217 | major | 1h 21m |
| Sep 1107:18 UTC | INC20000213 | critical | 6h 1m |
| Sep 921:53 UTC | INC20000211 | critical | 1h 58m |
| Sep 407:34 UTC | INC20000199 | critical | 2h 36m |
| Sep 109:58 UTC | INC20000190 | major | 3h 52m |
| Aug 3117:20 UTC | INC20000188 | critical | 2h 24m |
Also caused by deployment or rollout
All| Started | Vendor | Incident | Impact | Duration |
|---|---|---|---|---|
| Sep 1106:22 UTC | Issues with Workers VPC hostname route resolution on 2026-09-11 | none | 0m | |
| Aug 2014:43 UTC | Intermittent failures creating agent tasks | critical | 9h 54m | |
| Aug 2000:31 UTC | [Medium] Issue with Microsoft Office Integration and Box Edit | major | 1h 13m | |
| Aug 622:22 UTC | Trouble Using Search Bar For Some Admins | minor | 2h 44m | |
| Jul 2110:23 UTC | Job runs failing at the git clone step | critical | 2h 29m | |
| Jul 1907:33 UTC | Some EMEA customers experiencing Git clone failures (403 errors) on thier accounts | major | 6h 22m |
From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.