Snowflake Outage History

59 incidents recorded over the last 365 days, 58 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Snowflake status96.13% uptime history

Every Recorded Snowflake Incident

Snowflake incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Aug 20, 2026INC20000168Current status: The third-party cloud platform confirmed that the mitigation was complete, and its automated recovery system appears to have initiated. We independently monitored the environment and verified that…1h 56mResolved
Aug 18, 2026INC20000163Current 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…1h 53mResolved
Aug 14, 2026INC20000158Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…2h 5mResolved
Aug 14, 2026INC20000157Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…1h 8mResolved
Aug 5, 2026INC20000139Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…1h 8mResolved
Aug 3, 2026INC20000129Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…6h 47mResolved
Aug 3, 2026INC20000128Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…2h 22mResolved
Jul 30, 2026INC20000115Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…1h 56mResolved
Jul 25, 2026INC20000106Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…6h 55mResolved
Jul 11, 2026INC20000085Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…1h 55mResolved
Jul 10, 2026INC20000082Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…1h 57mResolved
Jun 30, 2026INC20000063Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…1h 0mResolved
Jun 24, 2026INC20000052Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…1h 44mResolved
Jun 23, 2026INC20000047Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…14h 29mResolved
Jun 23, 2026INC20000046Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…1h 29mResolved
Jun 22, 2026AWS - US West (Oregon): INC0159680Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…3h 51mResolved
Jun 16, 2026INC0159144Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…9h 51mResolved
Jun 15, 2026INC20000034Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…30h 44mResolved
Jun 12, 2026INC20000033Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…2h 35mResolved
Jun 11, 2026INC20000032Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…0 minResolved
Jun 8, 2026INC20000030Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…1h 16mResolved
May 29, 2026Azure - West US 2 (Washington): INC0157956Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…15h 41mResolved
May 15, 2026INC0157230Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…1h 23mResolved
May 13, 2026INC0157155<b>Current status:</b> After investigating, we've determined this to be a false positive. There were no customer replication refresh operations impacted. We've confirmed replication services are functioning normally. If…1h 11mResolved
May 5, 2026Azure - West US 2 (Washington): INC0156645Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…8h 17mResolved
Apr 29, 2026Azure - UK South (London): INC0156355Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…1h 21mResolved
Apr 16, 2026GCP - US Central 1 (Iowa): INC0155608Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…1h 0mResolved
Apr 7, 2026Azure - East US 2 (Virginia): INC0155020Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…2h 29mResolved
Mar 27, 2026INC0154408Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…75h 3mResolved
Mar 21, 2026AWS - US West (Oregon): INC0154019Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…34 minResolved
Mar 16, 2026INC0153706Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…7h 3mResolved
Mar 12, 2026INC0153465Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…3h 30mResolved
Mar 7, 2026AWS - Europe (Zürich): INC0153183Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…2h 14mResolved
Mar 1, 2026AWS - Middle East (UAE): INC0152681To ensure the best possible service for our customers amid the persistent issues in the AWS Middle East (UAE) region and following the cloud service provider’s advice to transition workloads to other regions, we have…1801h 36mResolved
Feb 23, 2026Azure - Canada Central (Toronto): INC0152309Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…57 minResolved
Jan 27, 2026Azure - Central US (Iowa): INC0150687Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…1h 16mResolved
Jan 22, 2026AWS - US West (Oregon): INC0150440Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…4h 5mResolved
Jan 21, 2026AWS - US West (Oregon): INC0150359Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…2h 34mResolved
Jan 8, 2026INC0149526Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…1h 33mResolved
Jan 8, 2026Azure - West US 2 (Washington): INC0149493Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…2h 39mResolved
Dec 16, 2025INC0148543Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…13h 36mResolved
Dec 10, 2025AWS - US West (Oregon): INC0148166Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…1h 35mResolved
Nov 20, 2025Azure - Australia East (New South Wales): INC0147071Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…2h 41mResolved
Nov 19, 2025AWS - US East (N. Virginia): INC0146924Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…0 minResolved
Nov 5, 2025Azure - East US 2 (Virginia): INC0146178Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…4h 12mResolved
Nov 3, 2025Azure - Australia East (New South Wales): INC0146060Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…38 minResolved
Oct 22, 2025INC0145420Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…1h 6mResolved
Oct 20, 2025INC0145263Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…17h 21mResolved
Oct 14, 2025AWS - GovCloud (US-East): INC0144987Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…2h 16mResolved
Oct 3, 2025INC0144343Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…1h 57mResolved
Oct 2, 2025INC0144309Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…3h 1mResolved
Sep 30, 2025AWS - US East (N. Virginia): INC0144180Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…1h 35mResolved
Sep 30, 2025GCP - Europe West 2 (London): INC0144138Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…1h 17mResolved
Sep 27, 2025Azure - Switzerland North (Zürich): INC0143996Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…4h 2mResolved
Sep 24, 2025Azure - West Europe (Netherlands): INC0143819Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…2h 38mResolved
Sep 19, 2025Update New VNet Subnet IDs to Avoid Service InterruptionsWe have removed the previously communicated deadline to update VNet subnet IDs (BCR-1955) in the Azure - East US 2 (Virginia) and Azure - West US 2 (Washington) regions. Services will remain available, and no immediate…4h 0mScheduled
Sep 10, 2025Azure - East US 2 (Virginia): INC0142943Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…4h 48mResolved
Sep 10, 2025Azure - North Europe (Ireland): INC0142903Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…56 minResolved
Sep 3, 2025Azure - West Europe (Netherlands): INC0142507Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site…53 minResolved

How to Read This Snowflake Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Snowflake acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Snowflake outage in this window ran 75d 1h, against a mean recovery of 1d 11h. If you depend on Snowflake in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.