Previous incidents

We will continue to monitor to ensure scheduled backups work as expected.

Our team has successfully mitigated the root cause and have implemented the appropriate fix. All services are online and stable.

We have identified the root cause of the issue and deployed a patch. The Python ML runtime is back and operational now. We apologize for any inconvenience caused.

Our engineering team has applied a patch, and all services are now healthy. We will continue to monitor for errors and platform health. Thank you for your patience.

The connectivity issues with the database have been fully resolved, and the incident is now over. Thanks for your patience.

All databases are healthy and stable now. Thanks for your patience.

All services are healthy and stable. Thanks for your patience.

We have successfully deployed a fix to the issue. Our engineering team will continue to monitor the service.

We have resolved the issue. Console is up and fully functional now.

We have successfully implemented and deployed a fix. Functions are now stable and operational

We experienced problems with job processing as a result some users may have experienced degraded performance of functions and databases service. It has now been resolved and all services are operational.

The issue with the load balancer has been fully resolved, and all services are now operating as expected. We will continue to monitor the situation closely to ensure stability. Thank you for your patience and understanding during this time.

A fix was implemented and deployed to Cloud. Thanks to manual quality assurance we confirmed the problem is resolved for all affected functions.

The issue has been resolved and service has been restored.

Functions have stabilized.

We've fixed the problem so creating new functions and deploying will work now.

Any functions created during the incident that received the 'Invalid document structure: Unknown attribute: "specification"' error was not created successfully and should be deleted. You will get an error on deletion, but it should still delete.