- Level
- confirmed
- Worst impact
- Major outage
- Regions
- me
What to do
Check whether you use Snowflake in me. 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 75d 1h it lasted.
Anything that failed between 2026-03-01 13:33 UTC and 2026-05-15 15:10 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 12
- investigating
Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data.
provider
- identified
Current status: We've identified an issue with a third-party cloud platform, and we're coordinating with the provider to develop and implement a fix to restore service. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures.
provider
- identified
Current status: We're continuing to coordinate with our third-party cloud platform to develop and implement a fix to restore service. We'll provide another update within 4 hours. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. ETA: The third-party platform has advised that it may take multiple hours to resolve the issue. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Incident start time: 12:25 UTC March 01, 2026
provider
- identified
Current status: We're continuing to coordinate with our third-party cloud platform to develop and implement a fix to restore service. The provider has confirmed that the issue is due to a power disruption, and they expect full recovery to take multiple hours to complete. We'll provide another update within 6 hours. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. ETA: The third-party platform has advised that it may take multiple hours to resolve the issue. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Incident start time: 12:25 UTC March 01, 2026
provider
- identified
Current status: We continue to coordinate closely with our cloud provider as they work to resolve a major service disruption caused by a power outage at a primary data center. While we are seeing initial signs of recovery across several services, the provider expects full restoration to take multiple hours as they safely stabilize the environment. We'll provide another update within 6 hours. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. ETA: The third-party platform has advised that it may take multiple hours to resolve the issue. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Incident start time: 12:25 UTC March 01, 2026
provider
- identified
Current status: We continue to coordinate with our cloud provider following a power outage at a primary data center. While we have observed consistent signs of recovery in several key services, the provider is currently investigating a localized connectivity issues and elevated error rates within the region. Full restoration is expected to take several hours as they work to safely stabilize the environment. We will provide our next update within 6 hours. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. ETA: The third-party platform has advised that it may take multiple hours to resolve the issue. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Incident start time: 12:25 UTC March 01, 2026
provider
- identified
Current status: We continue to coordinate with our cloud provider following a power outage at a primary data center. Although we had observed early indicators of recovery, the provider has confirmed additional, ongoing impact that continues to cause elevated connectivity issues and error rates within the region. They continue to actively work on full restoration and environment stability but this is expected to take several hours. We will provide our next update within 6 hours. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. ETA: The third-party platform has advised that it may take multiple hours to resolve the issue. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Incident start time: 12:25 UTC March 01, 2026
provider
- identified
Current status: We're continuing to coordinate with our cloud service provider as they troubleshoot the impacting power outage at a primary data center. Elevated connectivity issues and error rates within the region will continue until the power issue has been resolved. While they're working to fully restore power and stabilize the environment, they now expect that this may take a day or more. We will provide our next update within 24 hours. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. ETA: The third-party platform has advised that it may take a day or more to resolve the issue. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Incident start time: 12:25 UTC March 01, 2026
provider
- identified
Current status: We're closely monitoring as coordination with our cloud service provider continues in an effort to restore service following the impacting power outage at a primary data center. They are prioritizing recovery for foundational services and pursuing multiple mitigation paths that do not depend on the underlying facilities being fully brought back online to provide some relief. However, full restoration will require that the underlying infrastructure be fully repaired, and this effort is ongoing. We're continuing to monitor for improvement, and we will provide our next update within 12 hours. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. ETA: An updated ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Affected customers should look for additional updates in their cloud service provider's personal health dashboard. Incident start time: 12:25 UTC March 01, 2026
provider
- identified
Current status: We continue to actively monitor the situation as we work with our cloud service provider to restore service following a power outage at a primary data center. Recovery efforts remain focused on foundational services, and multiple paths to restoration continue to be pursued. Work to restore the underlying infrastructure needed for full restoration is still in progress. Additionally, we've been informed that our cloud service provider will supplement their public service health updates with a targeted communications approach, delivered directly to customers through their personal health dashboards, for a more localized, relevant view of service health. We will provide our next update within 24 hours. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. ETA: An updated ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Affected customers should look for additional updates in their cloud service provider's personal health dashboard. Incident start time: 12:25 UTC March 01, 2026
provider
- identified
Current status: We continue to actively monitor the situation, and our cloud service provider affirms that meaningful progress is being made toward recovery, with several distinct services showing sustained improvement. While focused efforts continue toward full-service restoration for the region, the cloud service providers' initial advice to migrate your workloads and traffic to alternate Region(s) remains in place. We are in continuous contact with the provider and will post our next update once they confirm significant progress in restoring the site's physical environment, or when other material updates become available. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. ETA: An updated ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Affected customers should look for additional updates in their cloud service provider's personal health dashboard. Incident start time: 12:25 UTC March 01, 2026
provider
- resolved
To ensure the best possible service for our customers amid the persistent issues in the AWS Middle East (UAE) region and following the cloud service provider’s advice to transition workloads to other regions, we have decided to remove this region from our available listings until further notice.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-fd59ab2f46
Is Snowflake still down?
No, this incident was resolved 2026-05-15 15:10 UTC. For Snowflake's live state, see https://down.guide/snowflake.
How long did it last?
75d 1h, from 2026-03-01 13:33 UTC to 2026-05-15 15:10 UTC, by the times Snowflake posted.
What was affected?
Snowflake named in me.
What caused it?
Snowflake hasn't published a root cause. If it does, it shows here.
Where does this come from?
Snowflake's official status page, https://status.snowflake.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.