- Level
- confirmed
- Worst impact
- Major outage
- Components
- Databases, Tables, and Views, Virtual Warehouses, Data Loading and Unloading, Applications, Security and Privacy Features
- Down Index
- 40of 100
What to do
Check whether you use Snowflake Databases, Tables, and Views, Virtual Warehouses, Data Loading and Unloading, Applications and 1 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 1h 20m it lasted.
Anything that failed between 2026-09-25 23:00 UTC and 2026-09-26 00:20 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.
Root cause
Preliminary root cause: Our internal metadata database infrastructure in the affected region became unavailable, resulting in connectivity failures across multiple Snowflake services.Read the postmortem
Updates from Snowflake 4
- 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, and may be unable to connect to Snowflake via private connectivity, such as AWS PrivateLink. Additionally, they may be unable to continuously stream data into Snowflake using Snowpipe Streaming.
provider
- monitoring
Current status: We've implemented the fix for this issue, and 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 access or use multiple core Snowflake services and features. Affected users may have been unable to sign in, execute queries, or manage data, and may have been unable to connect to Snowflake via private connectivity, such as AWS PrivateLink. Additionally, they may have been unable to continuously stream data into Snowflake using Snowpipe Streaming. Incident start time: 22:35 UTC September 25, 2026 Incident end time: 22:59 UTC September 25, 2026 Preliminary root cause: Our internal metadata database infrastructure in the affected region became unavailable, resulting in connectivity failures across multiple Snowflake services.
provider
- resolved
Current status: We've implemented the fix for this issue and monitored the environment to confirm that service was restored. Most impact was resolved by 22:59 UTC, with the remaining backlog for scheduled and serverless task execution fully clearing by 23:43 UTC. 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 access or use multiple core Snowflake services and features. Affected users may have been unable to sign in, execute queries, or manage data, and may have been unable to connect to Snowflake via private connectivity, such as AWS PrivateLink. Additionally, they may have been unable to continuously stream data into Snowflake using Snowpipe Streaming, and customers using scheduled or serverless tasks may have experienced delayed task execution. Incident start time: 22:35 UTC September 25, 2026 Incident end time: 23:43 UTC September 25, 2026 Preliminary root cause: Our internal metadata database infrastructure in the affected region became unavailable, resulting in connectivity failures across multiple Snowflake services. A root cause analysis (RCA) will be conducted and a summary will be made available within 5 business days.
provider
- postmortem
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/INC20000237](https://community.snowflake.com/s/article/INC20000237)
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-281ed016a0
Is Snowflake still down?
No, this incident was resolved 2026-09-26 00:20 UTC. For Snowflake's live state, see https://down.guide/snowflake.
How long did it last?
1h 20m, from 2026-09-25 23:00 UTC to 2026-09-26 00:20 UTC, by the times Snowflake posted.
What was affected?
Snowflake named Databases, Tables, and Views, Virtual Warehouses, Data Loading and Unloading, Applications and 1 more.
What caused it?
Snowflake wrote: "Preliminary root cause: Our internal metadata database infrastructure in the affected region became unavailable, resulting in connectivity failures across multiple Snowflake services." The postmortem: https://stspg.io/sypcknfz85w6
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.