Is Snowflake Down?
Real-time status check for snowflake.com
Checking status...
About Snowflake Status
BlueMonitor checks Snowflake (snowflake.com) by sending automated requests to its servers. If the service responds within a normal timeframe and returns a successful status code, it's marked as operational. Response times over 3 seconds indicate the service is slow, and connection failures or server errors indicate the service may be down.
Recent Incidents
INC0154408
Mar 30 , 21:38 UTC Resolved - Current status: We've confirmed that the infrastructure issue delaying deployment of the fix to the GCP - US East 4 (N. Virginia) region was resolved, and we have monitored the environment to confirm that the affected functionality is now working as expected. 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 may have been unable to see or manage their Native Apps within the "Apps" page of the Snowsight UI. App execution and all other Snowflake features were not impacted. SQL commands (e.g., SHOW APPLICATIONS) or searching for apps using the Catalog > Database Explorer page could still be used to view and manage Native Apps. Incident start time: 00:00 UTC March 27, 2026 Incident end time: 05:55 UTC March 29, 2026 Preliminary root cause: A recent Snowsight release introduced a code issue that caused an error to occur when attempting to load application metadata within the Apps page. This prevented the page from rendering the list of installed applications as expected. A root cause analysis (RCA) document will be published within five business days. Mar 30 , 17:10 UTC Update - Current status: We've implemented the fix for this issue across all regions except GCP - US East 4, where we're working to complete the rollout of the fix. We'll continue to monitor the environment and provide another update by 18:00 UTC on March 31, 2026. Customer experience: Customers may be unable to see or manage their Native Apps within the "Apps" page of the Snowsight UI. App execution and all other Snowflake features are not impacted. ETA: The affected functionality has been restored in all but one region. An ETA is not yet available for the remaining GCP - US East 4 (N. Virginia) region; we'll provide one as soon as possible. In the meantime, we recommend affected users in that region use the suggested workaround. Workaround: While we're fo
AWS - US West (Oregon): INC0154019
Mar 21 , 07:12 UTC Resolved - 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 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. Users would have encountered HTTP 404 or other similar errors. Incident start time: 05:27 UTC March 21, 2026 Incident end time: 06:18 UTC March 21, 2026 Preliminary root cause: The investigation determined that infrastructure responsible for high-level traffic routing and name resolution became degraded, which caused customers to encounter HTTP 404 errors when attempting to access or use certain Snowflake services. A root cause analysis (RCA) document will be published within five business days. Mar 21 , 06:38 UTC Monitoring - 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. Users would have encountered HTTP 404 or other similar errors. Incident start time: 05:27 UTC March 21, 2026 Incident end time: 06:18 UTC March 21, 2026 Preliminary root cause: The investigation determined that infrastructure responsible for high-level traffic routing and name resolution became degraded, which caused customers to encounter HTTP 404 errors when attempting to access or use certain Snowflake services. Mar 21 , 06:23 UTC Identified - Current status: We've identified the source of the issue, and we're developing and implementing a
INC0153706
Mar 17 , 05:49 UTC Resolved - 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 been unable to create or alter Snowflake alerts. Incident start time: 14:53 UTC March 14, 2026 Incident end time: 04:39 UTC March 17, 2026 Preliminary root cause: A recent improvement to Snowflake alerts creation and alteration contained a code issue. A root cause analysis (RCA) document will be published within five business days. Mar 17 , 04:58 UTC Monitoring - Current status: We've finished rolling out the fix to restore service. 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 create or alter Snowflake alerts. Incident start time: 14:53 UTC March 14, 2026 Incident end time: 04:39 UTC March 17, 2026 Preliminary root cause: A recent improvement to Snowflake alerts creation and alteration contained a code issue. Mar 16 , 23:45 UTC Identified - Current status: We've determined a recent improvement to Snowflake alerts creation and alteration contains a code issue, which is causing the impact. We've developed a fix and are rolling it out to restore service. We'll provide another update within 6 hours. Customer experience: Customers hosted in the specified regions may be unable to create or alter Snowflake alerts. ETA: Our current estimate is that service will be restored for all affected customers within 6 hours. Customers will see relief as the fix rolls out. In the meantime, affected customers using replication in an unaffected region may initiate their failover procedures as a way to bypass the issue. Workaround: There are currently no available workarounds for this
INC0153465
Mar 12 , 23:13 UTC Resolved - Current status: We've confirmed that the rollback of the impacting Snowflake Intelligence update has completed, 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 use Snowflake Intelligence services and features. Additionally, users may have experienced issues with expired sessions attempting to access Snowflake Intelligence. Existing sessions should have been unaffected. Workaround: While we were focused on remediation, users may have been able to work around the issue by accessing the service directly via the non-account-specific URL, AI.Snowflake.com, in a private browser tab. Incident start time: 16:30 UTC March 12, 2026 Incident end time: 20:39 UTC March 12, 2026 Preliminary root cause: An update intended to optimize Snowflake Intelligence introduced a code issue that caused problems with expired sessions attempting to access Snowflake Intelligence. Mar 12 , 21:50 UTC Monitoring - Current status: We've confirmed that the rollback of the impacting Snowflake Intelligence update has completed, 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 use Snowflake Intelligence services and features. Additionally, users may have experienced issues with expired sessions attempting to access Snowflake Intelligence. Existing sessions should have been unaffected. Workaround: While we were focused on remediation, users may have been able to work around the issue by accessing the service directly via the non-account-specific URL, AI.Snowflake.com, in a private browser tab. Incident start time: 16:30 UTC March 12, 2026 Incident end time: 20:39 UTC March 12, 2026 Preliminary root cause: An update intended to optimize Snowflake Intelligence introduced a code issue that c
AWS - Europe (Zürich): INC0153183
Mar 7 , 22:20 UTC Resolved - Current status: We've coordinated with our third-party cloud platform to confirm that the fix for this issue was successfully implemented, and we've monitored the environment to confirm that service has been fully 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. Incident start time: 19:30 UTC March 07, 2026 Incident end time: 21:10 UTC March 07, 2026 Preliminary root cause: A third-party cloud platform experienced an issue with part of their storage service, which temporarily prevented some Snowflake services and features from working for a subset of customers in this region. A root cause analysis (RCA) document will be published within ten business days. Mar 7 , 21:23 UTC Monitoring - Current status: We've coordinated with our third-party cloud platform to remediate 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. Incident start time: 19:30 UTC March 07, 2026 Incident end time: 21:10 UTC March 07, 2026 Preliminary root cause: A third-party cloud platform experienced an issue with part of their storage service, which temporarily prevented some Snowflake services and features from working for a subset of customers in this region. Mar 7 , 20:37 UTC Identified - Current status: We've identified an issue with a third-party cloud platform, and we're coordinating with the provider to restore service. We're beginning to see som
AWS - Middle East (UAE): INC0152681
Mar 5 , 04:39 UTC Update - Current status: We continue to actively monitor the situation, and our cloud service provider affirms that meaningful progress is being made toward recovery, with several distinct services showing sustained improvement. While focused efforts continue toward full-service restoration for the region, the cloud service providers' initial advice to migrate your workloads and traffic to alternate Region(s) remains in place. We are in continuous contact with the provider and will post our next update once they confirm significant progress in restoring the site's physical environment, or when other material updates become available. 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: An updated 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. Affected customers should look for additional updates in their cloud service provider's personal health dashboard. Incident start time: 12:25 UTC March 01, 2026 Mar 4 , 06:02 UTC Update - Current status: We continue to actively monitor the situation as we work with our cloud service provider to restore service following a power outage at a primary data center. Recovery efforts remain focused on foundational services, and multiple paths to restoration continue to be pursued. Work to restore the underlying infrastructure needed for full restoration is still in progress. Additionally, we've been informed that our cloud service provider will supplement their public service health updates with a targeted communications approach, delivered directly to customers through their personal health dashboards, for a more localized, relevant view of service health. We will provide our next update within 24 hours. Customer experience: Cus
Azure - Canada Central (Toronto): INC0152309
Feb 23 , 22:07 UTC Resolved - Current status: Our observations of service telemetry continue to indicate that our service has recovered following our mitigation. 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 intermittent delays or failures when accessing or using Snowflake services and features. This may have included slower query execution, intermittent availability, or limited feature functionality. Incident start time: 19:26 UTC February 23, 2026 Incident end time: 21:11 UTC February 23, 2026 Preliminary root cause: A networking issue caused a component to be unable to process traffic and resolve DNS requests as expected. A root cause analysis (RCA) document will be published within five business days. Feb 23 , 21:47 UTC Monitoring - Current status: We identified a networking issue that caused a component to be unable to process traffic and resolve DNS requests as expected, resulting in impact. We 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 experience intermittent delays or failures when accessing or using Snowflake services and features. This may include slower query execution, intermittent availability, or limited feature functionality. Incident start time: 19:26 UTC February 23, 2026 Incident end time: 21:11 UTC February 23, 2026 Preliminary root cause: A networking issue caused a component to be unable to process traffic and resolve DNS requests as expected. Feb 23 , 21:09 UTC Investigating - Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. Customer experience: Customers hosted in the specified regions may experience intermittent delays or failures when acc
Azure - Central US (Iowa): INC0150687
Jan 27 , 19:30 UTC Resolved - 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 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. Additionally, they may have been unable to continuously stream data into Snowflake using Snowpipe Streaming, or ingest data using Snowpipe, and may have been unable to execute queries, retrieve results, or manage data objects such as tables and views. Incident start time: 17:51 UTC January 27, 2026 Incident end time: 18:25 UTC January 27, 2026 Preliminary root cause: A recent change to our service infrastructure experienced an incompatibility issue on a subset of instances in the metadata database layer, causing requests to fail. A root cause analysis (RCA) document will be published within five business days. Jan 27 , 19:02 UTC Monitoring - Current status: We've identified a recent change to our service infrastructure that resulted in impact. We've reverted this change to remediate the issue, and we've observed that the issue has been resolved. 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. Additionally, they may have been unable to continuously stream data into Snowflake using Snowpipe Streaming, or ingest data using Snowpipe, and may have been unable to execute queries, retrieve results, or manage data objects such as tables and views. Incident start time: 17:51 UTC Jan
AWS - US West (Oregon): INC0150440
Jan 22 , 23:24 UTC Resolved - Current status: Our observations of service telemetry continue to indicate that our service has recovered following the restart of the systems related to the Snowsight application-hosting layer. 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 Snowflake services and features using Snowsight or may have experienced delays. A subset of customers may have encountered errors while executing queries and other related operations. Incident start time: 19:02 UTC January 22, 2026 Incident end time: 19:30 UTC January 22, 2026 Preliminary root cause: While we're continuing to investigate to determine the underlying root cause of this issue, we suspect that a recent change made to our internal monitoring systems may have resulted in the problem with the Snowsight application-hosting layer. A root cause analysis (RCA) document will be published within five business days. Jan 22 , 20:48 UTC Monitoring - Current status: Our observations of service telemetry indicate that our service has recovered following the restart of the systems related to the Snowsight application-hosting layer. 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 Snowflake services and features using Snowsight or may have experienced delays. Incident start time: 19:02 UTC January 22, 2026 Incident end time: 19:30 UTC January 22, 2026 Preliminary root cause: While we're continuing to investigate to determine the underlying root cause of this issue, we suspect that a recent change made to our internal monitoring systems may have resulted in the problem with the Snowsight application-hosting layer. Jan 22 , 19:48 UTC Update - Current status: Our investigation has led us to focus on
AWS - US West (Oregon): INC0150359
Jan 21 , 21:57 UTC Resolved - 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 been unable to access or use Snowflake services and features via Snowsight and may have experienced delays. Incident start time: 19:00 UTC January 21, 2026 Incident end time: 20:08 UTC January 21, 2026 Preliminary root cause: Our preliminary investigation identified that the Snowsight application-hosting layer and the Snowsight-specific database layer experienced an issue that led to an unexpected surge in requests, leading to high resource utilization and preventing the service from processing the associated traffic, resulting in suspended login attempts. A root cause analysis (RCA) document will be published within five business days. Jan 21 , 20:57 UTC Monitoring - Current status: We've completed a restart on systems related to the application layer. Our telemetry indicates that this issue is no longer occurring, and users should be able to successfully access the service via the Snowsight User Interface (UI). 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 Snowflake services and features via Snowsight and may have experienced delays. Incident start time: 19:00 UTC January 21, 2026 Incident end time: 20:08 UTC January 21, 2026 Preliminary root cause: Our preliminary investigation identified that the Snowsight application-hosting layer and the Snowsight-specific database layer experienced an issue that led to an unexpected surge in requests, leading to high resource utilization and preventing the service from processing the associated traffic, resulti
Frequently Asked Questions
Is Snowflake down right now?
This page shows the real-time status of Snowflake. The status is checked automatically by pinging Snowflake's servers. If the status shows "Down", it means Snowflake is currently experiencing issues.
Why is Snowflake not working?
Snowflake may not be working due to server outages, scheduled maintenance, network issues, or high traffic. Check the current status above for real-time information.
How do I check if Snowflake is down for everyone?
BlueMonitor checks Snowflake's servers from our monitoring infrastructure. If the status shows "Down" here, it's likely down for everyone. If it shows "Up" but you can't access it, the issue may be on your end.
What should I do if Snowflake is down?
If Snowflake is down, you can: wait a few minutes and try again, check their official social media for updates, clear your browser cache, or try using a different network connection.