Snowflake Status

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

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

Identified: 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

Investigating: 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

Resolved: Current status: We identified and reverted a misconfigured change, 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 multiple core Snowflake services and features. For example, affected users may have been unable to access Snowsight, Snowflake Openflow, Snowpark Container Services, or Cortex AI services (such as Cortex LLM functions, Agents, Analyst, and Search).

Workaround: There were no available workarounds for this issue.

Incident start time: 23:23 UTC June 10, 2026 Incident end time: 23:58 UTC June 10, 2026

Preliminary root cause: A misconfiguration during a system maintenance operation caused connectivity failures in the affected region.

A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.

Resolved: Current status: We've monitored the environment and confirmed 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 using Snowsight. Customers may have experienced page not found errors or general login failures.

Incident start time: 14:58 UTC June 08, 2026 Incident end time: 15:20 UTC June 08, 2026

Preliminary root cause: An internal system degradation occurred within backend database infrastructure that supports Snowsight in the affected region, causing Snowsight request failures. The issue was detected by system health monitoring, and automated recovery systems performed scaling and targeted infrastructure restart operations that helped to restore service. We’re continuing to investigate to confirm the underlying root cause details and the contributing factors.

A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.

Monitoring: Current status: During our investigation, the service self-recovered. 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. Customers may have experienced page not found errors or general login failures.

Workaround: There are currently no available workarounds for this issue.

Incident start time: 14:58 UTC June 08, 2026

Investigating: 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 Snowflake services and features using Snowsight.