Customer Service Team June 11th, 2018

Update: Amazon ElastiCache Mandatory Maintenance in next 2-3 weeks

AWS reached out to us that they need to apply mandatory updates for ElastiCache service. This update will effect all regions and include mandatory patches to improve security, reliability and operational performance.

In case of single instances there will be a short service interruption which may effect your project availability. You can read more about ElastiCache maintenance at [1].

root360 will contact all customers which have ElastiCache service in place to find best suitable maintenance window. 
For any question, feel free to get back to us at



  • ElastiCache patches to improve security, reliability and operational performance

Bugfix: root360 central logging system - masking issue

To comply with the new General Data Protection Regulation (DSGVO) we released an update of our central logging system last week.

One of the new feature is masking of IPv4 and IPv6 addresses during logrotation.

That way the current log files provide the IP addresses for log analysis but older compressed logfiles (e.g. from yesterday) are cleaned.

Under some circumstances the masking of IPv6 addresses also masked timestamps and other strings that are not IPv6 addresses.

We just released an update that fixes this issue.

If you have questions concerning the root360 central logging system you can read our documentation.

For issues with the root360 central logging system please contact our support team via ticket system or via mail at

Update: temporary disruption - limited accessibility of the root360 Customer Service

Due to a regional disturbance of the Internet connection, we have currently limited access. The communication via our ticket system as well as the telephony is affected by the disruption. We are already in contact with all involved service providers to solve the problem as fast as possible.

We will keep you updated via this channel.


  • 12:10 disruption is solved by our service provider

New Feature: root360 central logging system - improved log rotation and IP masking

The root360 logging system is an overall collector for technical and custom logs. Logs will be transferred to a unique place and merge into a single log per instance role. This solutions provides the most sophisticated way to transfer and monitor logs of scaling instances even with a limited lifetime.


As of 31st of May 2018 we will release a major update for root360 central logging system. Following changes will be applied for all managed logs in root360 central logging system:

  • Data retention will be 90 days of anonymized logs
  • Log rotation will take place on daily basis
  • IP masking will be applied after 1 day masking IPv4 and IPv6

This will affect logs which are registered via "register-log" [1] and "check-log-registration" [2] as well. Besides that, all customers will still be able to debug, aggregate and analyze most recent log files without any masking. Masking for IPv4 and IPv6 will be applied to the logs at first rotation only.

This action is required to fulfill latest requirements of DS-GVO (GDPR) for our customers. 

In case you will need a different log solution besides the upcoming changes, please get in touch with us at

We will be happy to support you.



New Features

  • mask IPv4 and IPv6 for all managed logs

  • force a pre-defined data retention

  • save disc space and log processing overhead

  • fulfill DS-GVO (GDPR) requirements

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

Moritz April 26th, 2018

Update: GitLab Service disrupted

Currently the GitLab Service is experiencing disruptions. This might cause deployment failures.

The status can be checked at


  • Problems should be resolved.

  • The problems occur again

  • Problems should be resolved by Gitlab.

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.