In progress -
We have blocked all connections to shared cluster tiger. Please contact support@cloudamqp.com if you have any questions or need help creating/migrating to a new cluster.
May 2, 07:55 UTC
Scheduled - Shutdown of shared cluster tiger on April 30, 2022.
This cluster runs on legacy hardware and we have decided to shut it down. We have made newer clusters available in the same region so if you login into CloudAMQP and create a new shared account in the same region you will end up on a newer cluster automatically.
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 26, 10:42 UTC
Scheduled - For some clusters, the cloudamqp.com cluster hostname will change from "CNAME record" to "A record". After this change, inside VPC, the rmq.cloudamqp.com (or rmqN.cloudamqp.com) hostname will no longer resolve to the internal IP addresses of the cluster. If you are using VPC, you need to connect to the internal cluster hostname (in.cloudamqp.com or in.rmqN.cloudamqp.com), otherwise the external IP addresses will be used.
There should be no downtime or connection loss as your servers will keep the same IPs as before, only the DNS setup is changed.
This setup has been the default for new clusters on CloudAMQP and has proven to be better in many ways. Clients will know all the IP addresses of the cluster, and can re-connect to new nodes in the cluster faster. It also speeds up plan changes.
All affected customers have been notified with the exact maintenance time via email.
You can find the time for the maintenance, with the ability to reschedule in the CloudAMQP Console (per instance).