Future changes won’t be applied until the test suite is improved.
Users of the Google Cloud Compute Engine experienced a disruption to their services on the 7th March after a 43 minute outage.
The outage was attributed to "packet loss on egress network traffic", which was caused by an issue with a patch.
Google, said: "The root cause of the packet loss was a configuration change introduced to the network stack designed to provide greater isolation between VMs and projects by capping the traffic volume allowed by an individual VM."
"The configuration change had been tested prior to deployment to production without incident. However as it was introduced into the production environment it affected some VMs in an unexpected manner."
The disruption to service is the second that the company has had to deal with over the past few weeks. The result is that Google will be withholding future changes until the test suite has been improved.
Google, said: "Future changes will not be applied to production until the test suite has been improved to demonstrate parity with behavior observed in production during this incident."
"Additionally, Google engineers are immediately amending the rollout protocol for network configuration changes so that future production changes will be applied to a small fraction of VMs at a time, reducing the exposure in the event of undetected behavior."