Migration of CloudAMQP servers in Azure Classic (servers in Azure ARM are not affected)
Scheduled Maintenance Report for CloudAMQP
Completed
All instances that were scheduled to be migrated have been migrated.
Posted Sep 19, 2017 - 19:49 UTC
In progress
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted Sep 19, 2017 - 06:00 UTC
Scheduled
We have scheduled a maintenance for CloudAMQP instances in Azure Classic, where we will move the instances from Azure Classic to Azure ARM. It will require about 5 min downtime for all single node servers (2 and 3 node clusters are not affected).

Type: Change old instances from Azure Classic to Azure ARM
Date: Tuesday 19 September
Time: 6am-12pm UTC

For minimal disturbance, remember to always configure your clients to automatically reconnect on connection loss.
Please do a full reload (cmd-shift-r) if the management interface is not accessible after the upgrade has been completed.

If you can't allow any scheduled downtime we recommend you to move to a new dedicated cluster via queue federation, as explained here: https://www.cloudamqp.com/blog/2015-07-08-migrate-between-plans-rabbitmq-queue-federation.html

Read more about performance in Azure-ARM here: https://www.cloudamqp.com/blog/2016-11-08-better-performance-azure-arm.html

This ONLY affects servers Azure in Azure Classic (servers that were created before August 2017), i.e. servers that are still on the old underlying instance types.

Email us at support@cloudamqp.com if you have any question.
Posted Sep 18, 2017 - 11:54 UTC