Resolved -
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.
Aug 18, 14:51 UTC
Monitoring -
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.
Aug 18, 13:55 UTC
Identified -
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.
Aug 18, 13:33 UTC
Investigating -
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
Aug 18, 12:58 UTC
Resolved -
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 region may be unable to access or use Snowsight and may observe "503 Service Unavailable" errors.
Incident start time: 17:05 UTC August 14, 2026 Incident end time: 18:12 UTC August 14, 2026
Preliminary root cause: A routine system configuration change intended to optimize performance caused elevated latency in the metadata layer, resulting in service disruptions. Once identified, the configuration was reverted and affected service infrastructure was restarted to restore service.
A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.
Aug 14, 19:35 UTC
Monitoring -
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.
Customer experience: Customers hosted in the specified region may have been unable to access or use Snowsight and may have seen "503 Service Unavailable" errors.
Incident start time: 17:05 UTC August 14, 2026 Incident end time: 18:12 UTC August 14, 2026
Preliminary root cause: A routine system configuration change intended to optimize performance caused elevated latency in the metadata layer, resulting in service disruptions. Once identified, the configuration was reverted and affected service infrastructure was restarted to restore service.
Aug 14, 18:30 UTC
Identified -
Current status: We've identified a system configuration issue affecting Snowsight, 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 access or use Snowsight and may observe "503 Service Unavailable" errors.
ETA: Our current estimate is that service will be restored within 30 minutes.
Workaround: There are currently no available workarounds for this issue.
Incident start time: 17:05 UTC August 14, 2026
Aug 14, 17:58 UTC
Investigating -
Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 30 minutes.
Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features using Snowsight. Affected users may be unable to sign in and may observe "503 Service Unavailable" errors.
Incident start time: 17:05 UTC August 14, 2026
Aug 14, 17:29 UTC
Resolved -
Current status: We've 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 region may have experienced intermittent authentication failures and "service unavailable" errors between approximately 14:20 and 14:45 UTC.
Incident start time: 14:20 UTC August 14, 2026 Incident end time: 14:45 UTC August 14, 2026
Preliminary root cause: A service infrastructure layer supporting authentication and session initiation for Snowsight entered an unhealthy state, causing login failures and service disruptions.
A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.
Aug 14, 16:28 UTC
Monitoring -
Current status: We've identified an issue that caused elevated error rates for Snowsight availability, and we've validated that service health has returned to normal following action by automated recovery systems. We'll continue to monitor the environment until we're confident all services are functioning properly.
Customer experience: Customers hosted in the specified region may have experienced intermittent authentication failures and "service unavailable" errors between approximately 14:20 and 14:45 UTC.
Incident start time: 14:20 UTC August 14, 2026 Incident end time: 14:45 UTC August 14, 2026
Preliminary root cause: A service infrastructure layer supporting authentication and session initiation for Snowsight entered an unhealthy state, causing login failures and service disruptions.
Aug 14, 15:19 UTC
Resolved -
Current status: We've confirmed that this issue has been resolved, and we have monitored the environment to confirm that the affected functionality is now working as expected. 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 intermittently unable to use CoCo services through Snowsight. Users may have seen an "Internal Server Error" when interacting with the service. All other Snowflake features were not impacted.
Incident start time: 11:40 UTC August 05, 2026 Incident end time: 15:00 UTC August 05, 2026
Preliminary root cause: An underlying system component supporting Cortex services experienced failures due to connectivity issues with the file system, resulting in intermittent customer impact.
A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.
Aug 5, 15:49 UTC
Monitoring -
Current status: We've completed implementing our 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 intermittently unable to use CoCo services through Snowsight. Users may have received an "Internal Server Error" when interacting with the service. All other Snowflake features were not impacted.
Incident start time: 11:40 UTC August 05, 2026 Incident end time: 15:00 UTC August 05, 2026
Preliminary root cause: An underlying system component supporting Cortex services experienced failures due to connectivity issues with the file system, resulting in intermittent customer impact.
Aug 5, 15:14 UTC
Identified -
Current status: We've identified an issue with the underlying infrastructure supporting CoCo services, 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 CoCo services through Snowsight. Users may receive an "Internal Server Error" when interacting with the service. All other Snowflake features are not impacted.
ETA: Our current estimate is that service will be restored within 30 minutes.
Incident start time: 11:40 UTC August 05, 2026
Preliminary root cause: An underlying system component supporting CoCo services experienced failures, resulting in customer impact.
Aug 5, 15:00 UTC
Investigating -
Current status: We're continuing to investigate the issue with Snowflake Data Cloud. We're investigating a portion of infrastructure that appears unhealthy to develop a mitigation plan. We'll provide another update within 1 hour.
Customer experience: Customers hosted in the specified regions may be experiencing issues using CoCo through Snowsight. Users may receive an "Internal Server Error," when interacting with the service.
Aug 5, 14:41 UTC