We are currently experiencing failing deployments due to a broken Ubuntu package. At the moment all deployments will fail. This has no impact on your currently running releases, so no downtime or other issues are to be expected. Nether the less please do not run deployments until further notice.
We will keep you updated.
18:02 We have successfully recovered package availability for all deployments and started internal measures to prevent further service disruptions caused by package maintainers.
We released new features for our dashboard "Orbiter". The Orbiter now offers the possibilty to list all existing snapshots of a database instance. Further the public ip address of the bastion host is shown in the Orbiter.
By clicking the snapshots button all snapshots will be displayed in a separeted pop-up.
The pop-up shows all available snapshots with additional information about them, including the important time of creation. By clicking the relevant snapshot identifier a new view will be displayed.
This view provides the ability to copy the restore command for the specific snapshot. This command has to be run on the bastion host to create a new database beside the exisiting to access the restored data.
Public ip address
The Orbiter now shows the public ip address of the bastion host. There is a link to our knowledge base, which discribes how to connect via ssh to the environment, too.
On Monday we released new features for our dashboard “Orbiter”. Now, it offers even more details about your AWS infrastructure in one compressed view.
Integration of ECS (Elastic Container Service)
With the update “Orbiter” gives you more insights in your Docker containers. You can keep an eye on the workload of your containers run on ECS on our own. If you think limits should be adjusted, just let us know.
Integration of CDN (CloudFront) & Elastic Search
You can also monitor your CDN and Elastic Search in the “Orbiter”.
Our next steps:
Our work at the “Orbiter” is still not finished. In the next release we are planning to add ECS Log Files and an overview about backups and how to restore.
As we rolled out our cloud management CLI suite 'r3'  almost a year ago, we are deprecating the old legacy commands for deploying customer code into our infrastructure. This affects the following commands:
Starting today those commands will deploy the code and always return code 250 and a deprecation message when the deploy was successful. You should switch to the r3-command to deploy your code  by 27th September 2018. After this date the mentioned commands will be removed.
Hipchat has been a great platform to support customers during migration phase to the AWS powered root360 platform. Today, we will announce the end of the hipchat service for all customer as well. We will discontinue the service by end of August 2018.
As we like to chat with you, we published a new chat service paired with our customer support portal. After you successful logged in to https://support.root360.cloud, you will see a small orange bubble on the bottom right.
By clicking this chat icon you will be transferred immediately to a customer support agent.
We will answer as soon as possible to support you.
Please keep in mind, that we will only support chat during business hours. In the event of a fault, please call +49 (0) 341 39 280 907-7 or send us a ticket via https://support.root360.cloud
In the night between 1:39 AM UTC and 1:49 AM UTC AWS experienced network connectivity issues for some instances in a single Availability Zone in the EU-CENTRAL-1 Region. This may have affected your availability during this period.
We have reviewed the components and do not see any malfunction of currently running instances. The issues has been resolved by AWS at 2:34 AM UTC officially.