Is Snowflake down?
Snowflake is having issues
Right now
Partly. INC20000150.
Last checked (2026-10-10 07:16 UTC) from status.snowflake.com · every 180s
For agents
proceed
Proceed, expect slow or flaky responses.
GET upbutler.com/status/snowflake/status.agent.json
MCP: upstream_status {"service":"snowflake"}
Cloud data warehouse per cloud region, including Cortex AI.
What Snowflake says
Degraded· 1 open incident
Taken as is from Snowflake's own status page API. Incident titles and component names below are theirs.
Open status.snowflake.comWhat UpButler measured
There is no keyless endpoint of Snowflake that says anything useful, so UpButler does not probe it. To check your own Snowflake account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.
Open at Snowflake
- INC20000150identified · impact minor
Since · Virtual Warehouses, Snowpark Container Services
Current status: Since our last update, capacity availability and provisioning performance for virtual warehouses have materially improved. Additional capacity has become available in the region, and Snowflake has increased the resources reserved for customer workloads. We are continuing to monitor warehouse capacity and provisioning performance through periods of peak demand. Snowpark Container Services remains subject to capacity constraints. We continue to preserve available resources, coordi…
Text written by Snowflake, shown unchanged.
Which part of Snowflake?
Snowflake components
2 of 80 not operational
AWS - US East (N. Virginia)
- Databases, Tables, and ViewsOperational
- Virtual WarehousesOperational
Azure - East US 2 (Virginia)
- Databases, Tables, and ViewsOperational
Azure - West Europe (Netherlands)
- Databases, Tables, and ViewsOperational
AWS - Europe (Frankfurt)
- Databases, Tables, and ViewsOperational
- Virtual WarehousesOperational
AWS - Asia Pacific (Sydney)
- Databases, Tables, and ViewsOperational
- Virtual WarehousesOperational
AWS - US West (Oregon)
- Databases, Tables, and ViewsOperational
- Virtual WarehousesOperational
AWS - Europe (Ireland)
- Databases, Tables, and ViewsOperational
- Virtual WarehousesOperational
AWS - Asia Pacific (Singapore)
- Databases, Tables, and ViewsOperational
- Virtual WarehousesOperational
Azure - Australia East (New South Wales)
- Databases, Tables, and ViewsOperational
Azure - US Gov (Virginia)
- Databases, Tables, and ViewsOperational
AWS - Canada (Central)
- Databases, Tables, and ViewsOperational
- Virtual WarehousesOperational
Azure - Canada Central (Toronto)
- Databases, Tables, and ViewsOperational
Azure - UAE North (Dubai)
- Databases, Tables, and ViewsOperational
AWS - US East (Ohio)
- Databases, Tables, and ViewsOperational
- Virtual WarehousesOperational
AWS - Asia Pacific (Tokyo)
- Databases, Tables, and ViewsOperational
- Virtual WarehousesOperational
Azure - West US 2 (Washington)
- Databases, Tables, and ViewsOperational
- Virtual WarehousesOperational
GCP - US Central 1 (Iowa)
- Databases, Tables, and ViewsOperational
- Virtual WarehousesDegraded
- Snowpark Container ServicesDegraded
GCP - Europe West 4 (Eemshaven)
- Databases, Tables, and ViewsOperational
AWS - Asia Pacific (Mumbai)
- Databases, Tables, and ViewsOperational
- Virtual WarehousesOperational
Azure - Switzerland North (Zürich)
- Databases, Tables, and ViewsOperational
GCP - Europe West 2 (London)
- Databases, Tables, and ViewsOperational
AWS - Europe (London)
- Databases, Tables, and ViewsOperational
- Virtual WarehousesOperational
Azure - Central US (Iowa)
- Databases, Tables, and ViewsOperational
AWS - Asia Pacific (Seoul)
- Databases, Tables, and ViewsOperational
- Virtual WarehousesOperational
Azure - North Europe (Ireland)
- Databases, Tables, and ViewsOperational
AWS - GovCloud (US-West)
- Databases, Tables, and ViewsOperational
- Virtual WarehousesOperational
Azure - Japan East (Tokyo, Saitama)
- Databases, Tables, and ViewsOperational
AWS - Europe (Stockholm)
- Databases, Tables, and ViewsOperational
- Virtual WarehousesOperational
AWS - US East (Commercial Gov-Virginia)
- Databases, Tables, and ViewsOperational
- Virtual WarehousesOperational
Azure - Southeast Asia (Singapore)
- Databases, Tables, and ViewsOperational
Azure - South Central US (Texas)
- Databases, Tables, and ViewsOperational
- Virtual WarehousesOperational
Azure - Central India (Pune)
- Databases, Tables, and ViewsOperational
AWS - Asia Pacific (Osaka)
- Databases, Tables, and ViewsOperational
- Virtual WarehousesOperational
GCP - US East 4 (N. Virginia)
- Databases, Tables, and ViewsOperational
AWS - South America (São Paulo)
- Databases, Tables, and ViewsOperational
- Virtual WarehousesOperational
Azure - UK South (London)
- Databases, Tables, and ViewsOperational
AWS - Europe (Paris)
- Databases, Tables, and ViewsOperational
- Virtual WarehousesOperational
AWS - Asia Pacific (Jakarta)
- Databases, Tables, and ViewsOperational
- Virtual WarehousesOperational
AWS - Europe (Zürich)
- Databases, Tables, and ViewsOperational
- Virtual WarehousesOperational
AWS GovCloud - DoD
- Databases, Tables, and ViewsOperational
- Virtual WarehousesOperational
GCP - Europe West 3 (Frankfurt)
- Databases, Tables, and ViewsOperational
GCP - Middle East (Dammam)
- Databases, Tables, and ViewsOperational
Azure - Mexico (Central)
- Databases, Tables, and ViewsOperational
AWS - US West (Commercial Gov - Oregon)
- Databases, Tables, and ViewsOperational
- Virtual WarehousesOperational
Azure - Central Korea (Seoul)
- Databases, Tables, and ViewsOperational
AWS - Africa (Cape Town)
- Databases, Tables, and ViewsOperational
- Virtual WarehousesOperational
Azure - Sweden Central (Gävle)
- Databases, Tables, and ViewsOperational
GCP - Australia Southeast 2 (Melbourne)
- Databases, Tables, and ViewsOperational
Azure - East US (Virginia)
- Databases, Tables, and ViewsOperational
AWS - GovCloud (US-East)
- Databases, Tables, and ViewsOperational
AWS - Asia Pacific (Malaysia)
- Databases, Tables, and ViewsOperational
AWS - Asia Pacific (Thailand)
- Databases, Tables, and ViewsOperational
AWS - Asia Pacific (New Zealand)
- Databases, Tables, and ViewsOperational
Snowflake incidents, last 90 days
- 2026-07-13: no record
- 2026-07-14: no record
- 2026-07-15: no record
- 2026-07-16: no record
- 2026-07-17: no record
- 2026-07-18: no record
- 2026-07-19: no record
- 2026-07-20: no record
- 2026-07-21: no record
- 2026-07-22: no record
- 2026-07-23: no record
- 2026-07-24: no record
- 2026-07-25: no record
- 2026-07-26: no record
- 2026-07-27: no record
- 2026-07-28: no record
- 2026-07-29: no record
- 2026-07-30: no record
- 2026-07-31: no record
- 2026-08-01: no record
- 2026-08-02: no record
- 2026-08-03: no record
- 2026-08-04: no record
- 2026-08-05: no record
- 2026-08-06: no record
- 2026-08-07: no record
- 2026-08-08: no record
- 2026-08-09: no record
- 2026-08-10: no record
- 2026-08-11: no record
- 2026-08-12: no record
- 2026-08-13: no record
- 2026-08-14: no record
- 2026-08-15: no record
- 2026-08-16: no record
- 2026-08-17: no record
- 2026-08-18: no record
- 2026-08-19: no record
- 2026-08-20: no record
- 2026-08-21: no record
- 2026-08-22: no record
- 2026-08-23: no record
- 2026-08-24: no record
- 2026-08-25: no record
- 2026-08-26: no record
- 2026-08-27: no record
- 2026-08-28: minor incident
- 2026-08-29: minor incident
- 2026-08-30: minor incident
- 2026-08-31: minor incident
- 2026-09-01: minor incident
- 2026-09-02: minor incident
- 2026-09-03: minor incident
- 2026-09-04: minor incident
- 2026-09-05: minor incident
- 2026-09-06: minor incident
- 2026-09-07: minor incident
- 2026-09-08: minor incident
- 2026-09-09: minor incident
- 2026-09-10: minor incident
- 2026-09-11: minor incident
- 2026-09-12: minor incident
- 2026-09-13: minor incident
- 2026-09-14: minor incident
- 2026-09-15: minor incident
- 2026-09-16: minor incident
- 2026-09-17: minor incident
- 2026-09-18: minor incident
- 2026-09-19: minor incident
- 2026-09-20: minor incident
- 2026-09-21: minor incident
- 2026-09-22: minor incident
- 2026-09-23: minor incident
- 2026-09-24: minor incident
- 2026-09-25: minor incident
- 2026-09-26: minor incident
- 2026-09-27: critical incident
- 2026-09-28: minor incident
- 2026-09-29: minor incident
- 2026-09-30: minor incident
- 2026-10-01: minor incident
- 2026-10-02: minor incident
- 2026-10-03: minor incident
- 2026-10-04: minor incident
- 2026-10-05: minor incident
- 2026-10-06: major incident
- 2026-10-07: minor incident
- 2026-10-08: minor incident
- 2026-10-09: minor incident
- 2026-10-10: minor incident
Each bar is a day, coloured by the worst incident Snowflake reported. It is their incident record, not a measurement of uptime.
- Incidents
- 2
- 2 major or critical
- Typical time to resolve
- —
- median, needs 3 incidents
- Nine in ten within
- —
- 90th percentile
- Longest
- 1 h 13 min
- record since 2026-08-28
| Started (UTC) | Incident | Impact | Lasted |
|---|---|---|---|
| INC20000263 | major | 1 h 13 min | |
| INC20000239 | critical | 1 h 1 min |
Get alerted when Snowflake goes down
No account. One email when Snowflake reports an incident, one when it is over. You confirm the address first, and every email has a one-click unsubscribe.
Or follow the RSS feed. On UpButler? Add Snowflake as a dependency to route it to Slack, Teams or a webhook.
Status badge
Show Snowflake's current status in a README or an internal wiki. It updates by itself.
[](https://upbutler.com/status/snowflake)Tell your outage from Snowflake's
Declare that your project depends on Snowflake. When one of your monitors fails while Snowflake has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.
npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.
# upbutler.yaml
dependencies:
- snowflakecurl -s https://upbutler.com/status/snowflake/status.agent.json{
"schema": "upbutler.upstream-status/v1",
"service": "snowflake",
"verdict": "proceed",
"status": "degraded",
"reason": "INC20000150",
"retryAfterSec": null,
"incident": {
"title": "INC20000150",
"url": "https://status.snowflake.com/incidents/9p16kxkml7v2"
},
"probe": null
}Questions
- Is Snowflake down right now?
- Partly. As of 2026-10-10 07:16 UTC, Snowflake is having issues, with an open incident: "INC20000150". This page reads the status again every 3 minutes.
- Where does this status come from?
- From Snowflake's own status page API at https://status.snowflake.com. UpButler reads it once for everyone (not once per visitor) every 3 minutes with conditional requests, and shows it unchanged: incident titles and component names are Snowflake's words.
- Can I get an alert when Snowflake goes down?
- Yes, without an account: enter your email on this page, confirm the link we send, and you get one email when Snowflake reports an incident and one when it is over. There is also an RSS feed at https://upbutler.com/status/snowflake/feed.rss. Teams on UpButler can route the same alert to Slack, Teams or a webhook.
- How can my agent or app check Snowflake status?
- Fetch https://upbutler.com/status/snowflake/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"snowflake"}, on https://upbutler.com/mcp/public.
- How do I know whether an outage is mine or Snowflake's?
- Add "snowflake" to the dependencies of your UpButler workspace. When one of your monitors fails while Snowflake has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.
Also check
UpButler is not affiliated with Snowflake. Status and incident text belong to Snowflake and are read from their public status source; the probe result is UpButler's own measurement.