CloudAMQP Status

Shutdown of shared cluster tiger on April 30, 2022

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.

Dedicated clusters: DNS change

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).

Uptime over the past 90 days. View historical uptime.

Shared servers Operational

Dedicated servers Operational

Backend Operational

Metrics Operational

90 days ago

99.99 % uptime

Today

Heroku Operational

DNS Operational

Help Scout Email Processing Operational

AWS Operational

90 days ago

100.0 % uptime

Today

AWS ec2-ap-northeast-1 Operational

90 days ago

100.0 % uptime

Today

AWS ec2-us-west-2 Operational

90 days ago

100.0 % uptime

Today

AWS ec2-us-west-1 Operational

90 days ago

100.0 % uptime

Today

AWS ec2-us-east-2 Operational

90 days ago

100.0 % uptime

Today

AWS ec2-us-east-1 Operational

90 days ago

100.0 % uptime

Today

AWS ec2-sa-east-1 Operational

90 days ago

100.0 % uptime

Today

AWS ec2-eu-west-3 Operational

90 days ago

100.0 % uptime

Today

AWS ec2-eu-west-2 Operational

90 days ago

100.0 % uptime

Today

AWS ec2-eu-west-1 Operational

90 days ago

100.0 % uptime

Today

AWS ec2-eu-central-1 Operational

90 days ago

100.0 % uptime

Today

AWS ec2-ca-central-1 Operational

90 days ago

100.0 % uptime

Today

AWS ec2-ap-southeast-2 Operational

90 days ago

100.0 % uptime

Today

AWS ec2-ap-southeast-1 Operational

90 days ago

100.0 % uptime

Today

AWS ec2-ap-northeast-2 Operational

90 days ago

100.0 % uptime

Today

AWS ec2-me-south-1 Operational

90 days ago

100.0 % uptime

Today

AWS ec2-eu-south-1 Operational

90 days ago

100.0 % uptime

Today

AWS ec2-eu-north-1 Operational

90 days ago

100.0 % uptime

Today

AWS ec2-ap-south-1 Operational

90 days ago

100.0 % uptime

Today

AWS ec2-ap-east-1 Operational

90 days ago

100.0 % uptime

Today

AWS ec2-af-south-1 Operational

90 days ago

100.0 % uptime

Today

Google Cloud Platform Google Compute Engine Operational

90 days ago

100.0 % uptime

Today

DigitalOcean Operational

90 days ago

100.0 % uptime

Today

DigitalOcean AMS2 Operational

90 days ago

100.0 % uptime

Today

DigitalOcean AMS3 Operational

90 days ago

100.0 % uptime

Today

DigitalOcean FRA1 Operational

90 days ago

100.0 % uptime

Today

DigitalOcean LON1 Operational

90 days ago

100.0 % uptime

Today

DigitalOcean NYC2 Operational

90 days ago

100.0 % uptime

Today

DigitalOcean NYC3 Operational

90 days ago

100.0 % uptime

Today

DigitalOcean SFO1 Operational

90 days ago

100.0 % uptime

Today

DigitalOcean SGP1 Operational

90 days ago

100.0 % uptime

Today

DigitalOcean TOR1 Operational

90 days ago

100.0 % uptime

Today

Microsoft Azure Operational

90 days ago

99.98 % uptime

Today

Operational

Degraded Performance

Partial Outage

Major Outage

Maintenance

Scheduled Maintenance

Shared servers RabbitMQ + Erlang upgrade May 19, 20:30-21:30 UTC

We will be undergoing scheduled maintenance on the below servers to upgrade RabbitMQ and Erlang versions. This will lead to some downtime on the affected servers.

llama-01.rmq.cloudamqp.com
skunk-01.rmq.cloudamqp.com
clam-01.rmq.cloudamqp.com
jellyfish-01.rmq.cloudamqp.com
shark-01.rmq.cloudamqp.com
puma-01.rmq.cloudamqp.com
spider-01.rmq.cloudamqp.com
antelope-01.rmq.cloudamqp.com
hawk-01.rmq.cloudamqp.com
gopher-01.rmq.cloudamqp.com
chimpanzee-01.rmq.cloudamqp.com
impala-01.rmq.cloudamqp.com
hare-01.rmq.cloudamqp.com
crane-01.rmq.cloudamqp.com
jaguar-01.rmq.cloudamqp.com
lion-01.rmq.cloudamqp.com
bee-01.rmq.cloudamqp.com
barnacle-01.rmq.cloudamqp.com
toad-01.rmq.cloudamqp.com
beaver-01.rmq.cloudamqp.com
Posted on May 12, 21:10 UTC

Past Incidents

May 18, 2022

No incidents reported today.

May 17, 2022

CloudAMQP RabbitMQ clusters in Azure South Africa North my be unreachable

Resolved - Most clusters were automatically restarted once Azure resolved the issue on their end. We had to manually restart a few nodes. But now clusters are all online.
May 17, 21:02 UTC

Investigating - We are investigating how to mitigate. Azure's statement about the incident is this:

Impact Statement: Starting at 19:21 UTC on 17 May 2022, you have been identified as a customer using Virtual Machines in South Africa North who may experience connection failures when trying to access some Virtual Machines hosted in the region. These Virtual Machines may have also restarted unexpectedly.

Current Status: We are aware of this issue and are actively investigating. The next update will be provided within 60 minutes.
May 17, 20:08 UTC

Issues creating shared instances (plans Lemur, Tiger) at the moment - we are looking into this.

Resolved - This incident has been resolved.
May 17, 15:39 UTC

Investigating - We are currently investigating this issue.
May 17, 15:14 UTC

May 16, 2022

No incidents reported.

May 15, 2022

No incidents reported.

May 14, 2022

No incidents reported.

May 13, 2022

No incidents reported.

May 12, 2022

Shared servers RabbitMQ + Erlang update

Completed - The scheduled maintenance has been completed.
May 12, 21:04 UTC

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 12, 20:30 UTC

Scheduled - We will be undergoing scheduled maintenance on the below servers to update RabbitMQ and Erlang. This will lead to some downtime on the affected servers.

Servers:
hummingbird-01.rmq.cloudamqp.com
codfish-01.rmq.cloudamqp
gerbil-01.rmq.cloudamqp.com
crow-01.rmq.cloudamqp.com
dingo-01.rmq.cloudamqp.com
armadillo-01.rmq.cloudamqp.com
stingray-01.rmq.cloudamqp.com
roedeer-01.rmq.cloudamqp.com
wolf-01.rmq.cloudamqp.com
finch-01.rmq.cloudamqp.com
coyote-01.rmq.cloudamqp.com
bonobo-01.rmq.cloudamqp.com
sparrow-01.rmq.cloudamqp.com
moose-01.rmq.cloudamqp.com
whale-01.rmq.cloudamqp.com
rhino-01.rmq.cloudamqp.com
May 6, 01:54 UTC

May 11, 2022

No incidents reported.

May 10, 2022

No incidents reported.

May 9, 2022

No incidents reported.

May 8, 2022

No incidents reported.

May 7, 2022

No incidents reported.

May 6, 2022

No incidents reported.

May 5, 2022

We will be performing scheduled maintenance on shared server "peacock"

Completed - The scheduled maintenance has been completed.
May 5, 20:48 UTC

Verifying - Verification is currently underway for the maintenance items.
May 5, 20:39 UTC

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 5, 20:31 UTC

Scheduled - We will be undergoing scheduled maintenance during this time.
May 3, 22:40 UTC

May 4, 2022

No incidents reported.

Related