As of December 3rd, 2018, PHP 7.0 has reached its end of life. This means it will no longer have security support and could be exposed to unpatched security vulnerabilities.
Additionally, as of December 31st, 2018, PHP 5.6 also reached its end of life. By the way, the first version 5.0 was launched 14 years ago.
root360 continues to provision PHP 7.0 and PHP 5.6 until mid of 2019 at no extra costs. This enables all customers to plan and migrate to PHP 7.1 or higher and regain security support. During your upgrade phase and required testing, we recommend to first update your local development or staging installation.
Get back to us at https://support.root360.cloud if we can support you planning your upgrade to PHP 7.1+.
Today will implement a feature that many of our docker customers have requested.
Until now a failed deployment caused a rollback to a previous version and returned exitcode 0 to your CI/CD pipelines. This caused troubles since your initial deployment did fail and the failure couldn't automatically be recognized by your toolchain. Therefor we changed the behavior so that a rollback is no longer marked as "OK". The rollback will now return exitcode 3.
A docker deployment can now reach the following states:
If you have further questions feel free to contact us at support.root360.cloud.
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 are always working to provide best and most efficient services at AWS for all customers.
In order to provide most recent features, higher security and higher performance for your application, we have updated our default settings to the following:
This change will NOT affect already provisioned resources but will be automatically applied when new resources are created.
When you have further questions, please get back to us at https://support.root360.cloud
19.11.2018: Additionally we have increased default version for memcached to 1.5 with AWS support (https://aws.amazon.com/about-aws/whats-new/2018/11/memcached15nowavailableonamazonelasticache/)
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.
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.
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:
Analyse traces to find long lasting querys and which component is involved:
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 https://support.root360.cloud
Find more information about Tideways 5 on https://tideways.com/profiler/...
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
simpler and better transaction naming
On Monday we released new features for our dashboard “Orbiter”. Now, it offers even more details about your AWS infrastructure in one compressed view.
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.
You can also monitor your CDN and Elastic Search in the “Orbiter”.
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.
Integration of ECS (Elastic Container Service)
Integration of CDN (CloudFront) & Elastic Search
Storage information for EC2 instances
We got a lot of feature requests concerning the default configuration of our servers.
Today we'll release changes that implement most of those requests.
The new configuration includes:
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.
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 deploy.py is deprecated since today. Please check your deployment processes.
As already announced Atlassian will not continue their Hipchat cloud service. You may read the full story at https://www.atlassian.com/blog...
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.
If you have further issues which may be related to this outage, please get back to us at https://support.root360.cloud/
11:04 fixed time in post
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 .
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 https://support.root360.cloud.
ElastiCache patches to improve security, reliability and operational performance
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.
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