Snowflake Outage History

Snowflake degraded · 1 active incident View live status →

Snowflake had 64 outages in the last 2 years totaling 74h 38m of downtime — averaging 2.6 incidents per month.

There were 64 Snowflake outages since September 24, 2025 totaling 74h 38m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.snowflake.com

Major September 14, 2026

INC20000217

Detected by Pingoru
Sep 14, 2026, 04:48 AM UTC
Resolved
Sep 14, 2026, 06:09 AM UTC
Duration
1h 21m
Affected: Databases, Tables, and ViewsDatabases, Tables, and ViewsDatabases, Tables, and ViewsDatabases, Tables, and ViewsDatabases, Tables, and ViewsDatabases, Tables, and Views
Timeline · 4 updates

Read the full incident report →

Critical September 11, 2026

INC20000213

Detected by Pingoru
Sep 11, 2026, 07:18 AM UTC
Resolved
Sep 11, 2026, 01:19 PM UTC
Duration
6h
Affected: Databases, Tables, and ViewsDatabases, Tables, and Views
Timeline · 8 updates

Read the full incident report →

Critical September 9, 2026

INC20000211

Detected by Pingoru
Sep 09, 2026, 09:53 PM UTC
Resolved
Sep 09, 2026, 11:51 PM UTC
Duration
1h 58m
Affected: Databases, Tables, and ViewsVirtual WarehousesData Loading and UnloadingApplicationsSnowpark Container ServicesAI and MLOrganization and Account ManagementAlerts and NotificationsBusiness Continuity
Timeline · 4 updates
  1. investigating Sep 09, 2026, 09:53 PM UTC

    Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. Incident start time: 21:27 UTC September 09, 2026

  2. identified Sep 09, 2026, 10:08 PM UTC

    Current status: We've identified the source of the issue, and we're implementing a fix to restore service. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, execute queries, or manage data. ETA: Our current estimate is that service will be restored within 15-30 minutes. Incident start time: 21:27 UTC September 09, 2026

  3. monitoring Sep 09, 2026, 10:48 PM UTC

    Current status: We've implemented the fix for this issue, and we'll continue to monitor the environment until we're confident all services are functioning properly. Customer experience: Customers hosted in the specified regions may have been unable to access or use multiple core Snowflake services and features. Affected users may have been unable to sign in, execute queries, or manage data. Workaround: There were no available workarounds for this issue. Incident start time: 21:26 UTC September 09, 2026 Incident end time: 21:55 UTC September 09, 2026 Preliminary root cause: A subset of our metadata database infrastructure became unavailable, resulting in failures across multiple Snowflake services.

  4. resolved Sep 09, 2026, 11:51 PM 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 specified regions may have been unable to access or use multiple core Snowflake services and features. Affected users may have been unable to sign in, execute queries, or manage data. Workaround: There were no available workarounds for this issue. Incident start time: 21:26 UTC September 09, 2026 Incident end time: 21:55 UTC September 09, 2026 Preliminary root cause: A subset of our metadata database infrastructure became unavailable, resulting in failures across multiple Snowflake services. A root cause analysis (RCA) will be conducted and a summary will be made available within 5 business days.

Read the full incident report →

Critical September 4, 2026

INC20000199

Detected by Pingoru
Sep 04, 2026, 07:34 AM UTC
Resolved
Sep 04, 2026, 10:10 AM UTC
Duration
2h 36m
Affected: Databases, Tables, and ViewsApplicationsDeveloper Tools
Timeline · 6 updates

Read the full incident report →

Major September 1, 2026

INC20000190

Detected by Pingoru
Sep 01, 2026, 09:58 AM UTC
Resolved
Sep 01, 2026, 01:50 PM UTC
Duration
3h 52m
Affected: AI and MLAI and MLAI and MLAI and MLAI and MLAI and MLAI and MLAI and MLAI and MLAI and MLAI and MLAI and MLAI and MLAI and MLAI and MLAI and MLAI and MLAI and MLAI and MLAI and MLAI and MLAI and MLAI and MLAI and MLAI and MLAI and MLAI and MLAI and MLAI and MLAI and MLAI and MLAI and MLAI and MLAI and MLAI and MLAI and MLAI and MLAI and MLAI and MLAI and MLAI and MLAI and MLAI and MLAI and MLAI and MLAI and MLAI and MLAI and MLAI and MLAI and MLAI and MLAI and ML
Timeline · 6 updates

Read the full incident report →

Critical August 31, 2026

INC20000188

Detected by Pingoru
Aug 31, 2026, 05:20 PM UTC
Resolved
Aug 31, 2026, 07:44 PM UTC
Duration
2h 24m
Affected: Databases, Tables, and ViewsVirtual WarehousesData Loading and UnloadingApplicationsSnowpark Container Services
Timeline · 6 updates

Read the full incident report →

Major August 27, 2026

INC20000182

Detected by Pingoru
Aug 27, 2026, 07:05 PM UTC
Resolved
Aug 27, 2026, 08:26 PM UTC
Duration
1h 20m
Affected: Security and Privacy FeaturesSecurity and Privacy FeaturesSecurity and Privacy Features
Timeline · 5 updates

Read the full incident report →

Critical August 25, 2026

INC20000175

Detected by Pingoru
Aug 25, 2026, 03:53 AM UTC
Resolved
Aug 25, 2026, 04:35 AM UTC
Duration
41m
Affected: Databases, Tables, and ViewsApplications
Timeline · 4 updates

Read the full incident report →

Major August 20, 2026

INC20000168

Detected by Pingoru
Aug 20, 2026, 01:47 PM UTC
Resolved
Aug 20, 2026, 03:43 PM UTC
Duration
1h 56m
Affected: Security and Privacy Features
Timeline · 5 updates

Read the full incident report →

Critical August 14, 2026

INC20000157

Detected by Pingoru
Aug 14, 2026, 03:19 PM UTC
Resolved
Aug 14, 2026, 04:28 PM UTC
Duration
1h 8m
Affected: Applications
Timeline · 3 updates
  1. monitoring Aug 14, 2026, 03:19 PM UTC

    Current status: We've identified an issue that caused elevated error rates for Snowsight availability, and we've validated that service health has returned to normal following action by automated recovery systems. We'll continue to monitor the environment until we're confident all services are functioning properly. Customer experience: Customers hosted in the specified region may have experienced intermittent authentication failures and "service unavailable" errors between approximately 14:20 and 14:45 UTC. Incident start time: 14:20 UTC August 14, 2026 Incident end time: 14:45 UTC August 14, 2026 Preliminary root cause: A service infrastructure layer supporting authentication and session initiation for Snowsight entered an unhealthy state, causing login failures and service disruptions.

  2. resolved Aug 14, 2026, 04:28 PM UTC

    Current status: 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 Community or the Support page in Snowsight. Customer experience: Customers hosted in the specified region may have experienced intermittent authentication failures and "service unavailable" errors between approximately 14:20 and 14:45 UTC. Incident start time: 14:20 UTC August 14, 2026 Incident end time: 14:45 UTC August 14, 2026 Preliminary root cause: A service infrastructure layer supporting authentication and session initiation for Snowsight entered an unhealthy state, causing login failures and service disruptions. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.

  3. postmortem Aug 22, 2026, 02:37 AM 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/INC20000157](https://community.snowflake.com/s/article/INC20000157)

Read the full incident report →

Minor August 3, 2026

INC20000128

Detected by Pingoru
Aug 03, 2026, 05:53 AM UTC
Resolved
Aug 03, 2026, 08:15 AM UTC
Duration
2h 22m
Affected: ApplicationsApplicationsApplicationsApplicationsApplications
Timeline · 6 updates

Read the full incident report →

Critical July 30, 2026

INC20000115

Detected by Pingoru
Jul 30, 2026, 03:00 AM UTC
Resolved
Jul 30, 2026, 04:56 AM UTC
Duration
1h 56m
Affected: ApplicationsApplicationsApplicationsApplicationsApplicationsApplicationsApplicationsApplicationsApplicationsApplicationsApplicationsApplicationsApplicationsApplicationsApplicationsApplicationsApplicationsApplicationsApplicationsApplicationsApplicationsApplicationsApplicationsApplicationsApplicationsApplicationsApplicationsApplicationsApplicationsApplicationsApplicationsApplications
Timeline · 5 updates

Read the full incident report →

Minor July 25, 2026

INC20000106

Detected by Pingoru
Jul 25, 2026, 09:05 AM UTC
Resolved
Jul 25, 2026, 04:01 PM UTC
Duration
6h 55m
Affected: Databases, Tables, and ViewsVirtual Warehouses
Timeline · 8 updates

Read the full incident report →

Minor July 11, 2026

INC20000085

Detected by Pingoru
Jul 11, 2026, 05:41 PM UTC
Resolved
Jul 11, 2026, 07:36 PM UTC
Duration
1h 55m
Affected: Virtual Warehouses
Timeline · 4 updates
  1. investigating Jul 11, 2026, 05:41 PM UTC

    Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 1 hour. Customer experience: Customers hosted in the specified regions may experience delays or intermittent failures when resuming or managing virtual warehouses. Existing warehouses that are already running may be unaffected. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Incident start time: 16:30 UTC July 11, 2026

  2. monitoring Jul 11, 2026, 06:37 PM UTC

    Current status: We've implemented the fix for this issue, and we'll continue to monitor the environment until we're confident all services are functioning properly. Customer experience: Customers hosted in the specified regions may have experienced delays or intermittent failures when resuming or managing virtual warehouses. Existing warehouses that were already running may have been unaffected. Incident start time: 16:35 UTC July 11, 2026 Incident end time: 18:10 UTC July 11, 2026 Preliminary root cause: Resource exhaustion in the binary download service caused delays when virtual warehouses attempted to download required software components during startup.

  3. resolved Jul 11, 2026, 07:36 PM 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 experience: Customers hosted in the specified regions may have experienced delays or intermittent failures when resuming or managing virtual warehouses. Existing warehouses that were already running may have been unaffected. Incident start time: 16:35 UTC July 11, 2026 Incident end time: 18:10 UTC July 11, 2026 Preliminary root cause: Resource exhaustion in the binary download service caused delays when virtual warehouses attempted to download required software components during startup. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.

  4. postmortem Jul 18, 2026, 01:40 AM 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/INC20000085](https://community.snowflake.com/s/article/INC20000085)

Read the full incident report →

Major July 10, 2026

INC20000082

Detected by Pingoru
Jul 10, 2026, 02:30 PM UTC
Resolved
Jul 10, 2026, 04:28 PM UTC
Duration
1h 57m
Affected: ApplicationsSecurity and Privacy Features
Timeline · 5 updates

Read the full incident report →

Critical June 30, 2026

INC20000063

Detected by Pingoru
Jun 30, 2026, 10:34 PM UTC
Resolved
Jun 30, 2026, 11:34 PM UTC
Duration
1h
Affected: Applications
Timeline · 4 updates
  1. identified Jun 30, 2026, 10:34 PM UTC

    Current status: We're investigating an issue with Snowsight authentication. We are seeing recovery as of 22:03 UTC and are continuing to monitor. We'll provide an update within 60 minutes. Customer experience: Customers may be unable to access Snowsight or may experience being logged out unexpectedly. All other Snowflake features are not impacted. ETA: We have taken action to address the issue and expect it to be resolved as of 22:03 UTC. Incident start time: 21:47 UTC June 30, 2026

  2. monitoring Jun 30, 2026, 10:39 PM UTC

    Current status: We've implemented the fix for this issue, and we'll continue to monitor the environment until we're confident all services are functioning properly. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified region may have been unable to access Snowsight or may have experienced being logged out unexpectedly. All other Snowflake features were not impacted. Workaround: While we were focused on remediation, customers who were logged out needed to log back in to Snowsight. Incident start time: 21:47 UTC June 30, 2026 Incident end time: 23:03 UTC June 30, 2026 Preliminary root cause: A routine system configuration change caused authentication issues with Snowsight. Once identified, the configuration was reverted.

  3. resolved Jun 30, 2026, 11:34 PM 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 experience: Customers hosted in the specified region may have been unable to access Snowsight or may have experienced being logged out unexpectedly. All other Snowflake features were not impacted. Workaround: While we were focused on remediation, customers who were logged out needed to log back in to Snowsight. Incident start time: 21:47 UTC June 30, 2026 Incident end time: 23:03 UTC June 30, 2026 Preliminary root cause: A routine system configuration change caused authentication issues with Snowsight. Once identified, the configuration was reverted. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.

  4. postmortem Jul 08, 2026, 11:14 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/INC20000063](https://community.snowflake.com/s/article/INC20000063)

Read the full incident report →

Critical June 24, 2026

INC20000052

Detected by Pingoru
Jun 24, 2026, 03:38 PM UTC
Resolved
Jun 24, 2026, 05:22 PM UTC
Duration
1h 44m
Affected: Databases, Tables, and ViewsVirtual WarehousesData Loading and UnloadingApplications
Timeline · 5 updates

Read the full incident report →

Major June 23, 2026

INC20000047

Detected by Pingoru
Jun 23, 2026, 05:01 PM UTC
Resolved
Jun 24, 2026, 07:30 AM UTC
Duration
14h 29m
Affected: ApplicationsSnowpark Container Services
Timeline · 10 updates

Read the full incident report →

Major June 23, 2026

INC20000046

Detected by Pingoru
Jun 23, 2026, 01:05 AM UTC
Resolved
Jun 23, 2026, 02:35 AM UTC
Duration
1h 29m
Affected: ApplicationsSnowpark Container Services
Timeline · 4 updates
  1. investigating Jun 23, 2026, 01:05 AM UTC

    Current status: We're investigating an issue with Snowpark Container Services and Snowsight. We'll provide an update within 60 minutes. Customer experience: Customers hosted in the specified region may be unable to access Snowpark Container Services, and may intermittently be unable to sign in to Snowsight. Affected user may see HTTP 500 errors. Incident start time: 22:38 UTC June 22, 2026

  2. monitoring Jun 23, 2026, 01:43 AM UTC

    Current status: We identified and reverted a recent configuration change to resolve the impact. We'll continue to monitor the environment until we're confident all services are functioning properly. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified region may have been unable to access Snowpark Container Services, and may have intermittently been unable to sign in to Snowsight. Affected users may have seen HTTP 500 errors. Workaround: There were no available workarounds for this issue. Incident start time: 22:38 UTC June 22, 2026 Incident end time: 01:28 UTC June 23, 2026 Preliminary root cause: A recent configuration change affected DNS resolution in the affected region, which caused connectivity failures for Snowpark Container Services and Snowsight.

  3. resolved Jun 23, 2026, 02:35 AM UTC

    Current status: We've monitored the environment to confirm that reverting the configuration change restored service. 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 specified region may have been unable to access Snowpark Container Services, and may have intermittently been unable to sign in to Snowsight. Affected users may have seen HTTP 500 errors. Workaround: There were no available workarounds for this issue. Incident start time: 22:38 UTC June 22, 2026 Incident end time: 01:28 UTC June 23, 2026 Preliminary root cause: A recent system configuration change affected DNS resolution in the region, which caused connectivity failures for Snowpark Container Services and Snowsight. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.

  4. postmortem Jul 02, 2026, 09: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/INC20000046](https://community.snowflake.com/s/article/INC20000046)

Read the full incident report →