CloudAMQP Status

All Systems Operational

Shared servers Operational

Dedicated servers Operational

Backend Operational

Metrics Operational

Heroku Operational

AWS route53 Operational

Help Scout Email Processing Operational

AWS ec2-ap-northeast-1 Operational

AWS ec2-ap-northeast-2 Operational

AWS ec2-ap-southeast-1 Operational

AWS ec2-ap-southeast-2 Operational

AWS ec2-ca-central-1 Operational

AWS ec2-eu-central-1 Operational

AWS ec2-eu-west-1 Operational

AWS ec2-eu-west-2 Operational

AWS ec2-eu-west-3 Operational

AWS ec2-sa-east-1 Operational

AWS ec2-us-east-1 Operational

AWS ec2-us-east-2 Operational

AWS ec2-us-gov-west-1 Operational

AWS ec2-us-west-1 Operational

AWS ec2-us-west-2 Operational

Google Cloud Platform Google Compute Engine Operational

Operational

Degraded Performance

Partial Outage

Major Outage

Maintenance

Scheduled Maintenance

Upgrade of shared servers "fox", "hornet", "lemur", "fish", "salamander","spotted-monkey","turtle", "baboon" Nov 12, 19:30-20:30 UTC

We will be undergoing scheduled maintenance during this time.
Posted on Oct 29, 23:03 UTC

Past Incidents

Oct 30, 2020

No incidents reported today.

Oct 29, 2020

Upgrade of shared servers "white-mynah-bird", "black-boar", "orangutan","wildboar","jellyfish","jaguar","eagle","clam"

Completed - The scheduled maintenance has been completed.
Oct 29, 20:15 UTC

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 29, 19:35 UTC

Scheduled - We will be undergoing scheduled maintenance during this time.
Oct 22, 20:15 UTC

Oct 28, 2020

No incidents reported.

Oct 27, 2020

No incidents reported.

Oct 26, 2020

No incidents reported.

Oct 25, 2020

CloudAMQP log server is sporadically failing

Resolved - Log system is fully operational
Oct 25, 19:50 UTC

Monitoring - Load has been reduced on the server, and it appears to have stabilized. We are continuing to monitor the performance.
Oct 25, 18:24 UTC

Investigating - The CloudAMQP log system is sporadically unresponsive. This is preventing messages from being shoveled from the logstream queue on the root vhost of customer's RabbitMQ brokers. Customers with dedicated instances might see buildup of messages in that queue and may not see current log entries on the CloudAMQP console.
Oct 25, 17:45 UTC

Oct 24, 2020

No incidents reported.

Oct 23, 2020

No incidents reported.

Oct 22, 2020

Upgrade of shared servers "macaw", "hare", "owl", "hedgehog", "hawk", "gull", "ferret ", and "cougar"

Completed - The scheduled maintenance has been completed.
Oct 22, 20:08 UTC

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 22, 19:30 UTC

Scheduled - We will upgrade RabbitMQ and Erlang versions on some of the shared servers.

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
Oct 15, 20:43 UTC

Oct 21, 2020

No incidents reported.

Oct 20, 2020

No incidents reported.

Oct 19, 2020

No incidents reported.

Oct 18, 2020

No incidents reported.

Oct 17, 2020

No incidents reported.

Oct 16, 2020

We're currently experiencing issues with metrics delivery, this affects all integrations

Resolved - This incident has been resolved.
Oct 16, 03:47 UTC

Update - After investigation the integrations have not been affected by this.
Oct 16, 00:33 UTC

Monitoring - A fix has been implemented and we are monitoring the results.
Oct 16, 00:33 UTC

Investigating - We are currently investigating this issue.
Oct 15, 23:19 UTC