What visitors reported during this incident
No visitor reports were filed for this incident.
Having problems with Snowflake now? Check the current statusAffected services
Updates (5)
- Jun 22, 2026, 10:16 PMINC20000033
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)
Snowflake ↗ - Jun 12, 2026, 08:57 PMINC20000033
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
Snowflake ↗ - Jun 12, 2026, 07:53 PMINC20000033
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 misconfigurati
Snowflake ↗ - Jun 12, 2026, 07:14 PMINC20000033
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:400423
Snowflake ↗ - Jun 12, 2026, 06:21 PMINC20000033
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
Snowflake ↗
What to do next
- Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
- Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
- Watch the provider going forward. Follow Snowflake's status feed →
GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.