Skip to content

Outage tracker

Snowflake: incident history

The last 24 hours in detail, Snowflake's declared incident record, and our regional check results beside it.

← Back to Snowflake's check readings

We started checking Snowflake on August 20, 2026, which is 80 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.

Email me when Snowflake reports an incident on its status page, and again when it reports it resolved.

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

This is Snowflake's own statement from its status page, with our regional reading beside it.

The last 24 hours

What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Snowflake's own status page declared. Below it, any public chatter we saw about Snowflake and the extra probe it triggered.

The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Snowflake's own status page declared. Three records side by side; none of them changes another.

Our probes, web (primary)
Our probes, community
Our probes, documentation
Our probes, marketplace
Unverified user reportsNo reports about Snowflake in the last 24 hours, which is not evidence that nothing is wrong.
Snowflake's status page
  1. INC20000150: minor incident, from before this window to now, still open per their page.
  2. INC20000336: minor incident, from 23:30 UTC to 03:00 UTC.
  3. INC20000337: minor incident, from 02:30 UTC to 04:45 UTC.

Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Snowflake's own declaration, shown as they made it.

Third-party chatter, labeled

Public posts from the last hour that mention Snowflake next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.

No matching public posts in the last hour from the sources we watch.

  • Confirmation probe03:01 UTC, Asia-Pacific: a new incident on their status page prompted an extra probe. Result: Snowflake answered normally.
  • Confirmation probe03:00 UTC, Europe: a new incident on their status page prompted an extra probe. Result: Snowflake answered normally.
  • Confirmation probe02:59 UTC, US-Central: a new incident on their status page prompted an extra probe. Result: Snowflake answered normally.
  • Confirmation probe02:59 UTC, US-West: a new incident on their status page prompted an extra probe. Result: Snowflake answered normally.
  • Confirmation probe02:59 UTC, South America: a new incident on their status page prompted an extra probe. Result: Snowflake answered normally.

Checks passing by region

Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.

RegionChecks passingProbes recorded
US-East100.00%3785
US-West99.97%3740
Europe100.00%3720
Asia-Pacific99.89%3630
US-Central100.00%1591
Canada100.00%1590
UK99.94%1590
Southeast Asia99.69%1588
Australia98.36%1589
South America96.93%1595

Their declared record

Snowflake's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.

INC20000337Minor incident
Nov 7, 2026, 2:38 AM UTC to Nov 7, 2026, 4:44 AM UTC (2h 5m)resolved
their latest update (Nov 7, 2026, 4:44 AM UTC): Current status: Our third-party cloud platform provider resolved the issue, and we've monitored the environment to confirm that service has been restored. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page…
INC20000336Minor incident
Nov 6, 2026, 11:32 PM UTC to Nov 7, 2026, 2:52 AM UTC (3h 20m)resolved
their latest update (Nov 7, 2026, 2:52 AM UTC): 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 Com…
INC20000321Minor incident
Oct 30, 2026, 8:38 PM UTC to Oct 31, 2026, 12:04 AM UTC (3h 26m)resolved
their latest update (Oct 31, 2026, 12:04 AM UTC): Current status: We've implemented the fix for this issue and 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 exper…
INC20000319Minor incident
Oct 29, 2026, 4:29 AM UTC to Oct 30, 2026, 1:57 AM UTC (21h 28m)resolved
their latest update (Oct 30, 2026, 1:57 AM UTC): 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 Com…
INC20000301Major outage
Oct 21, 2026, 6:26 PM UTC to Oct 21, 2026, 11:29 PM UTC (5h 3m)postmortem published
their latest update (Oct 28, 2026, 9:13 PM UTC): 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/INC20000301](https://community.snowflake.com/s/article/INC20000301)
INC20000299Minor incident
Oct 21, 2026, 7:45 AM UTC to Oct 21, 2026, 8:36 AM UTC (51 min)postmortem published
their latest update (Oct 28, 2026, 1:47 PM UTC): 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/INC20000299](https://community.snowflake.com/s/article/INC20000299)
INC20000294Major outage
Oct 20, 2026, 6:34 AM UTC to Oct 20, 2026, 3:26 PM UTC (8h 52m)postmortem published
their latest update (Nov 3, 2026, 4:23 PM UTC): 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/INC20000294](https://community.snowflake.com/s/article/INC20000294)
INC20000290Minor incident
Oct 19, 2026, 12:26 AM UTC to Oct 19, 2026, 1:11 AM UTC (44 min)resolved
their latest update (Oct 19, 2026, 1:11 AM UTC): Current status: We've monitored the environment and confirmed that service has been 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 …
INC20000287Major outage
Oct 16, 2026, 1:14 AM UTC to Oct 16, 2026, 1:43 AM UTC (29 min)postmortem published
their latest update (Oct 23, 2026, 4:47 PM UTC): [https://community.snowflake.com/s/article/INC20000287](https://community.snowflake.com/s/article/INC20000287)
INC20000277Minor incident
Oct 14, 2026, 9:47 PM UTC to Oct 15, 2026, 9:51 PM UTC (1d 0h)postmortem published
their latest update (Oct 23, 2026, 8:17 PM UTC): 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/INC20000277](https://community.snowflake.com/s/article/INC20000277)

Showing the 10 most recent of 73 incidents Snowflake has declared in the history we hold.

These entries are Snowflake's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.

Snowflake's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.

Full detail on what a probe does and does not prove is in the methodology page.