INC0153465
Mar 12, 19:42 UTCMar 12, 23:13 UTC
Duration
3h 31m
Impact
Major
Root cause
Not disclosed
Snowflake, 90 days
22 incidents
Affected
AI and MLAWS - US West (Oregon) - AI and MLAWS - US East (N. Virginia) - AI and MLAzure - East US 2 (Virginia) - AI and MLAzure - West Europe (Netherlands) - AI and MLAWS - Asia Pacific (Sydney) - AI and MLAWS - Europe (Frankfurt) - AI and MLAWS - Europe (Ireland) - AI and MLAWS - Asia Pacific (Singapore) - AI and MLAzure - Australia East (New South Wales) - AI and MLAWS - Canada (Central) - AI and MLAzure - Canada Central (Toronto) - AI and MLAzure - Southeast Asia (Singapore) - AI and MLAWS - US East (Ohio) - AI and ML
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/INC0153465](https://community.snowflake.com/s/article/INC0153465)
Timeline
- Postmortem · Mar 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)
- Resolved · Mar 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.
- Monitoring · Mar 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.
- Identified · Mar 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.
- Identified · Mar 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.
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 |
From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.