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 "dinosaur", "woodpecker", "raven", "bee", "antelope", "barnacle", "ferret", and "toad" Sep 24, 20:30-22:30 UTC
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 Sep 20, 23:17 UTC
Past Incidents
Sep 21, 2020

No incidents reported today.

Sep 20, 2020

No incidents reported.

Sep 19, 2020

No incidents reported.

Sep 18, 2020

No incidents reported.

Sep 17, 2020
Upgrade of shared servers "porpoise", "otter", "buck", "duckbill", "flamingo", "chimpanzee", "wolverine", and "albatross"
Completed - The scheduled maintenance has been completed.
Sep 17, 21:27 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Sep 17, 20: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

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.
Sep 10, 22:17 UTC
Sep 16, 2020

No incidents reported.

Sep 15, 2020

No incidents reported.

Sep 14, 2020
Issue with metrics server
Resolved - The problem was identified and resolved. Metrics delivery is now running normally.
Sep 14, 20:27 UTC
Investigating - Metrics are currently not being delivered due to some problems with our metrics server. We are investigating the problem
Sep 14, 19:10 UTC
Sep 13, 2020

No incidents reported.

Sep 12, 2020

No incidents reported.

Sep 11, 2020

No incidents reported.

Sep 10, 2020
Upgrade of shared servers "gopher", "hound", "lark", "sheep", "white-swan", "golden-kangaroo", "buffalo", and "wombat"
Completed - The scheduled maintenance has been completed.
Sep 10, 22:15 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Sep 10, 20:38 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.
Sep 4, 04:23 UTC
Sep 9, 2020

No incidents reported.

Sep 8, 2020
Restart of shared server "owl"
Resolved - The underlying VM for Owl was restarted.
Sep 8, 15:30 UTC
Sep 7, 2020

No incidents reported.

← Incident History Powered by Statuspage