CloudFail.net

We are still investigating the network issue with our xCloud infrastructure partner. We have established that new connections are not getting established to VMs. All engineers are working to ensure we restore proper network functionality.

Our engineers have been alerted to internal issues with the xCloud network, and are investigating the situation right now. All of our top engineers are working with the appropriate parties to come to a resolution. We will update you as more details become available.

We experienced a disruption of service on cluster EY01.  Engineers responded immediately and service is restored.  We are continuing our internal investigation as to the cause.

Our engineers have discovered the problem with the way that internal DNS was resolving, and have implemented the appropriate fix. Internal DNS resolution on the cluster is functioning as normal once again.

If you have any questions, please contact us by calling our support line or by filing a ticket in our support system.

We are currently investigating an issue with internal DNS resolution on ey04, which is affecting the way internal hostnames are returned within the cluster. Our engineers are working towards a resolution, and we will post more details and they become available.

It looks like the issue is resolved. We are looking into the issue to find any loose ends. If you have been affected and are still affected, log into our ticketing system or reach out to us on IRC:

irc://irc.freenode.net/#engineyard

Thanks

There are some connectivity issues with xCloud at the moment. We are currently investigating.

We found that the problem was a routing anomaly between the primary and secondary gateways.  We have restored network services on the secondary gateway but are still resolving the issue on the primary and will fail back later.

We have found a routing anomaly between the primary and secondary gateways.  We are working on a resolution.