Releases involving Timo

Timo September 28th, 2018

Update: root360 Cloud Dashboard “Orbiter” gets new features

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.


Get in touch with our root360 Dashboard at 
If your not registered yet, please contact us at

Timo September 12th, 2018

Update: Tidesways 5 now available on root360 cloud platform

With the release of Tideways 5, our customers now have the opportunity to use the new features of Tideways 5 to monitor the performance of their applications and to debug them on their server.

Tideways 5 now offers a more detailed view of the metrics:

5b98ea263c798_Tideways 1.png

Analyse traces to find long lasting querys and which component is involved:

5b98ed157389f_TIdeways 2.png

If you already use Tideways and would like to upgrade to version 5, then you can contact our support and upgrade them.

For questions about Tideways, please contact our customer service at

Find more information about Tideways 5 on

New Features

  • capturing more data in monitoring mode

  • always capture the total performance of SQL, HTTP, Redis, Memcache, File I/O and other downstream services for monitoring purposes

  • Memory Profiling

  • simpler and better transaction naming

Customer Service Team August 30th, 2018

Update: Deprecation of old legacy deploy scripts and​

As we rolled out our cloud management CLI suite 'r3' [1] 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 [2] by 27th September 2018. After this date the mentioned commands will be removed.

root360 Cloud Management CLI Suite r3

Default Deployment: How deployment via CLI is working

Docker (ECS) Deployment: root360 Container Platform Deployment 


  • Due to a security patch the deploy script is deprecated since today. Please check your deployment processes.

Customer Service Team July 19th, 2018

Bugfix: Today's AWS Network Connectivity Issues

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.

If you have further issues which may be related to this outage, please get back to us at



  • 11:04 fixed time in post

Timo May 23rd, 2018

Update: We are currently not available via and our ticket system

Currently we have no possibility to receive and send messages via and our ticket system. We are already in contact with the provider of our ticket system. We apologize for this circumstance and keep you up to date.


  • 14:15 - problems are resolved

Timo May 16th, 2018

Update: root360 Dashboard is getting new features

We've updated the root360 Dashboard with new features that allow our customers to get even more information about their environments. See our new features below.


We now offer our customers 14 days to look back in their metric graphs.



We have now given our customers the opportunity to see triggered CloudWatch alerts in the orbiter.


Alarm Thresholds

Our customers now see the set alarm thresholds in the graph and when they have been exceeded.


Mobile View

Always well informed on the way. Our dashboard now has a responsive design, allowing our customers to keep track of their environment from any device.


Get in touch with our root360 Dashboard at

If your not registered yet, please contact us at

New Features

  • extension of the time period from max. 6 hours to max. 14 days backwards

  • mobile view

  • added alarm threshold to graphs

  • see alarms for every single service

Timo May 9th, 2018

Update: Security enhancements for ssh connections

To increase security for our customers, we have increased security for SSH connections by disabling weak encryption, key exchange protocols, and MAC algorithms.

Timo April 30th, 2018

Update: Security enhancements on root360-redirect-service

To improve the security for our customers we disabled TLS verions 1.0 and 1.1 on our redirect service.

For more information about the root360 redirect service, see

Timo April 26th, 2018

Update: Ending support for MySQL minor engine versions 5.6.27 and 5.6.29 by AWS RDS

AWS has announced that as of August 1, 2018, support for the MySQL minor engine versions 5.6.27 and 5.6.29 will be discontinued.

Beginning on July 25, 2018 at 0:00 UTC, all RDS DB instances running MySQL 5.6.27 or 5.6.29 will be automatically upgraded to the latest minor version during the next maintenance window specified for each instance. Any instances still running one of these versions on August 1, 2018 at 0:00 UTC will be upgraded immediately. Once this completes, any instance restored from a snapshot of the deprecated version will automatically and immediately be upgraded to a currently supported version.

We will contact the relevant customers and, if necessary, schedule maintenance together. During maintenance, downtime can be expected.

Timo April 24th, 2018

Bugfix: Currently DNS problems effects availability of websites


We noticed some DNS problems occurring while accessing some websites. The problems aren't located at AWS only.

We will keep you updated.


  • 15:00 AWS also confirmed DNS resolution errors using third party DNS resolvers /

  • 15:30 AWS resolved the issues

Timo April 10th, 2018

Update: How to / Why request a vulnerability / penetration test

In order to prevent outage and security alerts caused by a penetration or vulnerability test, we require to announce this kind of automated test 3 business days before. We will also forward this information to AWS to ensure no actions will be taken during the test. Please note that only tests are allowed which are compliant to the AWS acceptable use policy and AWS penetration tests rules.

See our form

Timo April 3rd, 2018

Update: Currently npm installation fails

Currently the npm installation fails on our environments due to an internal npm failure. We are working on a patch right now.


  • 14:30 The patch for the broken npm was now rolled out in our environments, which fixes the npm installation issues.

Timo March 22nd, 2018

Update: deployments using fail

We've noticed an increased amount of errors in deployments that use

We are in contact with to locate the cause.

We'll keep you posted here.


  • 11:30 Our tests show that the regions Ireland and USA are not affected by this issue.

  • 13:00 Bitbucket confirmed an issue of the connection between there data centers causing this issue

  • see for current status on Bitbuckets side

  • 13:45 Bitbucket found the cause with their network vendor and are working to solve it


  • 17:00 issue was solved by Bitbucket and there network vendor; our tests confirm that the issue is solved

Timo March 8th, 2018

New Feature: Memcached Amplification: New DDoS attack has no effect on root360 infrastructures

The newly discovered ability to exploit publicly available memcaches for DDoS attacks is now even easier with ready-made tools. Nevertheless, it is not possible to misuse memcaches used in Root360 infrastructures because they are securely located in the application network and are not publicly accessible. Further information can be found in our Quickstart.

Timo March 2nd, 2018

Bugfix: AWS disruption on 1. March 2018 between 23:41 CET and 23:56 CET

Between 23:41 CET and 23:56 CET some EC2 instances experienced elevated DNS resolution errors in the EU-CENTRAL-1 and EU-WEST-1 Region. As a result of this, some AWS services experienced elevated errors and increased latency. The issue has been resolved and the service is operating normally.