Snowflake experienced a major incident on August 18, 2026 affecting AI and ML, lasting 1h 53m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Aug 18, 2026, 12:58 PM UTC
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 regions may experience issues with AI and ML functionality. Specifically, when using Cortex Code in Snowsight, customer may see the following: “Internal Server error: You may need to start a new chat.”. All other Snowflake features are not impacted. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Incident start time: 11:10 UTC August 18, 2026
- identified Aug 18, 2026, 01:33 PM UTC
Current status: We've identified an issue with container scheduling in our compute infrastructure that is affecting AI and ML functionality, and we're implementing a fix to restore service. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified region may be unable to use Cortex Code in Snowsight and may see the following error message: "Internal Server error: You may need to start a new chat." All other Snowflake features are not impacted. ETA: Our current estimate is that service will be restored within 30 minutes. Incident start time: 11:20 UTC August 18, 2026 Preliminary root cause: Resource exhaustion in the compute infrastructure caused container scheduling failures, resulting in AI and ML functionality becoming unavailable.
- monitoring Aug 18, 2026, 01:55 PM UTC
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. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified region may have been unable to use Cortex Code in Snowsight and may have seen the following error message: "Internal Server error: You may need to start a new chat." All other Snowflake features are not impacted. Incident start time: 11:20 UTC August 18, 2026 Incident end time: 13:45 UTC August 18, 2026 Preliminary root cause: Resource exhaustion in the compute infrastructure caused container scheduling failures, resulting in AI and ML functionality becoming unavailable.
- resolved Aug 18, 2026, 02:51 PM UTC
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 experienced issues with AI and ML functionality. Specifically, when using Cortex Code in Snowsight, customers may have seen the following: “Internal Server error: You may need to start a new chat.” All other Snowflake features were not impacted. Incident start time: 11:20 UTC August 18, 2026 Incident end time: 13:45 UTC August 18, 2026 Preliminary root cause: Resource exhaustion in the compute infrastructure caused container scheduling failures, resulting in AI and ML functionality becoming unavailable. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.