Snowflake experienced a 7.1-hour incident where customers in specified regions were unable to create or alter Snowflake alerts due to a code issue in a recent improvement to the alerts functionality. The issue was identified as stemming from faulty code in an alerts system update, and service was restored after implementing and rolling out a fix across the affected regions.
Current status: 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.
Customer experience: Customers hosted in the specified regions may have been unable to create or alter Snowflake alerts.
ETA: Our current estimate is that service will be restored within [2 hours]. In the meantime, we recommend that affected customers using replication initiate their failover procedures.
Incident start time: 14:53 UTC March 14, 2026
Incident end time: 04:39 UTC March 17, 2026
Preliminary root cause: 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.
Current status: 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.
Customer experience: Customers hosted in the specified regions may have been unable to create or alter Snowflake alerts.
Incident start time: 14:53 UTC March 14, 2026
Incident end time: 04:39 UTC March 17, 2026
Preliminary root cause: A recent improvement to Snowflake alerts creation and alteration contained a code issue.
Current status: 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.
Customer experience: Customers hosted in the specified regions may be unable to create or alter Snowflake alerts.
ETA: 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.
Workaround: There are currently no available workarounds for this issue.
Incident start time: 14:53 UTC March 14, 2026
Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes.
Customer experience: Customers hosted in the specified regions may be unable to create or alter Snowflake alerts.
Incident start time: 14:53 UTC March 14, 2026
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6020 services available
Integrations with