INC20000046
Incident
Report for Snowflake
Resolved
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.
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.
Monitoring
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.
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.
Investigating
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
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
This incident affected: AWS - Europe (London) (Applications, Snowpark Container Services).