Skip to main content
Snowflake

INC20000263

Partial outage Lasted 1h 13m · started · Snowflake's page

Level
confirmed
Worst impact
Partial outage
Components
Applications, Applications, Applications
Regions
me
Down Index
32of 100

What to do

  • Check whether you use Snowflake Applications, Applications, Applications 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 1h 13m it lasted.

    Anything that failed between 2026-10-06 14:44 UTC and 2026-10-06 15:57 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: 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.

Category: BGP or network

Read the postmortem

Updates from Snowflake 4

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

    provider

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

    provider

  3. resolved

    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.

    provider

  4. postmortem

    [https://community.snowflake.com/s/article/INC20000263](https://community.snowflake.com/s/article/INC20000263)

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

Is Snowflake still down?

No, this incident was resolved 2026-10-06 15:57 UTC. For Snowflake's live state, see https://down.guide/snowflake.

How long did it last?

1h 13m, from 2026-10-06 14:44 UTC to 2026-10-06 15:57 UTC, by the times Snowflake posted.

What was affected?

Snowflake named Applications, Applications, Applications in me.

What caused it?

BGP or network. Snowflake wrote: "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." The postmortem: https://stspg.io/g31s73hgsznk

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.