Snowflake: INC0153465

Impact: majorStatus: postmortemStarted 2026-03-12 19:42 UTCResolved 2026-03-12 23:13 UTC (3.5 h)5 updatesSource: stspg.io

Summary

Snowflake reported a major outage affecting Snowflake Intelligence services and features across listed AWS, Azure and GCP regions, from 2026-03-12 19:42 UTC to 2026-03-12 23:13 UTC. Affected customers could be unable to use these services; Snowflake attributed the issue to a recent Snowflake Intelligence update and confirmed its rollback was complete at 03-12 21:50 UTC.

Machine-written from the archived incident (Sol). Check the timeline before relying on it.

Affected components: AI and MLGCP - US Central 1 (Iowa) - AI and MLAI and MLAWS - Asia Pacific (Singapore) - AI and MLAI and MLAzure - Central India (Pune) - AI and MLAI and MLAWS - Asia Pacific (Seoul) - AI and MLAI and MLAWS - Asia Pacific (Jakarta) - AI and MLAI and MLAzure - Southeast Asia (Singapore) - AI and MLAI and MLAzure - Central Korea (Seoul) - AI and MLAI and MLAWS - US West (Oregon) - AI and MLAWS - Middle East (UAE) - AI and MLAI and MLGCP - US East 4 (N. Virginia) - AI and MLAI and MLGCP - Europe West 2 (London) - AI and MLAI and MLAzure - West US 2 (Washington) - AI and MLAI and MLAWS - Europe (Ireland) - AI and MLAI and MLGCP - Europe West 3 (Frankfurt) - AI and MLAI and MLGCP - Middle East (Dammam) - AI and MLAI and MLAWS - Europe (Paris) - AI and MLAI and MLAWS - Europe (Frankfurt) - AI and MLAI and MLAzure - East US (Virginia) - AI and MLAI and MLAzure - East US 2 (Virginia) - AI and MLAI and MLAzure - UK South (London) - AI and MLAI and MLAWS - US East (N. Virginia) - AI and MLAI and MLAWS - Europe (Zürich) - AI and MLAI and MLAzure - South Central US (Texas) - AI and MLAI and MLAzure - North Europe (Ireland) - AI and MLAI and MLAzure - Sweden Central (Gävle) - AI and MLAI and MLAzure - Japan East (Tokyo, Saitama) - AI and MLAI and MLAWS - Europe (London) - AI and MLAI and MLAWS - Asia Pacific (Sydney) - AI and MLAI and MLAzure - UAE North (Dubai) - AI and MLAI and MLAzure - West Europe (Netherlands) - AI and MLAI and MLGCP - Europe West 4 (Eemshaven) - AI and MLAI and MLAzure - Australia East (New South Wales) - AI and MLAI and MLAWS - South America (São Paulo) - AI and MLAI and MLAzure - Mexico (Central) - AI and MLAI and MLAWS - Canada (Central) - AI and MLAI and MLAWS - Africa (Cape Town) - AI and MLAI and MLAzure - Switzerland North (Zürich) - AI and MLAI and MLAWS - Asia Pacific (Osaka) - AI and MLAI and MLAzure - Central US (Iowa) - AI and MLAI and MLAWS - US East (Ohio) - AI and MLAI and MLAWS - Asia Pacific (Mumbai) - AI and MLAI and MLAWS - Europe (Stockholm) - AI and MLAI and MLAzure - Canada Central (Toronto) - AI and MLAI and MLAWS - Asia Pacific (Tokyo) - AI and MLAI and MLGCP - Australia Southeast 2 (Melbourne) - AI and ML

Timeline of updates

identified2026-03-12 19:42 UTC
Current status: We're aware of an issue affecting the Snowflake Data Cloud, and we've identified the source as a recent Snowflake Intelligence update. We're rolling back the change to restore service. Customers should experience relief as the rollback progresses across the affected infrastructure. We'll provide another update within 2 hours. Customer experience: Customers hosted in the specified regions may be unable to use Snowflake Intelligence services and features. Additionally, users may experience issues with expired sessions attempting to access Snowflake Intelligence. Existing sessions should be unaffected. ETA: An ETA is not yet available. We'll provide one as soon as possible. Workaround: While we're focused on remediation, please access the service or content using the AI.Snowflake.com URL through a private browser tab.
identified2026-03-12 20:18 UTC
Current status: We're continuing to monitor as the rollback of the Snowflake Intelligence update progresses. Affected customers should continue to experience relief as the rollback advances and reaches their environment. We'll provide another update within 4 hours. Customer experience: Customers hosted in the specified regions may be unable to use Snowflake Intelligence services and features. Additionally, users may experience issues with expired sessions attempting to access Snowflake Intelligence. Existing sessions should be unaffected. ETA: Our current estimate is that service will be restored within approximately 4 hours. We're continuing to monitor the rollback's progress to ensure this timeline remains accurate. Workaround: While we're focused on remediation, users may be able to work around the issue by accessing the service directly via the non-account-specific URL, AI.Snowflake.com, in a private browser tab.
monitoring2026-03-12 21:50 UTC
Current status: We've confirmed that the rollback of the impacting Snowflake Intelligence update has completed, and 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 use Snowflake Intelligence services and features. Additionally, users may have experienced issues with expired sessions attempting to access Snowflake Intelligence. Existing sessions should have been unaffected. Workaround: While we were focused on remediation, users may have been able to work around the issue by accessing the service directly via the non-account-specific URL, AI.Snowflake.com, in a private browser tab. Incident start time: 16:30 UTC March 12, 2026 Incident end time: 20:39 UTC March 12, 2026 Preliminary root cause: An update intended to optimize Snowflake Intelligence introduced a code issue that caused problems with expired sessions attempting to access Snowflake Intelligence.
resolved2026-03-12 23:13 UTC
Current status: We've confirmed that the rollback of the impacting Snowflake Intelligence update has completed, and 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 use Snowflake Intelligence services and features. Additionally, users may have experienced issues with expired sessions attempting to access Snowflake Intelligence. Existing sessions should have been unaffected. Workaround: While we were focused on remediation, users may have been able to work around the issue by accessing the service directly via the non-account-specific URL, AI.Snowflake.com, in a private browser tab. Incident start time: 16:30 UTC March 12, 2026 Incident end time: 20:39 UTC March 12, 2026 Preliminary root cause: An update intended to optimize Snowflake Intelligence introduced a code issue that caused problems with expired sessions attempting to access Snowflake Intelligence.
postmortem2026-03-19 21:24 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/INC0153465](https://community.snowflake.com/s/article/INC0153465)

Rewindex changes for this incident

Major incident: INC0153465 2026-03-12 19:42 UTC

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Snowflake profile · Recent Snowflake incidents · Markdown · JSON