Snowflake incident: INC0153706

Affected components

• Alerts and Notifications

1. postmortemMar 24, 2026, 23:55 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/INC0153706](https://community.snowflake.com/s/article/INC0153706)

2. resolvedMar 17, 2026, 05:49 UTC

   <b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may have been unable to create or alter Snowflake alerts. <b>Incident start time:</b> 14:53 UTC March 14, 2026 <b>Incident end time:</b> 04:39 UTC March 17, 2026 <b>Preliminary root cause:</b> A recent improvement to Snowflake alerts creation and alteration contained a code issue. A root cause analysis (RCA) document will be published within five business days.

3. monitoringMar 17, 2026, 04:58 UTC

   <b>Current status:</b> We've finished rolling out the fix to restore service. We'll continue to monitor the environment until we're confident all services are functioning properly. <b>Customer experience:</b> Customers hosted in the specified regions may have been unable to create or alter Snowflake alerts. <b>Incident start time:</b> 14:53 UTC March 14, 2026 <b>Incident end time:</b> 04:39 UTC March 17, 2026 <b>Preliminary root cause:</b> A recent improvement to Snowflake alerts creation and alteration contained a code issue.

4. identifiedMar 16, 2026, 23:45 UTC

   <b>Current status:</b> We've determined a recent improvement to Snowflake alerts creation and alteration contains a code issue, which is causing the impact. We've developed a fix and are rolling it out to restore service. We'll provide another update within 6 hours. <b>Customer experience:</b> Customers hosted in the specified regions may be unable to create or alter Snowflake alerts. <b>ETA:</b> Our current estimate is that service will be restored for all affected customers within 6 hours. Customers will see relief as the fix rolls out. In the meantime, affected customers using replication in an unaffected region may initiate their failover procedures as a way to bypass the issue. <b>Workaround:</b> There are currently no available workarounds for this issue. <b>Incident start time:</b> 14:53 UTC March 14, 2026

5. investigatingMar 16, 2026, 22:46 UTC

   <b>Current status:</b> We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. <b>Customer experience:</b> Customers hosted in the specified regions may be unable to create or alter Snowflake alerts. <b>Incident start time:</b> 14:53 UTC March 14, 2026

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Snowflake's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

How often does Snowflake have incidents?

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