Snowflake Investigating Cortex Code Outage

Snowflake Data Cloud experiencing issues with AI and ML functionality in Cortex Code.

By The Downtime · Aug 18, 2026 · 1:00 PM ·Updated 4 days ago

Snowflake is investigating a major incident affecting its Data Cloud platform, according to an incident report published at 11:10 UTC on August 18, 2026. The company reports that customers in specified regions may experience errors when using Cortex Code in Snowsight, with users encountering internal server errors prompting them to start new chat sessions. All other Snowflake features remain unaffected.

Snowflake is a cloud-based data platform widely used for data warehousing, analytics, and data sharing across enterprises.

The incident began at 11:10 UTC. Snowflake is currently investigating and committed to providing an update within one hour. No estimated time of resolution has been provided. The company has recommended that affected customers using replication initiate failover procedures as a precaution.

This is a developing story. We'll provide updates as more information becomes available.

🕒 Live updates (4)

resolved Aug 18, 2:51 PM

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.

monitoring Aug 18, 1:55 PM

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.

identified Aug 18, 1:33 PM

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.

investigating Aug 18, 12:58 PM

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

📎 Sources

Snowflake status ↗

Outage details are aggregated from official provider status pages. The Downtime reports them as a public service and is not affiliated with the providers named.