Potential issue with engines startup

Final update

An internal component issue was identified as the root cause of the incident. The problem has been successfully resolved, and engines, DDLs, and DMLs are now functioning properly and are fully operational.

1. Resolved · May 6, 14:46 UTC
   An internal component issue was identified as the root cause of the incident. The problem has been successfully resolved, and engines, DDLs, and DMLs are now functioning properly and are fully operational.
2. Investigating · May 6, 14:31 UTC
   We are continuing our investigation into the ongoing issue with engines startup. We have also identified that DML and DDL operations may potentially be impacted and be slow.
3. Investigating · May 6, 14:07 UTC
   Our team is still actively investigating the latency in engines startup. Please be aware that starting engines may require more time than expected. We appreciate your patience and will provide further updates as soon as additional information is available.
4. Investigating · May 6, 13:40 UTC
   We are continuing to investigate the issue affecting engines startup. During this time, engines may take longer than usual to start. We are working diligently to identify and resolve the issue, and will keep you updated on our progress.
5. Investigating · May 6, 13:20 UTC
   We are currently investigating a potential issue with engines startup. Engines that are already running are not affected at this moment. Further updates will be provided as soon as more information becomes available.