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
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.