INC20000046
Jun 23, 01:05 UTCJun 23, 02:35 UTC
Duration
1h 30m
Impact
Major
Root cause
DNS
Snowflake, 90 days
22 incidents
Affected
ApplicationsSnowpark Container ServicesAWS - Europe (London) - ApplicationsAWS - Europe (London) - Snowpark Container Services
Final update
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/INC20000046](https://community.snowflake.com/s/article/INC20000046)
Timeline
- Postmortem · Jul 2, 21:47 UTC
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/INC20000046](https://community.snowflake.com/s/article/INC20000046)
- Resolved · Jun 23, 02:35 UTC
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.
- Monitoring · Jun 23, 01:43 UTC
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.
- Investigating · Jun 23, 01:05 UTC
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
More from Snowflake
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 1404:48 UTC | INC20000217 | major | 1h 21m |
| Sep 1107:18 UTC | INC20000213 | critical | 6h 1m |
| Sep 921:53 UTC | INC20000211 | critical | 1h 58m |
| Sep 407:34 UTC | INC20000199 | critical | 2h 36m |
| Sep 109:58 UTC | INC20000190 | major | 3h 52m |
| Aug 3117:20 UTC | INC20000188 | critical | 2h 24m |
Also caused by dns
All| Started | Vendor | Incident | Impact | Duration |
|---|---|---|---|---|
| Jul 2720:34 UTC | Delays in creation of DNS records | minor | 2h 2m | |
| Jun 410:12 UTC | DNS API Service | minor | 1h 35m | |
| May 2223:27 UTC | New Database Creation Failing Due to Upstream Provider Issue | none | 32m | |
| May 1413:57 UTC | DNS service, Certificates and Managed MongoDB | minor | 6h 49m | |
| May 715:17 UTC | AWS Cluster DNS Changes Degraded Performance | major | 6h 58m | |
| Apr 2316:12 UTC | Incident with multiple GitHub services | critical | 1h 18m |
From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.