Skip to content
Snowflake · Data and observabilityJan 8, 2026, 18:49 UTC

INC0149526

MajorDeploymentUpdated 19h ago
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
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/INC0149526](https://community.snowflake.com/s/article/INC0149526)

Timeline

  1. 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)
  2. 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.
  3. 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.
  4. 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
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 deployment or rollout

All
StartedIncidentDuration
Sep 1106:22 UTCIssues with Workers VPC hostname route resolution on 2026-09-11Cloudflare0m
Aug 2014:43 UTCIntermittent failures creating agent tasksGitHub9h 54m
Aug 2000:31 UTC[Medium] Issue with Microsoft Office Integration and Box EditBox1h 13m
Aug 622:22 UTCTrouble Using Search Bar For Some AdminsSlack2h 44m
Jul 2110:23 UTCJob runs failing at the git clone stepdbt Labs2h 29m
Jul 1907:33 UTCSome EMEA customers experiencing Git clone failures (403 errors) on thier accountsdbt Labs6h 22m

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.