Get email notifications whenever Compose creates or updates an incident.
Get SMS notifications whenever Compose creates or resolves an incident.
Get webhook notifications whenever Compose creates an incident, updates an incident, or changes a component status.
Visit our support site.
All Systems Operational
Web Application
?
Operational
REST API
?
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Sep 22, 2017
No incidents reported today.
Sep 21, 2017
Resolved -
The host and capsules are now back online and deployments should be back to full health.
Sep 21, 09:27 UTC
Sep 21, 09:27 UTC
Identified -
We've had to stop/start the instance. The host is now back online and we are in the process of re-creating capsules and bringing those online.
Sep 21, 08:24 UTC
Sep 21, 08:24 UTC
Investigating -
We are currently investigating an outage with aws-us-east-1-data.39.dblayer.com
All deployments using this host should continue functioning due to failing over to other hosts.
Sep 21, 06:43 UTC
All deployments using this host should continue functioning due to failing over to other hosts.
Sep 21, 06:43 UTC
Sep 20, 2017
Beginning immediately and lasting until 22:00UTC, Compose will be performing necessary maintenance to aws-us-east-1-data.49.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.
Sep 20, 20:52 UTC
Sep 20, 20:52 UTC
Resolved -
The UI is now available.
Sep 20, 16:53 UTC
Sep 20, 16:53 UTC
Investigating -
We are investigating an issue that is preventing the UI from displaying for Heroku add-on users. Deployments themselves remain fully functional.
Sep 20, 09:25 UTC
Sep 20, 09:25 UTC
Sep 19, 2017
No incidents reported.
Sep 18, 2017
No incidents reported.
Sep 17, 2017
No incidents reported.
Sep 16, 2017
No incidents reported.
Sep 15, 2017
No incidents reported.
Sep 14, 2017
Resolved -
This incident has been resolved.
Sep 14, 22:06 UTC
Sep 14, 22:06 UTC
Investigating -
We're working through some issues with Amazon S3 which may be causing degraded functionality with Compose's UI as well as deployment operations like creating and accessing backups, and creating new deployments. Your running database deployments are safe and accessible, however. We're continuing to investigate.
Sep 14, 18:57 UTC
Sep 14, 18:57 UTC
Completed -
The scheduled maintenance has been completed and all services should now be back online.
Sep 14, 14:27 UTC
Sep 14, 14:27 UTC
Scheduled -
Beginning 2017-09-14 12:00 UTC and lasting until 2017-09-14 13:00UTC, Compose will be performing required maintenance to aws-us-east-1-data.34.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.
Aug 30, 18:28 UTC
Aug 30, 18:28 UTC
Sep 13, 2017
No incidents reported.
Sep 12, 2017
Completed -
The scheduled maintenance has been completed.
Sep 12, 15:33 UTC
Sep 12, 15:33 UTC
Verifying -
All capsules are now started. We are monitoring deployments and normal operation should be restored within the next 30 minutes.
Sep 12, 12:29 UTC
Sep 12, 12:29 UTC
Update -
The maintenance purpose has been completed. We are currently bringing all capsules back online.
Sep 12, 12:20 UTC
Sep 12, 12:20 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Sep 12, 11:58 UTC
Sep 12, 11:58 UTC
Scheduled -
Beginning 2017-09-12 12:00 UTC and lasting until 2017-09-12 13:00UTC, Compose will be performing required maintenance to aws-us-east-1-data.20.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.
Aug 18, 14:20 UTC
Aug 18, 14:20 UTC
Completed -
The maintenance has been completed.
Sep 12, 14:23 UTC
Sep 12, 14:23 UTC
In progress -
The scheduled maintenance is in progress.
Sep 12, 14:01 UTC
Sep 12, 14:01 UTC
Scheduled -
Beginning 2017-09-12 14:00 UTC and lasting until 2017-09-12 15:00 UTC, Compose will be performing required maintenance to aws-eu-west-1-data.2.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.
Aug 22, 15:50 UTC
Aug 22, 15:50 UTC
Resolved -
This maintenance is now complete.
Sep 12, 11:50 UTC
Sep 12, 11:50 UTC
Monitoring -
All capsules have been restarted. We'll be working through any remaining alerts to ensure deployments are in full health.
Sep 12, 11:14 UTC
Sep 12, 11:14 UTC
Update -
Capsules are being restarted now.
Sep 12, 11:01 UTC
Sep 12, 11:01 UTC
Update -
Host is back up, performing some maintenance and then will restart capsules.
Sep 12, 10:57 UTC
Sep 12, 10:57 UTC
Update -
Capsules stopped. Host rebooting now.
Sep 12, 10:43 UTC
Sep 12, 10:43 UTC
Update -
Attempting to gracefully stop what capsules we can before reboot.
Sep 12, 10:22 UTC
Sep 12, 10:22 UTC
Identified -
Beginning immediately, Compose will be performing necessary maintenance to aws-us-east-1-data.55. During this time, deployments using this host should remain operational and your databases should failover as intended. Further updates to follow.
Sep 12, 10:17 UTC
Sep 12, 10:17 UTC
Sep 11, 2017
No incidents reported.
Sep 10, 2017
No incidents reported.
Sep 9, 2017
No incidents reported.
Sep 8, 2017
Resolved -
The host is online and all capsules have been started.
Sep 8, 16:46 UTC
Sep 8, 16:46 UTC
Identified -
The AWS host aws-us-east-1-data.24.dblayer.com is undergoing emergency maintenance and some members may become unavailable. All deployments should fail over appropriately, however brief moments of poorer performance may occur.
Sep 8, 16:12 UTC
Sep 8, 16:12 UTC
← Incident History
Powered by Statuspage