CheckUpstream does not yet run an independent probe against Snowflake, so no availability figure is published for it — only Snowflake's own disclosure record below. 21 incidents were recorded in the past 12 months; the most recent resolved earlier today after 3 hours. Status signals are polled from Snowflake's official Atlassian Statuspage status page, alongside independent probes and community reports.
Independent measurement how this is computed
Not measured
We run no independent probe against Snowflake yet, so we publish no availability figure for it. What follows is Snowflake's own disclosure record, which is a different thing.
Vendor disclosed: 21 incidents · 170 of 180 days with none posted · 1d 19h of declared impact
Fewer incidents in the last 30 days than 5% of 232 tracked services.
Share of each window with no impact declared by Snowflake
7d
79.583%
30d
94.214%
90d
97.973%
180d
98.987%
1y
99.500%
Downtime like this can be refundable
If you're a paying Snowflake customer, outages in these windows may count against Snowflake's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
Track your Snowflake entitlement →Does Snowflake actually matter to you?
A Snowflake outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →Predicted resolution
n=5~119m (p25 69m – p75 147m)
Based on 5 historical Minor incidents · currently 6148m elapsed.
From 20 incidents Snowflake published and resolved in the last 180 days, measured between their own start and resolution times. It describes how long Snowflake takes to close an incident they have acknowledged — not how often they have them, and not how available they were.
Excluded: 1 still open.
Live Snowflake status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/snowflake)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Snowflake is currently Degraded. CheckUpstream tracks Snowflake in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Looking for the live "is Snowflake down" view? See the Snowflake Live status page.
Aug 24, 16:22 UTC · resolved in 18m · Resolved
Aug 14, 15:19 UTC · resolved in 0m · Monitoring
Aug 5, 14:44 UTC · resolved in 10m · Resolved
Aug 5, 14:41 UTC · resolved in 1h 8m · Resolved
Aug 3, 14:11 UTC · resolved in 8m · Resolved
Aug 3, 14:11 UTC · resolved in 6h 49m · Resolved
Aug 3, 05:57 UTC · resolved in 3m · Resolved
Aug 3, 05:53 UTC · resolved in 2h 27m · Resolved
Jul 30, 03:00 UTC · resolved in 2h 1m · Resolved
Jul 25, 09:05 UTC · resolved in 7h 4m · Resolved
Jul 11, 17:41 UTC · resolved in 1h 58m · Resolved
Snowflake's last resolved incident started earlier today and lasted 2h 30m (a complete outage).
We don't publish one. CheckUpstream runs no independent probe against Snowflake yet, and the only other figure available would be derived from Snowflake's own incident posts — which measures how much a vendor discloses rather than how available it was. Vendors that post often score worse than vendors that stay quiet, so the number would be backwards.
Sign up to CheckUpstream and add Snowflake to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll Snowflake's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.