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
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Jun 1, 2020

No incidents reported today.

May 31, 2020

No incidents reported.

May 30, 2020
Resolved - We are resolving this incident as we haven't seen any new issues.
If you still have issues contact support.
May 30, 22:43 UTC
Monitoring - This should now be resolved for all servers.
Some servers using MQTT need to disable, and then enable the MQTT-plugin. That can be done from the CloudAMQP Control Panel -> Plugins.
May 30, 19:47 UTC
Update - Java 8 users need to import the USERTrust CA to the truststore: https://crt.sh/?id=1199354
May 30, 16:37 UTC
Identified - One of the chains of the cross-signed certificate we use has expired. Most clients won't need to do anything, as clients should evaluate all chains. But older versions of Ruby, Node.js and Java might have problems.

We have removed the expired chain from all certificates.

More info available here: https://support.sectigo.com/Com_KnowledgeDetailPage?Id=kA03l00000117LT
May 30, 15:50 UTC
May 29, 2020

No incidents reported.

May 28, 2020
Completed - We will have to re-schedule this upgrade for a later date.
May 28, 20:09 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 28, 20:00 UTC
Scheduled - We will upgrade RabbitMQ and Erlang versions on the shared server "white-mynah-bird". We will also adjust the underlying hardware to more modern. This requires all queues you want to keep messages in to have a HA-policy with automatic queue syncing.

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
May 26, 21:51 UTC
May 27, 2020

No incidents reported.

May 26, 2020

No incidents reported.

May 25, 2020

No incidents reported.

May 24, 2020

No incidents reported.

May 23, 2020

No incidents reported.

May 22, 2020

No incidents reported.

May 21, 2020
Completed - We will have to postpone this maintenance for one week.
May 21, 20:27 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 21, 20:00 UTC
Scheduled - We will upgrade RabbitMQ and Erlang versions on the shared server "white-mynah-bird". We will also adjust the underlying hardware to more modern. This requires all queues you want to keep messages in to have a HA-policy with automatic queue syncing.

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
May 19, 03:18 UTC
May 20, 2020

No incidents reported.

May 19, 2020

No incidents reported.

May 18, 2020

No incidents reported.