Skip to content
Snowflake · Data and observabilityMar 16, 2026, 22:46 UTC

INC0153706

MinorNot disclosedUpdated 20h ago
Mar 16, 22:46 UTCMar 17, 05:49 UTC
Duration
7h 3m
Impact
Minor
Root cause
Not disclosed
Snowflake, 90 days
22 incidents
Affected
Alerts and NotificationsAWS - US West (Oregon) - Alerts and NotificationsAWS - US East (N. Virginia) - Alerts and NotificationsAzure - East US 2 (Virginia) - Alerts and NotificationsAWS - Asia Pacific (Singapore) - Alerts and NotificationsAzure - Australia East (New South Wales) - Alerts and NotificationsAzure - Canada Central (Toronto) - Alerts and NotificationsGCP - Europe West 4 (Eemshaven) - Alerts and NotificationsAWS - Asia Pacific (Mumbai) - Alerts and NotificationsAzure - Switzerland North (Zürich) - Alerts and NotificationsGCP - Europe West 2 (London) - Alerts and NotificationsAWS - Asia Pacific (Seoul) - Alerts and NotificationsAzure - Japan East (Tokyo, Saitama) - Alerts and NotificationsAWS - Europe (Stockholm) - Alerts and Notifications
Status page

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/INC0153706](https://community.snowflake.com/s/article/INC0153706)

Timeline

  1. Postmortem · Mar 24, 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. Resolved · Mar 17, 05:49 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.
  3. Monitoring · Mar 17, 04:58 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.
  4. Identified · Mar 16, 23:45 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
  5. Investigating · Mar 16, 22:46 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

More from Snowflake

Full history
StartedIncidentDuration
Sep 1404:48 UTCINC200002171h 21m
Sep 1107:18 UTCINC200002136h 1m
Sep 921:53 UTCINC200002111h 58m
Sep 407:34 UTCINC200001992h 36m
Sep 109:58 UTCINC200001903h 52m
Aug 3117:20 UTCINC200001882h 24m

From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.

Weekly: the week's major outages, postmortems and breaches, Saturday mornings.