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
INC20000139
Aug 5 , 15:49 UTC Resolved - Current status: We've confirmed that this issue has been 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 hosted in the specified region may have been intermittently unable to use CoCo services through Snowsight. Users may have seen an "Internal Server Error" when interacting with the service. All other Snowflake features were not impacted. Incident start time: 11:40 UTC August 05, 2026 Incident end time: 15:00 UTC August 05, 2026 Preliminary root cause: An underlying system component supporting Cortex services experienced failures due to connectivity issues with the file system, resulting in intermittent customer impact. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days. Aug 5 , 15:14 UTC Monitoring - Current status: We've completed implementing our 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 intermittently unable to use CoCo services through Snowsight. Users may have received an "Internal Server Error" when interacting with the service. All other Snowflake features were not impacted. Incident start time: 11:40 UTC August 05, 2026 Incident end time: 15:00 UTC August 05, 2026 Preliminary root cause: An underlying system component supporting Cortex services experienced failures due to connectivity issues with the file system, resulting in intermittent customer impact. Aug 5 , 15:00 UTC Identified - Current status: We've identified an issue with the underlying infrastructure supporting CoCo services, and we're implementing a
INC20000129
Aug 3 , 20:58 UTC Resolved - Current status: We've confirmed that this issue has been 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 hosted in the specified region may have been unable to start, resume, or manage virtual warehouses. The impact occurred during the periods of 13:33 to 15:20 UTC, and 16:05 to 16:36 UTC on August 03, 2026. Virtual warehouses may have appeared as stuck in the associated state. Existing warehouses that were already running may have been unaffected. Customers may also have seen queued or delayed queries for workloads running on affected warehouses. Additionally, some serverless tasks may have experienced residual queuing or failures until the backlog of requests which accumulated during the impact windows was processed. Incident start time: 13:33 UTC August 03, 2026 Incident end time: 16:36 UTC August 03, 2026 Preliminary root cause: A Cloud Services component responsible for virtual warehouse management became unhealthy. This caused failures in the internal workflows used to allocate and manage compute resources for warehouse start and resume operations, resulting in customer impact. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days. Aug 3 , 18:15 UTC Update - Current status: We've confirmed that our service has remained stable since 16:35 UTC, following our mitigation action; however, we're continuing to monitor the environment to confirm that the affected functionality continues to work as expected. Customer experience: Customers hosted in the specified region may have been unable to start, resume, or manage virtual warehouses. Virtual warehouses may have appeared as stuck in the associated state. Existing warehouses that
INC20000128
Aug 3 , 08:15 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 region may have experienced intermittent Snowsight login failures, elevated page load times, or session timeouts when accessing the web interface. Affected users may encounter errors such as "Failed to fetch" and "Execution failed", or HTTP 503 Service Unavailable messages. The issue was intermittent and did not affect all users or login attempts simultaneously; retrying failed requests generally results in successful connection. Although initial indications were that this issue was affecting multiple deployments, subsequent investigation demonstrated the issue was restricted to the AWS - Asia Pacific (Tokyo) region. Incident start time: 00:53 UTC August 03, 2026 Incident end time: 06:15 UTC August 03, 2026 Preliminary root cause: An update intended to improve the efficiency of connection handling at the network routing layer was identified and rolled back to restore service. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days. Aug 3 , 06:59 UTC Update - 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 region may have experienced intermittent Snowsight login failures, elevated page load times, or session timeouts when accessing the web interface. Affected users may encounter errors such as "Failed to fetch" and "Execution failed", or HTTP 503 Service Unavailable messages. The issue was intermittent and did not affect all users or login attempts simultaneously; retrying failed reques
INC20000115
Jul 30 , 04:56 UTC Resolved - Current status: We've monitored the environment and confirmed 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 regions may have been unable to log in to Snowsight. Affected users may have encountered HTTP 404 errors or "Incoming request with IP/Token is not allowed to access Snowflake" errors when attempting to access Snowsight via private endpoints. Workaround: There were no available workarounds for this issue. Incident start time: 00:18 UTC July 30, 2026 Incident end time: 03:52 UTC July 30, 2026 Preliminary root cause: A recent configuration change to a subset of the routing infrastructure caused connectivity failures for customers accessing Snowsight via private endpoints. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days. Jul 30 , 04:17 UTC Monitoring - Current status: We've reverted a recent configuration change and confirmed that service has been restored. 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 log in to Snowsight. Affected users may have encountered HTTP 404 errors or "Incoming request with IP/Token is not allowed to access Snowflake" errors when attempting to access Snowsight via private endpoints. Workaround: There were no available workarounds for this issue. Incident start time: 00:18 UTC July 30, 2026 Incident end time: 03:52 UTC July 30, 2026 Preliminary root cause: A recent configuration change to a subset of the routing infrastructure caused connectivity failures for customers accessing Snowsight via private endpoints. Jul 30 , 03:30 UTC Identified - Current status: We've identified the source of
INC20000106
Jul 25 , 16:01 UTC Resolved - Current status: We've confirmed that this issue has been 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 hosted in the specified region may have been unable to resume warehouses or may have experienced significant delays with serverless tasks and other workloads that required compute resources. Queries may have queued for extended periods instead of executing immediately, with some customers experiencing delays of several hours. Workaround: There were no available workarounds for this issue. Incident start time: 07:45 UTC July 25, 2026 Incident end time: 15:05 UTC July 25, 2026 Preliminary root cause: Unexpected demand from a large-scale workload exceeded available network capacity in the affected region, causing resource exhaustion that prevented new compute resources from being provisioned. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days. Jul 25 , 15:28 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 region may have been unable to resume warehouses or may have experienced significant delays with serverless tasks and other workloads that required compute resources. Queries may have queued for extended periods instead of executing immediately, with some customers experiencing delays of several hours. Workaround: There were no available workarounds for this issue. Incident start time: 07:45 UTC July 25, 2026 Incident end time: 15:05 UTC July 25, 2026 Preliminary root cause: Unexpected demand from a large-scale workload exceeded available
INC20000085
Jul 11 , 19:36 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 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. Jul 11 , 18:37 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 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. Jul 11 , 17:41 UTC Investigating - 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 ET
INC20000082
Jul 10 , 16:28 UTC Resolved - 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 regions may have been unable to connect to Snowflake via private connectivity solutions, such as PrivateLink. Users may have encountered connection errors or timeouts. Additionally, all customers using public connectivity may have been unable to access Snowsight between July 10, 2026, at 13:26 and 13:40 UTC. Incident start time: 13:26 UTC July 10, 2026 Incident end time: 14:33 UTC July 10, 2026 Preliminary root cause: Our preliminary root cause analysis identified that the load balancing infrastructure responsible for managing connections to Snowsight temporarily entered a degraded state, preventing requests from being processed successfully. We've engaged the associated Cloud Service Provider to investigate and troubleshoot this issue further. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days. Jul 10 , 15:58 UTC Monitoring - Current status: We've confirmed PrivateLink connectivity health has recovered, 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 connect to Snowflake via private connectivity solutions, such as PrivateLink. Users may have encountered connection errors or timeouts. Additionally, all customers using public connectivity may have been unable to access Snowsight between July 10, 2026, at 13:26 and 13:40 UTC. Incident start time: 13:26 UTC July 10, 2026 Incident end time: 14:33 UTC July 10, 2026 Preliminary root cause: Our preliminary root cause analysis identified that the load balancing infrastructure responsible for managing
INC20000063
Jun 30 , 23:34 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 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: 22: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. Jun 30 , 22:39 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. 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: 22:03 UTC June 30, 2026 Preliminary root cause: A routine system configuration change caused authentication issues with Snowsight. Once identified, the configuration was reverted. Jun 30 , 22:34 UTC Identified - 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 updat
INC20000052
Jun 24 , 17:22 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 region may have been unable to access or use Snowflake services and features using Snowsight. A subset of affected users in the region may also have been unable to execute queries, manage data, or may have experienced increased latency or performance issues with database operations. Incident start time: 15:10 UTC June 24, 2026 Incident end time: 15:50 UTC June 24, 2026 Preliminary root cause: A configuration issue caused an unexpected increase in load on our metadata database layer, resulting in cascading impact to dependent services like Snowsight and database operations. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days. Jun 24 , 16:44 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 region may have been unable to access or use Snowflake services and features using Snowsight. A subset of affected users in the region may also have been unable to execute queries, manage data, or may have experienced increased latency or performance issues with database operations. Incident start time: 15:10 UTC June 24, 2026 Incident end time: 15:50 UTC June 24, 2026 Preliminary root cause: A configuration issue caused an unexpected increase in load on our metadata database layer, resulting in cascading impact to dependent services like Snowsight and database operations. Jun 24 , 16:06 UTC Update - Current status: We've identified the source of the issue, and we've implemented a
INC20000047
Jun 24 , 07: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 region may have been intermittently unable to access or launch Streamlit apps, or may have experienced issues with other services and features that rely on Snowpark Container Services, such as Notebooks. Users may have experienced connection timeouts and received a "Connection error" when interacting with affected services. Workaround: There were no available workarounds for this issue. Incident start time: 15:20 UTC June 23, 2026 Incident end time: 05:10 UTC June 24, 2026 Preliminary root cause: A subset of infrastructure responsible for processing service requests experienced degraded performance, which prevented requests from completing and caused connectivity failures for services that rely on Snowpark Container Services. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days. Jun 24 , 06:01 UTC Monitoring - Current status: We restarted the affected infrastructure and confirmed it fully restored the remaining affected services. We'll continue to monitor the environment until we're confident all services are functioning properly. We'll provide another update within 1 hour. Customer experience: Customers hosted in the specified region may have been intermittently unable to access or launch Streamlit apps, or may have experienced issues with other services and features that rely on Snowpark Container Services, such as Notebooks. Users may have experienced connection timeouts and received a "Connection error" when interacting with affected services. Workaround: There were no available workarounds for this issue. Incident start time: 15:20 UTC June 23,
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.