All Systems Operational
Web Application   ? Operational
REST API   ? Operational
Softlayer aus-sydney-1 Region Operational
Softlayer aus-sydney-1 Region Clusters   Operational
Softlayer eu-frankfurt-2 Region Operational
Softlayer eu-frankfurt-2 Region Clusters   Operational
Softlayer eu-london-2 Region Operational
Softlayer eu-london-2 Region   Operational
Softlayer us-dallas-09 Region Operational
Softlayer us-dallas-9 Region Clusters   Operational
sl-us-dal-9-portal.4.dblayer.com   Operational
Softlayer us-south-1 Region Operational
Softlayer us-south-1 Region Clusters   Operational
AWS ap-southeast-2 Region Operational
AWS ap-southeast-2 Region Clusters   ? Operational
AWS eu-west-1 Region Operational
AWS eu-west-1 Region Clusters   ? Operational
AWS us-east-1 Region Operational
AWS us-east-1 Region Clusters   ? Operational
AWS us-west-2 Region Operational
AWS us-west-2 Region Clusters   ? Operational
Google Cloud us-east-1 Region Operational
Google Cloud us-east-1 Region Clusters   Operational
Softlayer us-east-1 Region Operational
Softlayer us-east-1 Region Clusters   Operational
AWS eu-central-1 Region Operational
AWS eu-central-1 Region Clusters   Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
Beginning at 2018-04-25 0000 UTC and ending at 2018-04-25 0300 UTC, scheduled maintenance will be performed on sl-eu-fra-2-portal.2.dblayer.com, sl-eu-lon-2-portal.2.dblayer.com, aws-eu-central-1-portal.2.dblayer.com, and aws-eu-west-1-portal.0.dblayer.com. These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.

In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).

We estimate that the maintenance on each host will take 1 hour.

If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 20:32 UTC
Beginning at 2018-04-25 0300 UTC and ending at 2018-04-25 0600 UTC, scheduled maintenance will be performed on sl-us-dal-9-portal.1.dblayer.com, sl-us-south-1-portal.0.dblayer.com, sl-us-south-1-portal.11.dblayer.com, sl-us-south-1-portal.14.dblayer.com, and sl-us-south-1-portal.17.dblayer.com. These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.

In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).

We estimate that the maintenance on each host will take 1 hour.

If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 20:49 UTC
Beginning at 2018-04-25 0600 UTC and ending at 2018-04-25 0900 UTC, scheduled maintenance will be performed on sl-us-dal-9-portal.2.dblayer.com, sl-us-south-1-portal.18.dblayer.com, sl-us-south-1-portal.21.dblayer.com, sl-us-south-1-portal.5.dblayer.com, and sl-us-south-1-portal.8.dblayer.com. These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.

In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).

We estimate that the maintenance on each host will take 1 hour.

If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 20:57 UTC
Beginning at 2018-04-25 0900 UTC and ending at 2018-04-25 1200 UTC, scheduled maintenance will be performed on sl-aus-syd-1-portal.2.dblayer.com and aws-ap-southeast-1-portal.0.dblayer.com. These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.

In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).

We estimate that the maintenance on each host will take 1 hour.

If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 21:01 UTC
Beginning at 2018-04-25 1500 UTC and ending at 2018-04-25 1800 UTC, scheduled maintenance will be performed sl-aus-syd-1-portal.3.dblayer.com and aws-ap-southeast-1-portal.1.dblayer.com. These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.

In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).

We estimate that the maintenance on each host will take 1 hour.

If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 21:10 UTC
Beginning at 2018-04-25 2100 UTC and ending at 2018-04-26 0000 UTC, scheduled maintenance will be performed sl-eu-fra-2-portal.3.dblayer.com, sl-eu-lon-2-portal.1.dblayer.com, aws-ap-southeast-1-portal.2.dblayer.com, aws-eu-central-1-portal.2.dblayer.com, and aws-eu-west-1-portal.1.dblayer.com. These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.

In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).

We estimate that the maintenance on each host will take 1 hour.

If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 21:17 UTC
Beginning at 2018-04-26 0000 UTC and ending at 2018-04-26 0300 UTC, scheduled maintenance will be performed on sl-eu-lon-2-portal.3.dblayer.com, aws-eu-west-1-portal.2.dblayer.com, sl-eu-fra-2-memory.0.dblayer.com, aws-eu-west-1-portal.7.dblayer.com, and aws-eu-west-1-portal.9.dblayer.com. These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.

In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).

We estimate that the maintenance on each host will take 1 hour.

If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 21:29 UTC
Beginning at 2018-04-26 0300 UTC and ending at 2018-04-26 0600 UTC, scheduled maintenance will be performed sl-us-dal-9-portal.3.dblayer.com, sl-us-south-1-portal.1.dblayer.com, sl-us-south-1-portal.10.dblayer.com, sl-us-south-1-portal.13.dblayer.com, and sl-us-south-1-portal.16.dblayer.com. These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.

In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).

We estimate that the maintenance on each host will take 1 hour.

If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 21:24 UTC
Beginning at 2018-04-26 0600 UTC and ending at 2018-04-26 0900 UTC, scheduled maintenance will be performed on sl-us-dal-9-portal.4.dblayer.com, sl-us-south-1-portal.4.dblayer.com, sl-us-south-1-portal.7.dblayer.com, aws-us-east-1-portal.24.dblayer.com, and aws-us-east-1-portal.27.dblayer.com. These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.

In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).

We estimate that the maintenance on each host will take 1 hour.

If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 21:32 UTC
Beginning at 2018-04-26 1200 UTC and ending at 2018-04-26 1500 UTC, scheduled maintenance will be performed on sl-aus-syd-1-memory.1.dblayer.com and aws-ap-southeast-1-memory.0.dblayer.com. These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.

In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).

We estimate that the maintenance on each host will take 1 hour.

If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 22:44 UTC
Beginning at 2018-04-26 1500 UTC and ending at 2018-04-26 1800 UTC, scheduled maintenance will be performed on sl-aus-syd-1-memory.2.dblayer.com and aws-ap-southeast-1-memory.1.dblayer.com. These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.

In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).

We estimate that the maintenance on each host will take 1 hour.

If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 22:57 UTC
Beginning at 2018-04-26 2100 UTC and ending at 2018-04-27 0000 UTC, scheduled maintenance will be performed on aws-eu-west-1-portal.3.dblayer.com, sl-eu-lon-2-portal.4.dblayer.com, sl-eu-fra-2-memory.5.dblayer.com, aws-eu-central-1-memory.1.dblayer.com, and aws-eu-west-1-portal.2.dblayer.com. These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.

In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).

We estimate that the maintenance on each host will take 1 hour.

If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 22:59 UTC
Beginning at 2018-04-27 0000 UTC and ending at 2018-04-27 0300 UTC, scheduled maintenance will be performed on aws-eu-west-1-portal.4.dblayer.com, sl-eu-lon-2-portal.5.dblayer.com, sl-eu-fra-2-memory.1.dblayer.com, aws-eu-central-1-memory.2.dblayer.com, aws-eu-west-1-portal.8.dblayer.com. These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.

In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).

We estimate that the maintenance on each host will take 1 hour.

If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 21:53 UTC
Beginning at 2018-04-27 0300 UTC and ending at 2018-04-27 0600 UTC, scheduled maintenance will be performed on sl-us-dal-9-portal.5.dblayer.com, aws-us-east-1-portal.31.dblayer.com, aws-us-east-1-portal.4.dblayer.com, aws-us-east-1-portal.6.dblayer.com, aws-us-east-1-portal.11.dblayer.com. These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.

In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).

We estimate that the maintenance on each host will take 1 hour.

If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 21:59 UTC
Beginning at 2018-04-27 0600 UTC and ending at 2018-04-27 0900 UTC, scheduled maintenance will be performed on sl-us-dal-9-portal.6.dblayer.com, aws-us-east-1-portal.7.dblayer.com, aws-us-east-1-portal.12.dblayer.com, aws-us-east-1-portal.17.dblayer.com, aws-us-east-1-portal.19.dblayer.com. These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.

In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).

We estimate that the maintenance on each host will take 1 hour.

If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 22:05 UTC
Beginning at 2018-04-27 1200 UTC and ending at 2018-04-27 1500 UTC, scheduled maintenance will be performed on sl-aus-syd-1-memory.3.dblayer.com, aws-ap-southeast-1-memory.2.dblayer.com. These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.

In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).

We estimate that the maintenance on each host will take 1 hour.

If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 22:08 UTC
Beginning at 2018-04-27 1500 UTC and ending at 2018-04-27 1800 UTC, scheduled maintenance will be performed on sl-aus-syd-1-data.0.dblayer.com, aws-ap-southeast-1-data.0.dblayer.com. These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.

In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).

We estimate that the maintenance on each host will take 1 hour.

If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 22:12 UTC
Beginning at 2018-04-27 2100 UTC and ending at 2018-04-27 2300 UTC, scheduled maintenance will be performed on sl-eu-lon-2-portal.6.dblayer.com, sl-eu-fra-2-memory.4.dblayer.com, aws-eu-central-data.5.dblayer.com, aws-eu-west-1-portal.10.dblayer.com, aws-eu-west-1-portal.5.dblayer.com. These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.

In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).

We estimate that the maintenance on each host will take 1 hour.

If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 22:18 UTC
Beginning at 2018-04-28 0000 UTC and ending at 2018-04-28 0300 UTC, scheduled maintenance will be performed on sl-us-dal-9-portal.7.dblayer.com, aws-us-east-1-portal.21.dblayer.com, aws-us-west-2-portal.0.dblayer.com, aws-us-east-1-portal.0.dblayer.com, aws-us-east-1-portal.2.dblayer.com, sl-eu-lon-portal.7.dblayer.com. These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.

In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).

We estimate that the maintenance on each host will take 1 hour.

If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 22:32 UTC
Past Incidents
Apr 22, 2018

No incidents reported today.

Apr 21, 2018

No incidents reported.

Apr 20, 2018

No incidents reported.

Apr 19, 2018
Resolved - This incident has been resolved.
Apr 19, 13:04 UTC
Update - lamppost.18.mongolayer.com maintenance is complete.
Apr 18, 20:10 UTC
Monitoring - The scheduled maintenance has been started for lamppost.16.mongolayer.com and lamppost.18.mongolayer.com.
Apr 18, 19:00 UTC
Completed - The scheduled maintenance has been completed.
Apr 19, 08:30 UTC
Verifying - Both hosts and all capsules are now back online. We are working through any remaining alerts to ensure deployments are returned to full health.
Apr 19, 08:23 UTC
Update - The memory.5 host and all capsules are back up and running. The memory.2 host is starting back up now.
Apr 19, 08:07 UTC
Update - Hosts are now down for maintenance.
Apr 19, 07:05 UTC
Update - Capsules are now shutdown.
Apr 19, 06:42 UTC
Update - We've started failing over all Redis deployments. Then we'll shutdown capsules in preparation for a hardware uprgade.
Apr 19, 06:33 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 19, 06:30 UTC
Scheduled - Beginning at 2018-04-19 0630 UTC and ending at 2018-04-19 1030 UTC, scheduled maintenance will be performed for sl-eu-fra-2-memory.2.dblayer.com and sl-eu-fra-2-memory.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.
Apr 17, 16:22 UTC
Resolved - This incident has been resolved.
Apr 19, 06:43 UTC
Monitoring - All capsules are now back online. We are working through remaining alerts to ensure deployments return to full health.
Apr 19, 06:21 UTC
Identified - Host and capsules are coming back online now.
Apr 19, 06:11 UTC
Investigating - Beginning immediately Compose will be performing necessary maintenance to aws-us-east-1-data.32.dblayer.com. During this time, deployments using this host should remain operational and your databases should failover as intended. If you have questions about this maintenance, please contact support@compose.io so we can answer your questions.
Apr 19, 05:47 UTC
Apr 18, 2018
Resolved - lamppost.14.mongolayer.com maintenance has been completed.
Apr 18, 19:38 UTC
Update - lamppost.12.mongolayer.com maintenance has been completed.
Apr 18, 18:17 UTC
Update - lamppost.10.mongolayer.com maintenance has been completed.
Apr 18, 16:01 UTC
Monitoring - The scheduled maintenance has been started for lamppost.10.mongolayer.com, lamppost.12.mongolayer.com and lamppost.14.mongolayer.com.
Apr 18, 14:01 UTC
Completed - The scheduled maintenance has been completed.
Apr 18, 18:15 UTC
Verifying - Hosts and capsules are now back up and running. We are working through any remaining alerts to ensure deployments are returned to full health.
Apr 18, 18:04 UTC
Update - All capsules are back up and running on the .1 host. Starting to bring the .4 host back online now.
Apr 18, 17:55 UTC
Update - Hardware upgrade has been completed. Starting to bring the host .1 back online first.
Apr 18, 17:39 UTC
Update - Hosts are now down for a hardware upgrade.
Apr 18, 15:57 UTC
Update - We’ve started failing over Redis deployments and shutting down capsules in preparation for a hardware upgrade.
Apr 18, 14:40 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 18, 14:30 UTC
Scheduled - Beginning at 2018-04-18 1430 UTC and ending at 2018-04-18 1830 UTC, scheduled maintenance will be performed for sl-eu-fra-2-memory.1.dblayer.com and sl-eu-fra-2-memory.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 17, 16:22 UTC
Completed - sl-us-south-1-portal.2.dblayer.com has finished the maintenance. This maintenance event is now complete. Please contact us at support@compose.io if you have any issues.
Apr 18, 15:49 UTC
Update - The maintenance for sl-us-south-1-portal.12.dblayer.com and sl-us-south-1-portal.15.dblayer.com are both completed. The final host, sl-us-south-1-portal.2.dblayer.com, is nearing completion.
Apr 18, 15:23 UTC
Update - sl-us-south-1-portal.3.dblayer.com maintenance has been completed.
Apr 18, 15:03 UTC
Update - Maintenance on sl-us-south-1-portal.20.dblayer.com has been completed.
Apr 18, 14:59 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 18, 13:00 UTC
Scheduled - During this required maintenance window, this host and all capsules will be temporarily unavailable. Customers with redundant ports will be unaffected as long as their applications are configured to use or failover to the other portals. Customers with these portals as their sole portal for their deployment can add additional portals under the security settings for their deployments. If you have questions about this maintenance, please contact support@compose.io
Apr 16, 18:13 UTC
Completed - The maintenance on sl-eu-lon-2-portal.0.dblayer.com is completed. All hosts affected by this maintenance are now back online and service should be fully restored. Please contact support@compose.io if you experience any issues.
Apr 18, 13:46 UTC
Update - The sl-aus-syd-1-portal.1.dblayer.com maintenance has been completed. The sl-eu-lon-2-portal.0.dblayer.com maintenance is nearing completion and service restoration should be available for most customers.
Apr 18, 12:59 UTC
Update - Maintenance on sl-eu-fra-2-portal.0.dblayer.com has been completed.
Apr 18, 11:16 UTC
Update - Maintenance on aws-eu-central-1-portal.0.dblayer.com and sl-us-dal-9-portal.0.dblayer.com is completed. The other three hosts are nearing completion and service should be slowly restored for portal capsules on the remaining hosts.
Apr 18, 11:15 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 18, 10:00 UTC
Scheduled - During this required maintenance window, this host and all capsules will be temporarily unavailable. Customers with redundant ports will be unaffected as long as their applications are configured to use or failover to the other portals. Customers with these portals as their sole portal for their deployment can add additional portals under the security settings for their deployments. If you have questions about this maintenance, please contact support@compose.io
Apr 16, 18:09 UTC
Resolved - This incident has been resolved.
Apr 18, 13:38 UTC
Monitoring - All capsules are back up and running. We are checking through alerts to ensure deployments return to full health.
Apr 18, 11:48 UTC
Update - Capsules are being restarted.
Apr 18, 11:23 UTC
Identified - Beginning immediately Compose will be performing necessary maintenance to sl-eu-lon-2-data.3.dblayer.com to fix some networking issues. During this time, deployments using this host should remain operational and your databases should failover as intended.
Apr 18, 10:52 UTC
Completed - The scheduled maintenance has been completed.
Apr 18, 09:23 UTC
Verifying - Hardware upgrade completed. Host and all capsules are back up and running. We are checking through alerts to ensure all deployments return to full health.
Apr 18, 08:51 UTC
Update - Hosts are now down for maintenance.
Apr 18, 07:13 UTC
Update - We are failing over the Redis deployments on memory.0 and memory.3 and beginning a shutdown of capsules in preparation for a hardware upgrade on these hosts.
Apr 18, 06:39 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 18, 06:30 UTC
Scheduled - Beginning on at 2018-04-18 0630 UTC and ending at 2018-04-18 1030 UTC, scheduled maintenance will be performed for sl-eu-fra-2-memory.0.dblayer.com and sl-eu-fra-2-memory.3.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 17, 16:22 UTC
Apr 17, 2018
Resolved - This incident has been resolved.
Apr 17, 20:14 UTC
Monitoring - The scheduled maintenance has been started for lamppost.15.mongolayer.com.
Apr 17, 19:01 UTC
Resolved - This incident has been resolved.
Apr 17, 14:46 UTC
Monitoring - The scheduled maintenance has been started for lamppost.11.mongolayer.com.
Apr 17, 14:01 UTC
Resolved - This incident has been resolved.
Apr 17, 14:46 UTC
Monitoring - The scheduled maintenance has been started for lamppost.19.mongolayer.com.
Apr 17, 14:02 UTC
Resolved - This incident has been resolved.
Apr 17, 08:02 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 17, 00:48 UTC
Investigating - We are currently investigating the outage with sl-eu-lon-2-data.6.dblayer.com that is part of the cluster in IBM Cloud/Softlayer at the London-02 datacenter.
Apr 16, 18:39 UTC
Resolved - This incident has been resolved.
Apr 17, 00:48 UTC
Monitoring - The scheduled maintenance has been started for lamppost.17.mongolayer.com.
Apr 16, 19:07 UTC
Apr 16, 2018
Resolved - This incident has been resolved.
Apr 16, 20:02 UTC
Monitoring - The scheduled maintenance has been started for lamppost.13.mongolayer.com.
Apr 16, 19:01 UTC
Resolved - This incident has been resolved.
Apr 16, 16:55 UTC
Monitoring - The scheduled maintenance has been started for lamppost.7.mongolayer.com.
Apr 16, 14:01 UTC
Resolved - This incident has been resolved.
Apr 16, 16:55 UTC
Monitoring - The scheduled maintenance has been started for lamppost.9.mongolayer.com.
Apr 16, 14:27 UTC
Apr 15, 2018
Resolved - This incident has been resolved.
Apr 15, 13:18 UTC
Monitoring - All capsules on data.3 have been restarted. We are checking through alerts to ensure deployments return to full health.
Apr 15, 11:26 UTC
Identified - data.3 host is back up. We are restarting capsules.
Apr 15, 11:07 UTC
Update - We are shutting down capsules on data.3 in order to reboot the host.
Apr 15, 10:41 UTC
Investigating - We are investigating networking related issues affecting deployments on these hosts.
Apr 15, 09:48 UTC
Apr 14, 2018

No incidents reported.

Apr 13, 2018
Resolved - This incident has been resolved.
Apr 13, 21:32 UTC
Monitoring - The host capital.3.mongolayer.com is currently undergoing required maintenance. If configured correctly, your applications and services should have failed over to the remaining healthy member. If you are having trouble, please consult the following article: https://www.compose.com/articles/support-desk-keeping-mongodb-live/
Apr 13, 15:16 UTC
Resolved - This incident has been resolved.
Apr 13, 16:15 UTC
Monitoring - The scheduled maintenance has been started for lamppost.2.mongolayer.com.
Apr 13, 14:02 UTC
Resolved - This incident has been resolved.
Apr 13, 15:19 UTC
Monitoring - Capsules have been recreated and deployments should be returning to full health. We are working through the remaining alerts and will resolve this issue when we believe things are 100%
Apr 13, 13:28 UTC
Identified - The host is up and running and our operations team is working to get things fully operational, extensive work is required on the host.
Apr 13, 12:05 UTC
Investigating - We are investigating an unplanned outage with the aws-us-east-1-data.2.dblayer.com host. Updates to follow.
Apr 13, 11:11 UTC
Apr 12, 2018
Resolved - This incident has been resolved.
Apr 12, 15:21 UTC
Monitoring - The scheduled maintenance has been started for lamppost.1.mongolayer.com.
Apr 12, 14:41 UTC
Resolved - This incident has been resolved.
Apr 12, 15:21 UTC
Monitoring - The scheduled maintenance has been started for lamppost.3.mongolayer.com.
Apr 12, 14:03 UTC
Apr 11, 2018
Resolved - This has now been resolved and LE certificate installation should now succeed as normal. If you’re still having trouble, please reach out to support@compose.io
Apr 11, 16:03 UTC
Identified - Our Let's Encrypt certificate issuance queue is backed up and new certificate installs will likely fail. This issue should be resolved within the hour. We will continue to update on the status here.
Apr 11, 14:02 UTC
Resolved - The hosts are online and all capsules have been started. Please contact us at support@compose.io if your deployment is having issues.
Apr 11, 15:09 UTC
Monitoring - The scheduled maintenance has been started for both lamppost.6.mongolayer.com and lamppost.8.mongolayer.com.
Apr 11, 14:00 UTC
Resolved - The host is healthy and all MongoDB capsules are up and running. Please reach out to support@compose.io if you are still experiencing trouble.
Apr 11, 13:12 UTC
Update - If configured correctly, your applications and services should have failed over to the remaining healthy member. If you are having trouble, please consult the following article: https://www.compose.com/articles/support-desk-keeping-mongodb-live/

If you still require assistance, please reach out to support@compose.io
Apr 11, 12:29 UTC
Identified - The host is back online and we are working to ensure all MongoDB capsules are running and healthy.
Apr 11, 12:27 UTC
Investigating - We're currently investigating an unplanned outage with the cockney.0.mongolayer.com host in Digital Ocean LON1
Apr 11, 12:20 UTC
Apr 10, 2018
Resolved - The host is online and all capsules have been started. Please contact us at support@compose.io if your deployment is having issues.
Apr 10, 15:24 UTC
Monitoring - The scheduled maintenance has been started for both lamppost.0.mongolayer.com and lamppost.5.mongolayer.com.
Apr 10, 14:04 UTC
Apr 9, 2018
Resolved - This incident has been resolved.
Apr 9, 22:58 UTC
Monitoring - All DNS records have been updated and normal operations should be resuming momentarily.
Apr 9, 17:43 UTC
Identified - We are currently in the process of rebuilding the host. Capsules have been created and DNS is being updated to reflect the host. If you have questions please contact us at support@compose.io.
Apr 9, 17:11 UTC
Investigating - We are currently investigating the outage withaws-eu-west-1-portal.4.dblayer.com- AWS - eu-west-1
Apr 9, 15:02 UTC
Resolved - We resolved the issue with the Compose.com UI being unable to browse the data in MongoDB deployments. Deployments themselves were not impacted by this outage. This was purely a UI issue.
Apr 9, 19:08 UTC
Investigating - Attempting to use the Compose.com user interface to browser data in MongoDB deployments is temporarily unavailable. This does not impact the availability of your data. MongoDB deployments are unaffected. This is purely a UI issue with Compose.com.
Apr 9, 16:09 UTC
Completed - The scheduled maintenance has been completed.
Apr 9, 16:59 UTC
Verifying - The host is back online and all capsules have been started.
Apr 9, 15:51 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 9, 14:00 UTC
Scheduled - Beginning on at 14:00 UTC and ending at 16:00 UTC, scheduled maintenance will be performed for candidate.43.mongolayer.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 3, 13:35 UTC
Apr 8, 2018
Resolved - This incident has been resolved.
Apr 8, 08:26 UTC
Update - That's nearly all alerts worked through now. Still leaving as monitoring, but marking the host as operational.
Apr 8, 02:32 UTC
Monitoring - All capsules have now been re-created. Depending on the size of the deployment is how long it'll take for the member to resync and transition to SECONDARY. We'll leave this incident in monitoring status until we've confirmed all deployments are in full health.
Apr 8, 02:16 UTC
Update - Capsules are being re-created on the host and deployments will start recovering to full health.
Apr 8, 01:45 UTC
Update - We've had to migrate the host to new hardware. As such we'll be re-creating capsules on the host which will take a little time.
Apr 8, 01:37 UTC
Identified - We are currently investigating the outage with candidate.61.mongolayer.com - AWS - US-East-1
Apr 8, 01:15 UTC