Verifying - Required work has been completed and host is back online. Additionally, all capsules should be running and we are currently verifying that deployments have resumed normal operations.
Apr 25, 14:19 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 25, 13:00 UTC
Scheduled - Beginning on at 13:00 UTC and ending at 14:00 UTC, scheduled maintenance will be performed for sl-us-dal-9-data.5.dblayer.com. This host and all capsules will be temporarily unavailable while the maintenance is being completed. Deployments using this host will remain operational. If you have questions about this maintenance, please contact support@compose.io.
Web Application ? Operational
REST API ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
Beginning on at 13:00 UTC and ending at 14:00 UTC, scheduled maintenance will be performed for sl-us-dal-9-data.7.dblayer.com. This host and all capsules will be temporarily unavailable while the maintenance is being completed. Deployments using this host will remain operational. If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 11, 15:05 UTC
During this period aws-eu-west-1-utility.1.dblayer.com will be taken offline. Deployments using this host will remain operational. If you have questions about this maintenance, please contact support@compose.io
Posted on Apr 25, 19:05 UTC
Past Incidents
Apr 26, 2017

No incidents reported today.

Apr 25, 2017
Completed - The scheduled maintenance has been completed.
Apr 25, 01:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 25, 00:00 UTC
Scheduled - During the this window the Digital Ocean networking team will be performing upgrades on networking hardware in LON1. This is pro-active maintenance to ensure optimal performance of the networking infrastructure and enable new features in the future.

Expected Impact: Digital Ocean expects the impact of this maintenance to be minimal, however; you may experience brief moments of increased latency and small amounts of packet loss lasting a maximum of between five and ten minutes.
Apr 17, 18:38 UTC
Apr 24, 2017

No incidents reported.

Apr 23, 2017

No incidents reported.

Apr 22, 2017

No incidents reported.

Apr 21, 2017
Resolved - This incident has been resolved.
Apr 21, 18:52 UTC
Identified - We have identified an issue with aws-eu-west-1-utility.0.dblayer.com which means it needs to be rebooted immediately. Customer deployments on our AWS eu-west-2 cluster should not be affected due to their HA design. Please contact support@compose.com if you are experiencing issues.
Apr 21, 15:31 UTC
Apr 20, 2017
Completed - The scheduled maintenance has been completed.
Apr 20, 14:41 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 20, 13:00 UTC
Scheduled - Beginning on at 13:00 UTC and ending at 13:00 UTC, scheduled maintenance will be performed for sl-us-dal-9-data.4.dblayer.com. This host and all capsules will be temporarily unavailable while the maintenance is being completed. Deployments using this host will remain operational. If you have questions about this maintenance, please contact support@compose.io.
Apr 11, 15:02 UTC
Apr 19, 2017
Completed - The scheduled maintenance has been completed.
Apr 19, 22:03 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 19, 19:00 UTC
Scheduled - During this period aws-us-east-1-utility.2.dblayer.com will be taken offline. Deployments using this host will remain operational. If you have questions about this maintenance, please contact support@compose.io
Apr 13, 14:23 UTC
Completed - All capsules are back online. If you continue to experience issues, please contact us at support@compose.io.
Apr 19, 15:11 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 19, 14:00 UTC
Scheduled - During this period aws-us-east-1-portal.9.dblayer.com will be taken offline. Customers with redundant portals will be unaffected. Customers with their sole portal on this host can add additional portals under the security settings of their deployments. If you have questions about this maintenance, please contact support@compose.io
Apr 13, 14:20 UTC
Apr 18, 2017
Completed - The scheduled maintenance has been completed.
Apr 18, 17:05 UTC
Verifying - All scheduled operations have been completed. We are now verifying that deployments using this host have recovered successfully.
Apr 18, 14:27 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 18, 13:00 UTC
Scheduled - Beginning on at 13:00 UTC and ending at 14:00 UTC, scheduled maintenance will be performed for sl-us-dal-9-data.0.dblayer.com. This host and all capsules will be temporarily unavailable while the maintenance is being completed. Deployments using this host will remain operational. If you have questions about this maintenance, please contact support@compose.io.
Apr 11, 15:00 UTC
Resolved - This incident should now be resolved. All capsules on the aws-us-east-1-memory.15 were restarted which re-established network connections with the other capsules in the deployments. Most deployments were then able to self-resolve their issues.

We've no more alerts for any deployments on aws-us-east-1-memory.15, but if you are still seeing issues please contact support@compose.io.
Apr 18, 11:18 UTC
Identified - We believe we've narrowed down the issue to the virtual networking layer on aws-us-east-1-memory.15. We are in the process of restarting capsules there to re-establish connections.
Apr 18, 10:50 UTC
Investigating - We are investigating networking issues on aws-us-east-1-memory hosts. We believe this is limited to the .13, .14 and .15 hosts. We'll update as we know more. This seems to have mostly impacted Redis deployments owing to the sentinels not being able to communicate properly.
Apr 18, 10:32 UTC
Resolved - This incident is now resolved.
Apr 18, 08:50 UTC
Monitoring - Service has been restored and we have been monitoring the situation. If you continue to experience issues, please contact us at support@compose.io.
Apr 18, 07:06 UTC
Investigating - We are looking into an issue with the host aws-eu-west-1-utility.2.dblayer.com. If you are having issues with your deployment, please contact support@compose.io. We apologize for the inconvenience.
Apr 18, 04:52 UTC
Apr 17, 2017
Resolved - The host is back online with all capsules running.
Apr 17, 14:39 UTC
Investigating - We are currently investigating an outage with gcp-us-east1-data.0.dblayer.com. Due to the high-availability nature of the Compose service, this should not result in deployment downtime.
Apr 17, 11:53 UTC
Apr 16, 2017

No incidents reported.

Apr 15, 2017

No incidents reported.

Apr 14, 2017

No incidents reported.

Apr 13, 2017
Resolved - We've monitored the host and it has remained stable since the last update. Setting this incident as resolved.
Apr 13, 10:53 UTC
Monitoring - The host is back online with all capsules running again. Owing to the proximity of this incident to the previous one we'll keep this incident open as monitoring.
Apr 13, 07:29 UTC
Investigating - This host is unavailable again, following the incident from earlier. We are investigating the issue. Since this was only recently rebooted there should have been no deployments using this as their primary.
Apr 13, 07:06 UTC
Resolved - The issue was identified and resolved. Unfortunately the host lighthouse.5 experienced an unplanned outage. If applications are developed to take advantage of replica sets they will be able to gracefully handle the step down of the primary node so that in the future, if a host should fail or if a routine stepdown event occurs (which is not uncommon as a result of transient cloud latency), your app can simply switch to reading and writing on the new primary within just a few seconds.
Apr 13, 01:22 UTC
Identified - A server appears to have become unreachable. We are rebooting this server now and will investigate the source of the outage when the server becomes available.
Apr 12, 23:51 UTC