Is Snowflake Down?

Current status: We've coordinated with our third-party provider who implemented a fix for this issue, and we've 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 seen pages that loaded indefinitely. Customers in other regions who connected from certain locations, including parts of the Middle East, may have seen an “Origin is unreachable” error. This depended on where the user was connecting from, not on which region the account was hosted in. Incident start time: 11:55 UTC October 06, 2026 Incident end time: 14:29 UTC October 06, 2026 Preliminary root cause: A network issue with a third-party edge network provider affected the routing of some Snowsight traffic between certain customer locations and the affected regions, resulting in pages that loaded indefinitely and connection errors. A root cause analysis (RCA) will be conducted and a summary will be made available within 10 business days. --- [2026-10-06T15:17:34.757Z] (monitoring) Current status: A third-party network provider reported that they are implementing a fix for the connectivity problems, and we have since observed signs of recovery in our health checks. We’ll continue to monitor the environment until we’re confident all services are functioning properly. We’ll provide another update within 1 hour. Customer experience: Customers hosted in the specified regions may have seen pages that loaded indefinitely. Customers in other regions who connected from certain locations, including parts of the Middle East, may have seen an “Origin is unreachable” error. This depended on where the user was connecting from, not on which region the account was hosted in. Incident start time: 11:55 UTC October 06, 2026 Incident end time: 14:29 UTC October 06, 2026 Preliminary root cause: A network issue with a third-party edge network provider affected the routing of some Snowsight traffic between certain customer locations and the affected regions, resulting in pages that loaded indefinitely and connection errors. --- [2026-10-06T14:44:36.196Z] (investigating) Current status: We're investigating an issue affecting user connections to Snowflake. We've narrowed our investigation to network connectivity between certain customer locations and the affected regions, and we've engaged third-party providers to assist. We're continuing to investigate the issue and will provide another update within 1 hour. Customer experience: Accounts hosted in Azure UAE North (azuaenorth) may see pages that load indefinitely. Customers in other deployments who connect from certain locations, including parts of the Middle East may see an “Origin is unreachable” error (Cloudflare error 523). This depends on where the user is connecting from, not on which region the account is hosted in. ETA: An ETA is not yet available. We'll provide one as soon as possible. because impact depends on where users connect from rather than where their account is hosted, we do not recommend failing over to another region, as it would not be expected to resolve the issue. Workaround: For customers affected by the "Origin is unreachable" error (Cloudflare error 523) when connecting from the Middle East or Israel, accessing Snowsight through a VPN that routes traffic through an exit location outside the affected area may restore access. Customers can also use programmatic access (drivers, connectors, SQL clients), which is not affected. Incident start time: 11:55 UTC October 06, 2026

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/INC20000239](https://community.snowflake.com/s/article/INC20000239) --- [2026-09-27T03:16:42.207Z] (resolved) Current status: We've coordinated with our third-party cloud platform to implement the fix for this issue, and we've 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 access or use multiple core Snowflake services and features. Affected users may have been unable to sign in, execute queries, or manage data. Incident start time: 00:25 UTC September 27, 2026 Incident end time: 01:00 UTC September 27, 2026 Preliminary root cause: An issue with our third-party cloud platform caused impact to multiple Snowflake services and features. We have engaged with our third-party for further details. A root cause analysis (RCA) will be conducted and a summary will be made available within 10 business days. --- [2026-09-27T02:15:52.009Z] (monitoring) Current status: We identified an issue with our third-party cloud platform that caused impact to Snowflake services. We've coordinated with our third-party cloud platform to implement 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. Incident start time: 00:25 UTC September 27, 2026 Incident end time: 01:00 UTC September 27, 2026 Preliminary root cause: An issue with our third-party cloud platform caused impact to multiple Snowflake services and features. We have engaged with our third-party for further details.

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) --- [2026-09-26T00:20:42.321Z] (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. --- [2026-09-25T23:26:33.719Z] (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. --- [2026-09-25T23:00:23.456Z] (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.