Snowflake reports multiple service issues

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.

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.

Current status: We've identified the source of the issue, and we've implemented a fix to restore service. We're assessing the recovery of affected components and we'll provide another update within 30 minutes. 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. Following initial recovery actions, sign in functionality has been restored, but customers may observe some increased latency or performance issues until service has fully recovered. ETA: Our current estimate is that service is recovering and will be fully restored within the next 30 minutes. Incident start time: 15:10 UTC June 24, 2026

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.

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.

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

Current status: We're continuing to validate recovery and address residual impact. We'll provide another update within 2 hours. Customer experience: Customers hosted in the specified region may be intermittently unable to access or launch Streamlit apps, or may experience issues with other services and features that rely on Snowpark Container Services, such as Notebooks. Users may experience connection timeouts and receive a "Connection error" when interacting with affected services. ETA: An ETA is not yet available. We'll provide one as soon as possible. Workaround: There are currently no available workarounds for this issue. Incident start time: 15:20 UTC June 23, 2026

Current status: We've identified the issue and deployed a two-part mitigation to address it, which included adding resources to the affected infrastructure and reverting a change. Affected services are recovering, and we're working to confirm full restoration. We'll provide another update within 2 hours. Customer experience: Customers hosted in the specified region may be intermittently unable to access or launch Streamlit apps, or may experience issues with other services and features that rely on Snowpark Container Services, such as Notebooks. Users may experience connection timeouts and receive a "Connection error" when interacting with affected services. ETA: An ETA is not yet available. We'll provide one as soon as possible. Workaround: There are currently no available workarounds for this issue. Incident start time: 15:20 UTC June 23, 2026

Current status: We've narrowed the issue to the request handling and authentication path for the affected services, and we're now applying and testing mitigation actions to restore service. We'll provide another update within 3 hours. Customer experience: Customers hosted in the specified region may be intermittently unable to access or launch Streamlit apps, or may experience issues with other services and features that rely on Snowpark Container Services, such as Notebooks. Users may experience connection timeouts and receive a "Connection error" when interacting with affected services. ETA: An ETA is not yet available. We'll provide one as soon as possible. Workaround: There are currently no available workarounds for this issue. Incident start time: 15:20 UTC June 23, 2026

Current status: We have narrowed the investigation to a request handling and authentication path for affected services. While the exact root cause is still under investigation, our teams have ruled out some earlier hypotheses and are actively evaluating potential mitigation actions. We'll provide another update within 2 hours. Customer experience: Customers hosted in the specified region may be intermittently unable to access or launch Streamlit apps, or may experience issues with other services and features that rely on Snowpark Container Services, such as Notebooks. Users may experience connection timeouts and receive a "Connection error" when interacting with affected services. ETA: An ETA is not yet available. We'll provide one as soon as possible. Workaround: There are currently no available workarounds for this issue. Incident start time: 15:20 UTC June 23, 2026

Current status: We've narrowed our investigation and remained focused on identifying a mitigation to address the impact to Snowpark Container Services. We'll provide another update within 2 hours. Customer experience: Customers hosted in the specified region may be unable to access or launch Streamlit apps or may experience connection timeouts and receive a "Connection error" when interacting with other services and features that rely on Snowpark Container Services. ETA: An ETA is not yet available. We'll provide one as soon as possible. Workaround: There are currently no available workarounds for this issue. Incident start time: 15:20 UTC June 23, 2026

Current status: We're continuing to investigate the issue affecting Snowpark Container Services to determine its source. We'll provide another update within 1 hour. Customer experience: Customers hosted in the specified region may be intermittently unable to access or launch Streamlit apps or may experience issues with other services and features that rely on Snowpark Container Services. Incident start time: 15:20 UTC June 23, 2026

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 region may be unable to access or launch Streamlit apps or other services and features that rely on Snowpark Container Services. Incident start time: 15:20 UTC June 23, 2026

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

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 region, which caused connectivity failures for Snowpark Container Services and Snowsight.

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 users may see HTTP 500 errors. Incident start time: 22:38 UTC June 22, 2026

Current status: We've monitored the environment to confirm our actions have 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 access or use multiple core Snowflake services and features, and may have experienced delays or failures with replication or when using Snowpipe to ingest files. Affected users may have been unable to execute queries and tasks or manage data, and may have seen a "Processing aborted due to error" SQL execution internal error. Incident start time: 20:12 UTC June 22, 2026 Incident end time: 21:45 UTC June 22, 2026 Preliminary root cause: Elevated load in a critical internal coordination service affected request processing for a subset of workloads. The underlying cause of the issue remains under investigation. A root cause analysis (RCA) document will be published within five business days.

Current status: We've completed actions to improve processing efficiency on the affected infrastructure and are seeing relief. We anticipate some customers may continue to experience latency as processing queues are 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 execute queries and tasks, or manage data. Users may have experienced delays or failures with replication or when using Snowpipe to ingest files. Affected users may have seen a SQL execution internal error: Processing aborted due to error. Incident start time: 20:12 UTC June 22, 2026 Incident end time: 21:45 UTC June 22, 2026 Preliminary root cause: Elevated load in a critical internal coordination service affected request processing for a subset of workloads. The underlying cause of the issue remains under investigation.

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/INC20000033](https://community.snowflake.com/s/article/INC20000033)

Current status: We are continuing to investigate the underlying source of the issue. In parallel, we are working to improve processing efficiency in a portion of our service infrastructure as a potential mitigation for the increased downstream load affecting related services. 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 execute queries and tasks, or manage data. Users may experience delays or failures with replication or when using Snowpipe to ingest files. Affected users may see a SQL execution internal error: Processing aborted due to error. Workaround: There are currently no available workarounds for this issue. An ETA is not yet available. We'll provide one as soon as possible. Incident start time: 20:12 UTC June 22, 2026

Current status: We've confirmed that this issue impacts service, and we're continuing to investigate to determine the source of the issue. 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 execute queries and tasks, or manage data. Users may may experience delays or failures when using Snowpipe to ingest files. Affected users may see a SQL execution internal error: Processing aborted due to error. Incident start time: 20:12 UTC June 22, 2026

Current status: We're continuing to investigate the issue with Snowflake Data Cloud. 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. Users may may experience delays or failures when using Snowpipe to ingest files.

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

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 seen that stored procedures that use Snowpark external access integrations failed with the following SQL execution internal error: 300010:4004234085. Incident start time: 15:10 UTC June 12, 2026 Incident end time: 19:15 UTC June 12, 2026 Preliminary root cause: A misconfiguration introduced by a recent network configuration change affecting outbound connectivity for stored procedures that use Snowpark external access integrations resulted in impact. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.

Current status: We've fully reverted the impacting network configuration change, and our telemetry indicates that service health is recovering. 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 seen that stored procedures that use Snowpark external access integrations failed with the following SQL execution internal error: 300010:4004234085. Incident start time: 15:10 UTC June 12, 2026 Incident end time: 19:15 UTC June 12, 2026 Preliminary root cause: A misconfiguration introduced by a recent network configuration change affecting outbound connectivity for stored procedures that use Snowpark external access integrations resulted in impact.

Current status: Our investigation indicates the issue is related to a recent network configuration change affecting outbound connectivity for stored procedures that use Snowpark external access integrations. We are reverting the suspected change and manually correcting the affected network configuration to restore service as quickly as possible. We'll provide an update within 1 hour. Customer experience: Customers hosted in the specified regions may see that stored procedures that use Snowpark external access integrations may fail with the following SQL execution internal error: 300010:4004234085. ETA: Our current estimate is that service will be restored within 1 hour. Incident start time: 15:10 UTC June 12, 2026

Current status: We're investigating an issue with stored procedures that use Snowpark External Access integrations. We'll provide an update within 1 hour. Customer experience: Customers hosted in the specified regions may see that stored procedures that use Snowpark External Access integrations may fail with the following SQL execution internal error: 300010:4004234085. Incident start time: 15:10 UTC June 12, 2026