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

Messages in priority queues will not survive an upgrade between RabbitMQ version 3.6 to 3.7. It is therefore important that any messages in priority queues are consumed or that you move to a dedicated instance prior to this maintenance.
Posted on Aug 6, 21:56 UTC
Past Incidents
Aug 7, 2020

No incidents reported today.

Aug 6, 2020
Completed - The scheduled maintenance has been completed.
Aug 6, 22:10 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 6, 20:44 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

Messages in priority queues will not survive an upgrade between RabbitMQ version 3.6 to 3.7. It is therefore important that any messages in priority queues are consumed or that you move to a dedicated instance prior to this maintenance.
Jul 29, 22:10 UTC
Aug 5, 2020

No incidents reported.

Aug 4, 2020

No incidents reported.

Aug 3, 2020

No incidents reported.

Aug 2, 2020

No incidents reported.

Aug 1, 2020

No incidents reported.

Jul 31, 2020

No incidents reported.

Jul 30, 2020

No incidents reported.

Jul 29, 2020
Completed - The scheduled maintenance has been completed.
Jul 29, 22:06 UTC
Update - squid is done, we are still working on fish and wasp.
Jul 29, 20:50 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 29, 20:36 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

Messages in priority queues will not survive an upgrade between RabbitMQ version 3.6 to 3.7. It is therefore important that any messages in priority queues are consumed or that you move to a dedicated instance prior to this maintenance.
Jul 24, 01:50 UTC
Resolved - This incident has been resolved.
Jul 29, 17:06 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jul 17, 20:11 UTC
Identified - We're investigating an issue with some metrics reported missing.
Jul 17, 19:02 UTC
Jul 28, 2020

No incidents reported.

Jul 27, 2020

No incidents reported.

Jul 26, 2020

No incidents reported.

Jul 25, 2020

No incidents reported.

Jul 24, 2020
Completed - The scheduled maintenance has been completed.
Jul 24, 01:36 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 23, 20:36 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

Messages in priority queues will not survive an upgrade between RabbitMQ version 3.6 to 3.7. It is therefore important that any messages in priority queues are consumed or that you move to a dedicated instance prior to this maintenance.
Jul 16, 23:48 UTC