INC0153706

What to do

• Check whether you use Snowflake Alerts and Notifications, Alerts and Notifications, Alerts and Notifications, Alerts and Notifications and 27 more. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 7h 3m it lasted.

  Anything that failed between 2026-03-16 22:46 UTC and 2026-03-17 05:49 UTC may need a replay.

• Subscribe to Snowflake's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=snowflake works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Snowflake 4

1. investigatingMar 16, 2026, 10:46 PM UTC

   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

   provider

2. identifiedMar 16, 2026, 11:45 PM UTC

   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

   provider

3. monitoringMar 17, 2026, 4:58 AM UTC

   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.

   provider

4. resolvedMar 17, 2026, 5:49 AM UTC

   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. 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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.