Is Snowflake down?
Vendor reports an incidentWhat Snowflake reports
Snowflake reports an incident on its status page: INC20000277.
Impact: minor. Since 2026-10-13 15:53 UTC.
Latest update, 2026-10-14 03:19 UTC: Current status: We've modified our remediation approach. After further investigation, we've determined that restarting infrastructure in the affected region is the most effective way to restore normal task execution. The infrastructure restart effort is in progress, and we've observed a decrease in task failure rates on infrastructure that has been restarted. We're monitoring to confirm normal task execution is fully restored across all the infrastructure. As a side effect of the restarts, task graph run history from before the incident start time (10:58 UTC October 13, 2026) may currently be unavailable, and history from after that time may be incomplete. We're investigating options to restore this history and we'll provide another update by 22:00 UTC on October 14. Customer experience: Prior to the mitigation: Customers hosted in the affected region may have experienced intermittent issues with scheduled or manual tasks. Most tasks completed as expected, but some may have been marked as failed even though they ran successfully. A small number of tasks may have remained in a pending state or failed to start. Affected users may have seen an error message, such as "Unexpected exception during task dispatch." After the mitigation: The next time each task runs, it may still be marked as failed with an internal error message even though its query ran successfully. This may happen up to one additional time per task. Customers may also see incomplete task graph run history. Specifically: - When customers open or refresh the Task Graphs tab on the Tasks page in Snowsight (Transformation » Tasks), or the Run History tab for individual tasks, they may not see task runs from before 10:58 UTC October 13, 2026. Some task runs from after that time may not appear. - The INFORMATION_SCHEMA.COMPLETE_TASK_GRAPHS function may not include some recently completed runs. - The INFORMATION_SCHEMA.CURRENT_TASK_GRAPHS function may show extra rows for previously scheduled runs that are no longer running. - The SNOWFLAKE.ACCOUNT_USAGE.COMPLETE_TASK_GRAPHS view will continue to show history from before 10:58 UTC October 13, 2026, but some runs after that time may not appear. ETA: An ETA is not yet available. We'll provide one as soon as possible. Workaround: Before rerunning a task that was reported as failed, we recommend using the QUERY_HISTORY function or the SNOWFLAKE.ACCOUNT_USAGE.QUERY_HISTORY view to confirm whether the queries run by the task actually succeeded or failed. Incident start time: 10:58 UTC October 13, 2026 Preliminary root cause: A subset of infrastructure in the region experienced an issue that left the task metadata inconsistent. As a result, some tasks were reported as failed even though they completed successfully, while others remained pending or failed to start.
Our regional reading
This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.
Checks passingchecked 9 minutes ago
Our checks of Snowflake pass from all 10 regions we check.
As of Oct 14, 2026, 1:11 PM UTC, RealUptime's checks of Snowflake passed in all 10 regions that returned a reading.
Snowflake reports: Minor incident (“Partially Degraded Service”)
Snowflake reports an active incident: INC20000277 (minor incident, since Oct 13, 2026, 3:53 PM UTC)
Snowflake's own component breakdown, as they publish it (our last read of their page failed, so this is the previous reading)
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Databases, Tables, and ViewsOperational
- Virtual WarehousesOperational
- Virtual WarehousesOperational
- Virtual WarehousesOperational
- Virtual WarehousesOperational
- Virtual WarehousesOperational
- Virtual WarehousesOperational
- Virtual WarehousesOperational
- Virtual WarehousesOperational
- Virtual WarehousesOperational
- Virtual WarehousesOperational
- Virtual WarehousesOperational
- Virtual WarehousesOperational
- Virtual WarehousesOperational
- Virtual WarehousesDegraded performance
- Virtual WarehousesOperational
- Virtual WarehousesOperational
- Virtual WarehousesOperational
- Virtual WarehousesOperational
- Virtual WarehousesOperational
- Virtual WarehousesOperational
- Virtual WarehousesOperational
- Virtual WarehousesOperational
- Virtual WarehousesOperational
- Virtual WarehousesOperational
- Virtual WarehousesOperational
- Virtual WarehousesOperational
- Virtual WarehousesOperational
- Virtual WarehousesOperational
- Virtual WarehousesOperational
- Virtual WarehousesOperational
- Virtual WarehousesOperational
- Virtual WarehousesOperational
- Virtual WarehousesOperational
- Virtual WarehousesOperational
- Virtual WarehousesOperational
- Virtual WarehousesOperational
- Virtual WarehousesOperational
- Virtual WarehousesOperational
- Virtual WarehousesOperational
- Virtual WarehousesOperational
- Virtual WarehousesOperational
- Virtual WarehousesOperational
- Virtual WarehousesOperational
- Virtual WarehousesOperational
- Virtual WarehousesOperational
- Virtual WarehousesOperational
- Virtual WarehousesOperational
These are Snowflake's components, named and scored by Snowflake. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.
This is Snowflake's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.
Snowflake response time, by region
Check your own site while you wait on Snowflake
Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Snowflake. It cannot diagnose Snowflake's own systems.
Email me when Snowflake reports an incident on its status page, and again when it reports it resolved.
Get an email when Snowflake reports an incident
Email me when Snowflake reports an incident on its status page, and again when it reports it resolved. No account, no card.
What our checks show, and what people reported
- North AmericaChecks passingUS-East, US-West, US-Central, Canada
- US-EastChecks passinglatency: 68msstatus code: 200checked: Oct 14, 2026, 1:05 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Snowflake normally. We do not have enough reports from US-East to say anything about what people there are seeing.
- US-WestChecks passinglatency: 204msstatus code: 200checked: Oct 14, 2026, 1:05 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Snowflake normally. We do not have enough reports from US-West to say anything about what people there are seeing.
- US-CentralChecks passinglatency: 67msstatus code: 200checked: Oct 14, 2026, 1:03 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Snowflake normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
- CanadaChecks passinglatency: 71msstatus code: 200checked: Oct 14, 2026, 1:04 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Snowflake normally. We do not have enough reports from Canada to say anything about what people there are seeing.
- South AmericaChecks passinglatency: 98msstatus code: 200checked: Oct 14, 2026, 1:05 PM UTC0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Snowflake normally. We do not have enough reports from South America to say anything about what people there are seeing.
- EuropeChecks passingEurope, UK
- EuropeChecks passinglatency: 199msstatus code: 200checked: Oct 14, 2026, 1:11 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Snowflake normally. We do not have enough reports from Europe to say anything about what people there are seeing.
- UKChecks passinglatency: 113msstatus code: 200checked: Oct 14, 2026, 1:05 PM UTC0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Snowflake normally. We do not have enough reports from UK to say anything about what people there are seeing.
- Asia PacificChecks passingAsia-Pacific, Southeast Asia, Australia
- Asia-PacificChecks passinglatency: 276msstatus code: 200checked: Oct 14, 2026, 1:05 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Snowflake normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
- Southeast AsiaChecks passinglatency: 512msstatus code: 200checked: Oct 14, 2026, 1:06 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Snowflake normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
- AustraliaChecks passinglatency: 340msstatus code: 200checked: Oct 14, 2026, 1:07 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Snowflake normally. We do not have enough reports from Australia to say anything about what people there are seeing.
Somewhere else or not sure: 0 people in the last 5 minutes
These are unverified reports from people using Snowflake, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Snowflake yet, which is not evidence that nothing is wrong.
Recent probe events
check entries are our own probes' readings; declared entries are the vendor's. How this check works
We have been measuring Snowflake since August 20, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.
Need this in writing? Generate an SLA evidence report for Snowflake covering any window you pick, with our check readings and Snowflake's own claim at the time, side by side.
Full check history for Snowflake: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.
Monitor your own site the same way
This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.
Start monitoring your own serversPut this badge in your README
Live, from this page's own readings.[](https://realuptime.io/outages/snowflake)<a href="https://realuptime.io/outages/snowflake"><img src="https://realuptime.io/outages/snowflake/badge.svg?days=30" alt="Snowflake uptime by RealUptime's checks"></a>The badge shows the share of our checks that passed over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.
To cite this page: RealUptime, "Is Snowflake down?", https://realuptime.io/outages/snowflake. The readings change with every check, so give the date you read them.
Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.
What we check
What our check can and cannot see
A pass means the service's public web page loaded and answered normally. It does not show that the product, the API or sign-in behind it works; a page can load from a cache while the product is down.
Host checked: app.snowflake.com