INC20000369
Snowflake reports an outage that affects databases, data loading, applications, Snowpark Container Services, and security features in the GCP Middle East (Dammam) region. Snowflake reports that the outage is resolved. The impact lasted from 05:28 UTC to 10:40 UTC on November 21, 2026, about 5 hours and 12 minutes.
State
Resolved
Started
Lasted
5 h 19 min
Worst impact
Major outage
Timeline
6 updatesInvestigating
2 h 17 min 43%
Identified
2 h 38%
Monitoring
1 h 2 min 19%
Updates
Times in UTCAs posted by Snowflake
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 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. Impact start time: 05:28 UTC November 21, 2026 Impact end time: 10:40 UTC November 21, 2026 Preliminary root cause: Our third-party cloud platform provider experienced an issue during a configuration rollout. A root cause analysis (RCA) will be conducted and a summary will be made available within 10 business days.
Current status: 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 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. Impact start time: 05:28 UTC November 21, 2026 Impact end time: 10:40 UTC November 21, 2026 Preliminary root cause: Our third-party cloud platform provider experienced an issue during a configuration rollout.
Current status: We're continuing to coordinate with our third-party cloud platform to develop and implement a fix to restore service. The ETA for restoration has been extended. We'll provide another update within 1 hour. 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: Our current estimate is that service will be restored within 2 hours. Impact start time: 05:28 UTC November 21, 2026
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 1 hour. 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: Our current estimate is that service will be restored within 2 hours. Impact start time: 05:28 UTC November 21, 2026
Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within two hours. Customer experience: Customers hosted in the specified region may experience intermittent failures when signing in to Snowflake, including when using OAuth or signing in to Snowsight. Impact start time: 05:28 UTC November 21, 2026
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 region may experience intermittent failures when signing in to Snowflake, including when using OAuth or signing in to Snowsight. Impact start time: 05:33 UTC November 21, 2026
Affected components
10Snowflake in the last 90 days
Full historyIncidents in 90 days
27
Days with an incident
82
Median duration
2 h 5 min
This incident
2.5× the median
Other Snowflake incidents
All incidentsSnowflake·INC20000351
Snowflake Virtual Warehouses in AWS Europe (Ireland) had intermittent delays in virtual warehouse resume operations, which caused queued or delayed queries. Snowflake implemented a fix and monitored the environment. Snowflake reports that this incident is resolved. The impact lasted about 7 hours.
Snowflake·INC20000350
Snowflake Data Loading and Unloading tasks in AWS US West (Oregon) had delays. Snowflake reports that this incident is resolved. It lasted 42 minutes.
Snowflake·INC20000347
Snowflake reported degraded performance for Databases, Tables, and Views in Azure Australia East (New South Wales). Customers in that region had delays when resuming virtual warehouses, and queries took longer than usual. Snowflake resolved the incident; the impact lasted 72 minutes.
Snowflake·INC20000337
Snowflake reports degraded service for Virtual Warehouses and Snowpark Container Services in Azure West US 2 (Washington). Customers had delays when resuming or scaling up warehouses, and intermittent delays when creating or scaling up Snowpark Container Services compute pools. The incident is resolved and it lasted 84 minutes.
Snowflake·INC20000336
Snowflake reports degraded Virtual Warehouses and Snowpark Container Services in AWS US West (Oregon) and AWS US West Commercial Gov (Oregon). Snowflake resolved the incident. The impact lasted from 22:50 UTC on November 06, 2026 to 00:31 UTC on November 07, 2026.
Follow Snowflake
Your coding agent knows when Snowflake is down, and tells you when a failure is theirs, not yours. You can also get Snowflake incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "snowflake" and tell me if Snowflake has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=snowflake/feed subscribe https://outages.live/feed.xml?providers=snowflakeFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane