Emergency Maintenance - aws-ap-southeast-1-data.3.dblayer.com
Identified - Beginning immediately Compose will be performing emergency maintenance on:

aws-ap-southeast-1-data.3.dblayer.com

This emergeny maintenance includes non-portal hosts which, by the design of the Compose platform, should not affect the availability of your database deployments. No action on your part should be required before or during this maintenance. If during the maintenance you experience problems with your deployment, please contact us immediately at support@compose.com and we will work with you to resolve these issues.

These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

Affected deployments:

5a1a5d02123a21519e1c1d00
5a54c0ca6f45c00014259443
5a55f6fdc607ae0019b96117
5a783c1dac6d770018f08fb1
5b5155dad48b64001d98cbe4
5b553255de49f900157f63d1
5b5b37e3a1ee500015b229a8
5b5ef84c36cc1a001a90ee04
5b7a60b4736508001dceffb8
5c91bc5e7849a7000b005951
5ca0708b73ec1c001140d365
5dcd041adfa469000e1c1f67
5e147cc07d277633c92aaab1
5e301f37c8b297587bfad7d5
5e30fed78f598c6b1d8fef70
5e3b6ab10743cd001528e6dc
5e69bec1bbb147000e83d490
5e6c61e8432c46001ae17888
5e7b48d01a02d158af9c9b48
5e7be4e59f80d0537eb41a56
5e985cd312e002000e1a4e16
5ea25d35c4f077000e771f35
5ea31aaa67e3ba00143a58d4
5ea6fddb67e3ba00173aff75
5eaa807e4476cf000edea181
5ece6d828f8a3f0011b2b979
5ef4d0b7ba17db001a9424de
5efaf2281e43b1000e21048f

If you have any questions about this maintenance, please email us at support@compose.com.
Jul 2, 19:40 UTC

About This Site

Your Compose deployment will use one of these three domains in the connection string:

- mongolayer.com
- dblayer.com
- composedb.com

These are mapped to the component groups below as follows:

- mongolayer.com - See the Legacy component groups
- dblayer.com - See the non-Legacy component groups
- composedb.com - Use a tool such as nslookup to map your domain to a dblayer.com address

www.compose.com Operational
Web Application ? Operational
REST API ? Operational
Heroku Add-on Web Application Operational
AWS ap-southeast-1 Region Major Outage
aws-ap-southeast-1-data.0.dblayer.com Operational
aws-ap-southeast-1-data.1.dblayer.com Operational
aws-ap-southeast-1-data.2.dblayer.com Operational
aws-ap-southeast-1-data.3.dblayer.com Major Outage
aws-ap-southeast-1-data.4.dblayer.com Operational
aws-ap-southeast-1-data.5.dblayer.com Operational
aws-ap-southeast-1-memory.0.dblayer.com Operational
aws-ap-southeast-1-memory.1.dblayer.com Operational
aws-ap-southeast-1-memory.2.dblayer.com Operational
aws-ap-southeast-1-portal.0.dblayer.com Operational
aws-ap-southeast-1-portal.1.dblayer.com Operational
aws-ap-southeast-1-portal.2.dblayer.com Operational
aws-ap-southeast-1-utility.0.dblayer.com Operational
aws-ap-southeast-1-utility.1.dblayer.com Operational
aws-ap-southeast-1-utility.2.dblayer.com Operational
AWS eu-central-1 Region Operational
aws-eu-central-1-data.0.dblayer.com Operational
aws-eu-central-1-data.1.dblayer.com Operational
aws-eu-central-1-data.2.dblayer.com Operational
aws-eu-central-1-data.3.dblayer.com Operational
aws-eu-central-1-data.4.dblayer.com Operational
aws-eu-central-1-data.5.dblayer.com Operational
aws-eu-central-1-memory.0.dblayer.com Operational
aws-eu-central-1-memory.1.dblayer.com Operational
aws-eu-central-1-memory.2.dblayer.com Operational
aws-eu-central-1-portal.0.dblayer.com Operational
aws-eu-central-1-portal.1.dblayer.com Operational
aws-eu-central-1-portal.2.dblayer.com Operational
aws-eu-central-1-utility.0.dblayer.com Operational
aws-eu-central-1-utility.1.dblayer.com Operational
aws-eu-central-1-utility.2.dblayer.com Operational
aws-eu-central-1-memory.3.dblayer.com Operational
aws-eu-central-1-data.7.dblayer.com Operational
aws-eu-central-1-data.6.dblayer.com Operational
aws-eu-central-1-memory.4.dblayer.com Operational
aws-eu-central-1-data.8.dblayer.com Operational
AWS eu-west-1 Region Operational
aws-eu-west-1-data.0.dblayer.com Operational
aws-eu-west-1-data.1.dblayer.com Operational
aws-eu-west-1-data.2.dblayer.com Operational
aws-eu-west-1-data.3.dblayer.com Operational
aws-eu-west-1-data.4.dblayer.com Operational
aws-eu-west-1-data.5.dblayer.com Operational
aws-eu-west-1-data.6.dblayer.com Operational
aws-eu-west-1-data.7.dblayer.com Operational
aws-eu-west-1-data.8.dblayer.com Operational
aws-eu-west-1-data.9.dblayer.com Operational
aws-eu-west-1-data.10.dblayer.com Operational
aws-eu-west-1-data.11.dblayer.com Operational
aws-eu-west-1-data.12.dblayer.com Operational
aws-eu-west-1-data.13.dblayer.com Operational
aws-eu-west-1-data.14.dblayer.com Operational
aws-eu-west-1-data.15.dblayer.com Operational
aws-eu-west-1-data.17.dblayer.com Operational
aws-eu-west-1-memory.0.dblayer.com Operational
aws-eu-west-1-memory.1.dblayer.com Operational
aws-eu-west-1-memory.2.dblayer.com Operational
aws-eu-west-1-memory.3.dblayer.com Operational
aws-eu-west-1-memory.4.dblayer.com Operational
aws-eu-west-1-memory.5.dblayer.com Operational
aws-eu-west-1-memory.6.dblayer.com Operational
aws-eu-west-1-memory.7.dblayer.com Operational
aws-eu-west-1-memory.8.dblayer.com Operational
aws-eu-west-1-portal.0.dblayer.com Operational
aws-eu-west-1-portal.1.dblayer.com Operational
aws-eu-west-1-portal.2.dblayer.com Operational
aws-eu-west-1-portal.3.dblayer.com Operational
aws-eu-west-1-portal.4.dblayer.com Operational
aws-eu-west-1-portal.5.dblayer.com Operational
aws-eu-west-1-portal.6.dblayer.com Operational
aws-eu-west-1-portal.7.dblayer.com Operational
aws-eu-west-1-portal.8.dblayer.com Operational
aws-eu-west-1-portal.9.dblayer.com Operational
aws-eu-west-1-portal.10.dblayer.com Operational
aws-eu-west-1-utility.0.dblayer.com Operational
aws-eu-west-1-utility.1.dblayer.com Operational
aws-eu-west-1-utility.2.dblayer.com Operational
aws-eu-west-1-utility.3.dblayer.com Operational
aws-eu-west-1-utility.4.dblayer.com Operational
aws-eu-west-1-utility.5.dblayer.com Operational
aws-eu-west-1-utility.7.dblayer.com Operational
aws-eu-west-1-utility.8.dblayer.com Operational
aws-eu-west-1-data.20.dblayer.com Operational
aws-eu-west-1-data.18.dblayer.com Operational
aws-eu-west-1-data.19.dblayer.com Operational
AWS us-east-1 Region Operational
aws-us-east-1-data.0.dblayer.com Operational
aws-us-east-1-data.1.dblayer.com Operational
aws-us-east-1-data.2.dblayer.com Operational
aws-us-east-1-data.3.dblayer.com Operational
aws-us-east-1-data.4.dblayer.com Operational
aws-us-east-1-data.5.dblayer.com Operational
aws-us-east-1-data.6.dblayer.com Operational
aws-us-east-1-data.7.dblayer.com Operational
aws-us-east-1-data.8.dblayer.com Operational
aws-us-east-1-data.9.dblayer.com Operational
aws-us-east-1-data.10.dblayer.com Operational
aws-us-east-1-data.11.dblayer.com Operational
aws-us-east-1-data.12.dblayer.com Operational
aws-us-east-1-data.13.dblayer.com Operational
aws-us-east-1-data.14.dblayer.com Operational
aws-us-east-1-data.15.dblayer.com Operational
aws-us-east-1-data.16.dblayer.com Operational
aws-us-east-1-data.17.dblayer.com Operational
aws-us-east-1-data.18.dblayer.com Operational
aws-us-east-1-data.19.dblayer.com Operational
aws-us-east-1-data.20.dblayer.com Operational
aws-us-east-1-data.21.dblayer.com Operational
aws-us-east-1-data.22.dblayer.com Operational
aws-us-east-1-data.23.dblayer.com Operational
aws-us-east-1-data.24.dblayer.com Operational
aws-us-east-1-data.25.dblayer.com Operational
aws-us-east-1-data.26.dblayer.com Operational
aws-us-east-1-data.27.dblayer.com Operational
aws-us-east-1-data.28.dblayer.com Operational
aws-us-east-1-data.29.dblayer.com Operational
aws-us-east-1-data.30.dblayer.com Operational
aws-us-east-1-data.31.dblayer.com Operational
aws-us-east-1-data.32.dblayer.com Operational
aws-us-east-1-data.33.dblayer.com Operational
aws-us-east-1-data.34.dblayer.com Operational
aws-us-east-1-data.36.dblayer.com Operational
aws-us-east-1-data.37.dblayer.com Operational
aws-us-east-1-data.38.dblayer.com Operational
aws-us-east-1-data.39.dblayer.com Operational
aws-us-east-1-data.40.dblayer.com Operational
aws-us-east-1-data.41.dblayer.com Operational
aws-us-east-1-data.45.dblayer.com ? Operational
aws-us-east-1-data.46.dblayer.com Operational
aws-us-east-1-data.47.dblayer.com Operational
aws-us-east-1-data.48.dblayer.com Operational
aws-us-east-1-data.49.dblayer.com Operational
aws-us-east-1-data.51.dblayer.com Operational
aws-us-east-1-data.52.dblayer.com Operational
aws-us-east-1-data.53.dblayer.com Operational
aws-us-east-1-data.54.dblayer.com Operational
aws-us-east-1-data.55.dblayer.com Operational
aws-us-east-1-data.56.dblayer.com Operational
aws-us-east-1-data.57.dblayer.com Operational
aws-us-east-1-data.58.dblayer.com Operational
aws-us-east-1-data.59.dblayer.com Operational
aws-us-east-1-data.60.dblayer.com Operational
aws-us-east-1-data.61.dblayer.com Operational
aws-us-east-1-data.62.dblayer.com Operational
aws-us-east-1-data.63.dblayer.com Operational
aws-us-east-1-data.64.dblayer.com Operational
aws-us-east-1-memory.0.dblayer.com Operational
aws-us-east-1-memory.1.dblayer.com Operational
aws-us-east-1-memory.2.dblayer.com Operational
aws-us-east-1-memory.3.dblayer.com Operational
aws-us-east-1-memory.4.dblayer.com Operational
aws-us-east-1-memory.5.dblayer.com Operational
aws-us-east-1-memory.6.dblayer.com Operational
aws-us-east-1-memory.7.dblayer.com Operational
aws-us-east-1-memory.8.dblayer.com Operational
aws-us-east-1-memory.9.dblayer.com Operational
aws-us-east-1-memory.10.dblayer.com Operational
aws-us-east-1-memory.11.dblayer.com Operational
aws-us-east-1-memory.12.dblayer.com Operational
aws-us-east-1-memory.13.dblayer.com Operational
aws-us-east-1-memory.14.dblayer.com Operational
aws-us-east-1-memory.15.dblayer.com Operational
aws-us-east-1-memory.16.dblayer.com Operational
aws-us-east-1-memory.17.dblayer.com Operational
aws-us-east-1-memory.18.dblayer.com Operational
aws-us-east-1-memory.19.dblayer.com Operational
aws-us-east-1-memory.20.dblayer.com Operational
aws-us-east-1-memory.21.dblayer.com Operational
aws-us-east-1-memory.22.dblayer.com Operational
aws-us-east-1-memory.23.dblayer.com Operational
aws-us-east-1-memory.24.dblayer.com Operational
aws-us-east-1-memory.25.dblayer.com Operational
aws-us-east-1-portal.0.dblayer.com Operational
aws-us-east-1-portal.1.dblayer.com Operational
aws-us-east-1-portal.2.dblayer.com Operational
aws-us-east-1-portal.3.dblayer.com Operational
aws-us-east-1-portal.4.dblayer.com Operational
aws-us-east-1-portal.5.dblayer.com Operational
aws-us-east-1-portal.6.dblayer.com Operational
aws-us-east-1-portal.7.dblayer.com Operational
aws-us-east-1-portal.8.dblayer.com Operational
aws-us-east-1-portal.9.dblayer.com Operational
aws-us-east-1-portal.10.dblayer.com Operational
aws-us-east-1-portal.11.dblayer.com Operational
aws-us-east-1-portal.12.dblayer.com Operational
aws-us-east-1-portal.13.dblayer.com Operational
aws-us-east-1-portal.14.dblayer.com Operational
aws-us-east-1-portal.15.dblayer.com Operational
aws-us-east-1-portal.16.dblayer.com Operational
aws-us-east-1-portal.17.dblayer.com Operational
aws-us-east-1-portal.18.dblayer.com Operational
aws-us-east-1-portal.19.dblayer.com Operational
aws-us-east-1-portal.20.dblayer.com Operational
aws-us-east-1-portal.21.dblayer.com Operational
aws-us-east-1-portal.22.dblayer.com Operational
aws-us-east-1-portal.23.dblayer.com Operational
aws-us-east-1-portal.24.dblayer.com Operational
aws-us-east-1-portal.25.dblayer.com Operational
aws-us-east-1-portal.26.dblayer.com Operational
aws-us-east-1-portal.27.dblayer.com Operational
aws-us-east-1-portal.28.dblayer.com Operational
aws-us-east-1-portal.29.dblayer.com Operational
aws-us-east-1-portal.30.dblayer.com Operational
aws-us-east-1-portal.31.dblayer.com Operational
aws-us-east-1-portal.32.dblayer.com Operational
aws-us-east-1-portal.33.dblayer.com Operational
aws-us-east-1-utility.0.dblayer.com Operational
aws-us-east-1-utility.1.dblayer.com Operational
aws-us-east-1-utility.2.dblayer.com Operational
aws-us-east-1-utility.3.dblayer.com Operational
aws-us-east-1-utility.4.dblayer.com Operational
aws-us-east-1-utility.5.dblayer.com Operational
aws-us-east-1-utility.6.dblayer.com Operational
aws-us-east-1-utility.7.dblayer.com Operational
aws-us-east-1-utility.8.dblayer.com Operational
aws-us-east-1-utility.9.dblayer.com Operational
aws-us-east-1-utility.10.dblayer.com Operational
aws-us-east-1-utility.11.dblayer.com Operational
aws-us-east-1-utility.12.dblayer.com Operational
aws-us-east-1-utility.13.dblayer.com Operational
aws-us-east-1-utility.14.dblayer.com Operational
aws-us-east-1-utility.15.dblayer.com Operational
aws-us-east-1-utility.16.dblayer.com Operational
aws-us-east-1-utility.17.dblayer.com Operational
aws-us-east-1-utility.18.dblayer.com Operational
aws-us-east-1-utility.19.dblayer.com Operational
aws-us-east-1-utility.20.dblayer.com Operational
aws-us-east-1-utility.21.dblayer.com Operational
aws-us-east-1-utility.22.dblayer.com Operational
aws-us-east-1-utility.23.dblayer.com Operational
aws-us-east-1-utility.24.dblayer.com Operational
aws-us-east-1-utility.25.dblayer.com Operational
aws-us-east-1-utility.26.dblayer.com Operational
aws-us-east-1-utility.27.dblayer.com Operational
aws-us-east-1-utility.28.dblayer.com Operational
aws-us-east-1-utility.29.dblayer.com Operational
aws-us-east-1-utility.30.dblayer.com Operational
aws-us-east-1-utility.31.dblayer.com Operational
aws-us-east-1-utility.32.dblayer.com Operational
aws-us-east-1-utility.33.dblayer.com Operational
aws-us-east-1-utility.36.dblayer.com Operational
aws-us-east-1-utility.37.dblayer.com Operational
aws-us-east-1-utility.38.dblayer.com Operational
aws-us-east-1-utility.39.dblayer.com Operational
aws-us-east-1-data.66.dblayer.com Operational
aws-us-east-1-data.68.dblayer.com Operational
aws-us-east-1-portal.36.dblayer.com Operational
aws-us-east-1-memory.26.dblayer.com Operational
aws-us-east-1-memory.27.dblayer.com Operational
aws-us-east-1-utility.42.dblayer.com Operational
aws-us-east-1-utility.41.dblayer.com Operational
aws-us-east-1-memory.29.dblayer.com Operational
aws-us-east-1-data.65.dblayer.com Operational
aws-us-east-1-data.67.dblayer.com Operational
aws-us-east-1-data.69.dblayer.com Operational
aws-us-east-1-memory.31.dblayer.com Operational
aws-us-east-1-memory.28.dblayer.com Operational
aws-us-east-1-data.70.dblayer.com Operational
aws-us-east-1-portal.34.dblayer.com Operational
aws-us-east-1-portal.35.dblayer.com Operational
aws-us-east-1-utility.40.dblayer.com Operational
aws-us-east-1-memory.30.dblayer.com Operational
AWS us-west-2 Region Operational
aws-us-west-2-data.0.dblayer.com Operational
aws-us-west-2-data.1.dblayer.com Operational
aws-us-west-2-data.2.dblayer.com Operational
aws-us-west-2-data.3.dblayer.com Operational
aws-us-west-2-data.4.dblayer.com Operational
aws-us-west-2-data.5.dblayer.com Operational
aws-us-west-2-memory.0.dblayer.com Operational
aws-us-west-2-memory.1.dblayer.com Operational
aws-us-west-2-memory.2.dblayer.com Operational
aws-us-west-2-memory.3.dblayer.com Operational
aws-us-west-2-memory.4.dblayer.com Operational
aws-us-west-2-memory.5.dblayer.com Operational
aws-us-west-2-portal.0.dblayer.com Operational
aws-us-west-2-portal.1.dblayer.com Operational
aws-us-west-2-portal.2.dblayer.com Operational
aws-us-west-2-utility.0.dblayer.com Operational
aws-us-west-2-utility.1.dblayer.com Operational
aws-us-west-2-utility.2.dblayer.com Operational
aws-us-west-2-portal.5.dblayer.com Operational
aws-us-west-2-data.6.dblayer.com Operational
aws-us-west-2-portal.3.dblayer.com Operational
aws-us-west-2-data.7.dblayer.com Operational
aws-us-west-2-data.8.dblayer.com Operational
aws-us-west-2-portal.4.dblayer.com Operational
Google Cloud eu-west-1 Region Operational
gcp-europe-west1-cpu.0.dblayer.com Operational
gcp-europe-west1-cpu.1.dblayer.com Operational
gcp-europe-west1-cpu.2.dblayer.com Operational
gcp-europe-west1-data.0.dblayer.com Operational
gcp-europe-west1-data.1.dblayer.com Operational
gcp-europe-west1-data.2.dblayer.com Operational
gcp-europe-west1-memory.0.dblayer.com Operational
gcp-europe-west1-memory.1.dblayer.com Operational
gcp-europe-west1-memory.2.dblayer.com Operational
gcp-europe-west1-memory.3.dblayer.com Operational
gcp-europe-west1-memory.4.dblayer.com Operational
gcp-europe-west1-memory.5.dblayer.com Operational
gcp-europe-west1-utility.0.dblayer.com Operational
gcp-europe-west1-utility.1.dblayer.com Operational
gcp-europe-west1-utility.2.dblayer.com Operational
Google Cloud us-east-1 Region Operational
gcp-us-east1-cpu.0.dblayer.com Operational
gcp-us-east1-cpu.1.dblayer.com Operational
gcp-us-east1-cpu.2.dblayer.com Operational
gcp-us-east1-cpu.3.dblayer.com Operational
gcp-us-east1-cpu.4.dblayer.com Operational
gcp-us-east1-cpu.5.dblayer.com Operational
gcp-us-east1-cpu.6.dblayer.com Operational
gcp-us-east1-cpu.7.dblayer.com Operational
gcp-us-east1-data.0.dblayer.com Operational
gcp-us-east1-data.1.dblayer.com Operational
gcp-us-east1-data.2.dblayer.com Operational
gcp-us-east1-data.3.dblayer.com Operational
gcp-us-east1-data.4.dblayer.com Operational
gcp-us-east1-data.5.dblayer.com Operational
gcp-us-east1-data.6.dblayer.com Operational
gcp-us-east1-data.7.dblayer.com Operational
gcp-us-east1-data.8.dblayer.com Operational
gcp-us-east1-memory.0.dblayer.com Operational
gcp-us-east1-memory.1.dblayer.com Operational
gcp-us-east1-memory.2.dblayer.com Operational
gcp-us-east1-memory.3.dblayer.com Operational
gcp-us-east1-memory.4.dblayer.com Operational
gcp-us-east1-memory.5.dblayer.com Operational
gcp-us-east1-memory.6.dblayer.com Operational
gcp-us-east1-memory.7.dblayer.com Operational
gcp-us-east1-memory.8.dblayer.com Operational
gcp-us-east1-utility.0.dblayer.com Operational
gcp-us-east1-utility.1.dblayer.com Operational
gcp-us-east1-utility.2.dblayer.com Operational
gcp-us-east1-utility.3.dblayer.com Operational
gcp-us-east1-utility.4.dblayer.com Operational
gcp-us-east1-utility.5.dblayer.com Operational
Softlayer aus-sydney-1 Region Operational
sl-aus-syd-1-data.0.dblayer.com Operational
sl-aus-syd-1-data.1.dblayer.com Operational
sl-aus-syd-1-data.2.dblayer.com Operational
sl-aus-syd-1-data.3.dblayer.com Operational
sl-aus-syd-1-data.4.dblayer.com Operational
sl-aus-syd-1-data.5.dblayer.com Operational
sl-aus-syd-1-data.6.dblayer.com Operational
sl-aus-syd-1-data.7.dblayer.com Operational
sl-aus-syd-1-data.8.dblayer.com Operational
sl-aus-syd-1-memory.0.dblayer.com Operational
sl-aus-syd-1-memory.1.dblayer.com Operational
sl-aus-syd-1-memory.2.dblayer.com Operational
sl-aus-syd-1-memory.3.dblayer.com Operational
sl-aus-syd-1-memory.4.dblayer.com Operational
sl-aus-syd-1-memory.5.dblayer.com Operational
sl-aus-syd-1-portal.0.dblayer.com Operational
sl-aus-syd-1-portal.1.dblayer.com Operational
sl-aus-syd-1-portal.2.dblayer.com Operational
sl-aus-syd-1-portal.3.dblayer.com Operational
sl-aus-syd-1-utility.0.dblayer.com ? Operational
sl-aus-syd-1-utility.1.dblayer.com Operational
sl-aus-syd-1-utility.2.dblayer.com Operational
sl-aus-syd-1-utility.3.dblayer.com Operational
Softlayer eu-frankfurt-2 Region Operational
sl-eu-fra-2-data.0.dblayer.com ? Operational
sl-eu-fra-2-data.1.dblayer.com ? Operational
sl-eu-fra-2-data.2.dblayer.com Operational
sl-eu-fra-2-data.3.dblayer.com Operational
sl-eu-fra-2-data.4.dblayer.com Operational
sl-eu-fra-2-data.5.dblayer.com Operational
sl-eu-fra-2-memory.0.dblayer.com Operational
sl-eu-fra-2-memory.1.dblayer.com Operational
sl-eu-fra-2-memory.2.dblayer.com Operational
sl-eu-fra-2-memory.3.dblayer.com Operational
sl-eu-fra-2-memory.4.dblayer.com Operational
sl-eu-fra-2-memory.5.dblayer.com Operational
sl-eu-fra-2-portal.0.dblayer.com Operational
sl-eu-fra-2-portal.1.dblayer.com Operational
sl-eu-fra-2-portal.2.dblayer.com Operational
sl-eu-fra-2-utility.0.dblayer.com Operational
sl-eu-fra-2-utility.1.dblayer.com Operational
sl-eu-fra-2-utility.2.dblayer.com Operational
Softlayer eu-london-2 Region Operational
sl-eu-lon-2-data.0.dblayer.com Operational
sl-eu-lon-2-data.1.dblayer.com Operational
sl-eu-lon-2-data.2.dblayer.com Operational
sl-eu-lon-2-data.3.dblayer.com Operational
sl-eu-lon-2-data.4.dblayer.com Operational
sl-eu-lon-2-data.5.dblayer.com Operational
sl-eu-lon-2-data.6.dblayer.com Operational
sl-eu-lon-2-data.7.dblayer.com Operational
sl-eu-lon-2-data.8.dblayer.com Operational
sl-eu-lon-2-data.9.dblayer.com Operational
sl-eu-lon-2-data.10.dblayer.com Operational
sl-eu-lon-2-data.11.dblayer.com Operational
sl-eu-lon-2-data.12.dblayer.com Operational
sl-eu-lon-2-data.13.dblayer.com Operational
sl-eu-lon-2-data.14.dblayer.com Operational
sl-eu-lon-2-memory.0.dblayer.com Operational
sl-eu-lon-2-memory.1.dblayer.com Operational
sl-eu-lon-2-memory.2.dblayer.com Operational
sl-eu-lon-2-memory.3.dblayer.com Operational
sl-eu-lon-2-memory.4.dblayer.com Operational
sl-eu-lon-2-memory.5.dblayer.com Operational
sl-eu-lon-2-memory.6.dblayer.com Operational
sl-eu-lon-2-portal.0.dblayer.com Operational
sl-eu-lon-2-portal.1.dblayer.com Operational
sl-eu-lon-2-portal.2.dblayer.com Operational
sl-eu-lon-2-portal.3.dblayer.com Operational
sl-eu-lon-2-portal.4.dblayer.com Operational
sl-eu-lon-2-portal.5.dblayer.com Operational
sl-eu-lon-2-portal.6.dblayer.com Operational
sl-eu-lon-2-portal.7.dblayer.com Operational
sl-eu-lon-2-portal.8.dblayer.com Operational
sl-eu-lon-2-utility.0.dblayer.com Operational
sl-eu-lon-2-utility.1.dblayer.com Operational
sl-eu-lon-2-utility.2.dblayer.com Operational
sl-eu-lon-2-utility.3.dblayer.com Operational
sl-eu-lon-2-utility.4.dblayer.com Operational
sl-eu-lon-2-utility.5.dblayer.com Operational
sl-eu-lon-2-utility.6.dblayer.com Operational
sl-eu-lon-2-utility.7.dblayer.com Operational
sl-eu-lon-2-utility.8.dblayer.com Operational
Softlayer us-east-1 Region Operational
sl-us-wdc-1-data.0.dblayer.com Operational
sl-us-wdc-1-data.1.dblayer.com Operational
sl-us-wdc-1-data.2.dblayer.com Operational
sl-us-wdc-1-memory.0.dblayer.com Operational
sl-us-wdc-1-memory.1.dblayer.com Operational
sl-us-wdc-1-memory.2.dblayer.com Operational
sl-us-wdc-1-portal.0.dblayer.com Operational
sl-us-wdc-1-portal.1.dblayer.com Operational
sl-us-wdc-1-portal.2.dblayer.com Operational
Softlayer us-dallas-09 Region Operational
sl-us-dal-9-data.0.dblayer.com Operational
sl-us-dal-9-data.1.dblayer.com Operational
sl-us-dal-9-data.2.dblayer.com Operational
sl-us-dal-9-data.3.dblayer.com Operational
sl-us-dal-9-data.4.dblayer.com Operational
sl-us-dal-9-data.5.dblayer.com Operational
sl-us-dal-9-data.6.dblayer.com Operational
sl-us-dal-9-data.7.dblayer.com Operational
sl-us-dal-9-data.8.dblayer.com Operational
sl-us-dal-9-data.9.dblayer.com Operational
sl-us-dal-9-data.10.dblayer.com Operational
sl-us-dal-9-data.11.dblayer.com Operational
sl-us-dal-9-data.12.dblayer.com Operational
sl-us-dal-9-memory.0.dblayer.com Operational
sl-us-dal-9-memory.1.dblayer.com Operational
sl-us-dal-9-memory.2.dblayer.com Operational
sl-us-dal-9-memory.3.dblayer.com Operational
sl-us-dal-9-memory.4.dblayer.com Operational
sl-us-dal-9-memory.5.dblayer.com Operational
sl-us-dal-9-portal.0.dblayer.com Operational
sl-us-dal-9-portal.1.dblayer.com Operational
sl-us-dal-9-portal.2.dblayer.com Operational
sl-us-dal-9-portal.3.dblayer.com Operational
sl-us-dal-9-portal.4.dblayer.com Operational
sl-us-dal-9-portal.5.dblayer.com Operational
sl-us-dal-9-portal.6.dblayer.com Operational
sl-us-dal-9-utility.3.dblayer.com Operational
sl-us-dal-9-utility.4.dblayer.com Operational
sl-us-dal-9-utility.5.dblayer.com Operational
sl-us-dal-9-utility.8.dblayer.com Operational
Softlayer us-south-1 Region Operational
sl-us-south-1-data.0.dblayer.com Operational
sl-us-south-1-data.1.dblayer.com Operational
sl-us-south-1-data.2.dblayer.com Operational
sl-us-south-1-data.3.dblayer.com Operational
sl-us-south-1-data.4.dblayer.com Operational
sl-us-south-1-data.5.dblayer.com Operational
sl-us-south-1-data.6.dblayer.com Operational
sl-us-south-1-data.7.dblayer.com Operational
sl-us-south-1-data.8.dblayer.com Operational
sl-us-south-1-data.9.dblayer.com Operational
sl-us-south-1-data.10.dblayer.com Operational
sl-us-south-1-data.11.dblayer.com Operational
sl-us-south-1-data.12.dblayer.com Operational
sl-us-south-1-data.13.dblayer.com Operational
sl-us-south-1-data.14.dblayer.com Operational
sl-us-south-1-data.15.dblayer.com Operational
sl-us-south-1-data.16.dblayer.com Operational
sl-us-south-1-data.17.dblayer.com Operational
sl-us-south-1-data.18.dblayer.com Operational
sl-us-south-1-data.19.dblayer.com Operational
sl-us-south-1-data.20.dblayer.com Operational
sl-us-south-1-data.21.dblayer.com Operational
sl-us-south-1-data.22.dblayer.com Operational
sl-us-south-1-data.23.dblayer.com Operational
sl-us-south-1-data.24.dblayer.com Operational
sl-us-south-1-data.25.dblayer.com Operational
sl-us-south-1-data.26.dblayer.com Operational
sl-us-south-1-data.27.dblayer.com Operational
sl-us-south-1-data.28.dblayer.com Operational
sl-us-south-1-data.29.dblayer.com Operational
sl-us-south-1-data.30.dblayer.com Operational
sl-us-south-1-data.31.dblayer.com Operational
sl-us-south-1-data.32.dblayer.com Operational
sl-us-south-1-data.33.dblayer.com Operational
sl-us-south-1-data.34.dblayer.com Operational
sl-us-south-1-data.35.dblayer.com Operational
sl-us-south-1-data.36.dblayer.com Operational
sl-us-south-1-data.37.dblayer.com Operational
sl-us-south-1-data.38.dblayer.com Operational
sl-us-south-1-data.39.dblayer.com Operational
sl-us-south-1-data.40.dblayer.com Operational
sl-us-south-1-data.41.dblayer.com Operational
sl-us-south-1-data.42.dblayer.com Operational
sl-us-south-1-data.43.dblayer.com Operational
sl-us-south-1-data.44.dblayer.com Operational
sl-us-south-1-memory.0.dblayer.com Operational
sl-us-south-1-memory.1.dblayer.com Operational
sl-us-south-1-memory.2.dblayer.com Operational
sl-us-south-1-memory.3.dblayer.com Operational
sl-us-south-1-memory.4.dblayer.com ? Operational
sl-us-south-1-memory.5.dblayer.com Operational
sl-us-south-1-memory.6.dblayer.com Operational
sl-us-south-1-memory.7.dblayer.com Operational
sl-us-south-1-memory.8.dblayer.com Operational
sl-us-south-1-memory.9.dblayer.com Operational
sl-us-south-1-memory.10.dblayer.com Operational
sl-us-south-1-memory.11.dblayer.com Operational
sl-us-south-1-portal.0.dblayer.com Operational
sl-us-south-1-portal.1.dblayer.com Operational
sl-us-south-1-portal.2.dblayer.com Operational
sl-us-south-1-portal.3.dblayer.com Operational
sl-us-south-1-portal.4.dblayer.com Operational
sl-us-south-1-portal.5.dblayer.com Operational
sl-us-south-1-portal.6.dblayer.com Operational
sl-us-south-1-portal.7.dblayer.com Operational
sl-us-south-1-portal.8.dblayer.com Operational
sl-us-south-1-portal.9.dblayer.com Operational
sl-us-south-1-portal.10.dblayer.com Operational
sl-us-south-1-portal.11.dblayer.com Operational
sl-us-south-1-portal.12.dblayer.com Operational
sl-us-south-1-portal.13.dblayer.com Operational
sl-us-south-1-portal.14.dblayer.com Operational
sl-us-south-1-portal.15.dblayer.com Operational
sl-us-south-1-portal.16.dblayer.com Operational
sl-us-south-1-portal.17.dblayer.com Operational
sl-us-south-1-portal.18.dblayer.com Operational
sl-us-south-1-portal.19.dblayer.com Operational
sl-us-south-1-portal.20.dblayer.com Operational
sl-us-south-1-portal.21.dblayer.com Operational
sl-us-south-1-portal.22.dblayer.com Operational
sl-us-south-1-portal.23.dblayer.com Operational
sl-us-south-1-portal.24.dblayer.com Operational
sl-us-south-1-portal.25.dblayer.com Operational
sl-us-south-1-portal.26.dblayer.com Operational
sl-us-south-1-portal.27.dblayer.com Operational
sl-us-south-1-portal.28.dblayer.com Operational
sl-us-south-1-utility.0.dblayer.com Operational
sl-us-south-1-utility.1.dblayer.com Operational
sl-us-south-1-utility.2.dblayer.com Operational
sl-us-south-1-utility.3.dblayer.com Operational
sl-us-south-1-utility.4.dblayer.com Operational
sl-us-south-1-utility.5.dblayer.com Operational
sl-us-south-1-utility.6.dblayer.com Operational
sl-us-south-1-utility.7.dblayer.com Operational
sl-us-south-1-utility.8.dblayer.com Operational
sl-us-south-1-utility.9.dblayer.com Operational
sl-us-south-1-utility.10.dblayer.com Operational
sl-us-south-1-utility.11.dblayer.com Operational
sl-us-south-1-utility.12.dblayer.com Operational
sl-us-south-1-utility.13.dblayer.com Operational
sl-us-south-1-utility.14.dblayer.com Operational
sl-us-south-1-utility.15.dblayer.com Operational
sl-us-south-1-utility.16.dblayer.com Operational
sl-us-south-1-utility.17.dblayer.com Operational
sl-us-south-1-utility.18.dblayer.com Operational
sl-us-south-1-utility.19.dblayer.com Operational
sl-us-south-1-utility.20.dblayer.com Operational
sl-us-south-1-utility.21.dblayer.com Operational
sl-us-south-1-utility.22.dblayer.com Operational
sl-us-south-1-utility.23.dblayer.com Operational
sl-us-south-1-utility.24.dblayer.com Operational
sl-us-south-1-data.52.dblayer.com Operational
sl-us-south-1-portal.45.dblayer.com Operational
sl-us-south-1-data.71.dblayer.com Operational
sl-us-south-1-data.54.dblayer.com Operational
sl-us-south-1-portal.36.dblayer.com Operational
sl-us-south-1-portal.38.dblayer.com Operational
sl-us-south-1-data.49.dblayer.com Operational
sl-us-south-1-data.50.dblayer.com Operational
sl-us-south-1-portal.42.dblayer.com Operational
sl-us-south-1-utility.40.dblayer.com Operational
sl-us-south-1-data.48.dblayer.com Operational
sl-us-south-1-memory.23.dblayer.com Operational
sl-us-south-1-portal.39.dblayer.com Operational
sl-us-south-1-data.70.dblayer.com Operational
sl-us-south-1-utility.26.dblayer.com Operational
sl-us-south-1-utility.27.dblayer.com Operational
sl-us-south-1-portal.40.dblayer.com Operational
sl-us-south-1-portal.32.dblayer.com Operational
sl-us-south-1-portal.43.dblayer.com Operational
sl-us-south-1-portal.37.dblayer.com Operational
sl-us-south-1-portal.29.dblayer.com Operational
sl-us-south-1-data.57.dblayer.com Operational
sl-us-south-1-utility.38.dblayer.com Operational
sl-us-south-1-data.51.dblayer.com Operational
sl-us-south-1-data.60.dblayer.com Operational
sl-us-south-1-memory.21.dblayer.com Operational
sl-us-south-1-memory.14.dblayer.com Operational
sl-us-south-1-memory.18.dblayer.com Operational
sl-us-south-1-memory.22.dblayer.com Operational
sl-us-south-1-portal.31.dblayer.com Operational
sl-us-south-1-data.56.dblayer.com Operational
sl-us-south-1-utility.41.dblayer.com Operational
sl-us-south-1-memory.13.dblayer.com Operational
sl-us-south-1-portal.30.dblayer.com Operational
sl-us-south-1-data.62.dblayer.com Operational
sl-us-south-1-utility.43.dblayer.com Operational
sl-us-south-1-utility.30.dblayer.com Operational
sl-us-south-1-utility.25.dblayer.com Operational
sl-us-south-1-data.53.dblayer.com Operational
sl-us-south-1-utility.37.dblayer.com Operational
sl-us-south-1-data.59.dblayer.com Operational
sl-us-south-1-memory.12.dblayer.com Operational
sl-us-south-1-portal.41.dblayer.com Operational
sl-us-south-1-utility.39.dblayer.com Operational
sl-us-south-1-utility.29.dblayer.com Operational
sl-us-south-1-memory.20.dblayer.com Operational
sl-us-south-1-data.55.dblayer.com Operational
sl-us-south-1-utility.42.dblayer.com Operational
sl-us-south-1-memory.19.dblayer.com Operational
sl-us-south-1-portal.47.dblayer.com Operational
sl-us-south-1-data.61.dblayer.com Operational
sl-us-south-1-data.58.dblayer.com Operational
sl-us-south-1-portal.46.dblayer.com Operational
sl-us-south-1-utility.45.dblayer.com Operational
sl-us-south-1-portal.44.dblayer.com Operational
sl-us-south-1-utility.44.dblayer.com Operational
sl-us-south-1-data.69.dblayer.com Operational
sl-us-south-1-utility.28.dblayer.com Operational
sl-us-south-1-portal.59.dblayer.com Operational
Softlayer eu-de-1 Region (IBM Cloud EU Supported) ? Operational
sl-eu-fra-2-data.6.dblayer.com Operational
sl-eu-fra-2-data.7.dblayer.com Operational
sl-eu-fra-2-data.8.dblayer.com Operational
sl-eu-fra-2-data.9.dblayer.com Operational
sl-eu-fra-2-data.10.dblayer.com Operational
sl-eu-fra-2-data.11.dblayer.com Operational
sl-eu-de-1-data.12.dblayer.com Operational
sl-eu-de-1-data.13.dblayer.com Operational
sl-eu-de-1-data.14.dblayer.com Operational
sl-eu-fra-2-memory.6.dblayer.com Operational
sl-eu-fra-2-memory.7.dblayer.com Operational
sl-eu-fra-2-memory.8.dblayer.com Operational
sl-eu-de-1-memory.9.dblayer.com Operational
sl-eu-de-1-memory.10.dblayer.com Operational
sl-eu-de-1-memory.11.dblayer.com Operational
sl-eu-fra-2-portal.3.dblayer.com Operational
sl-eu-fra-2-portal.4.dblayer.com Operational
sl-eu-fra-2-portal.5.dblayer.com Operational
sl-eu-de-1-portal.7.dblayer.com Operational
sl-eu-de-1-portal.8.dblayer.com Operational
sl-eu-de-1-portal.9.dblayer.com Operational
Legacy - AWS - AP Southeast 2 Operational
galaga.0.mongolayer.com ? Operational
galaga.1.mongolayer.com ? Operational
galaga.2.mongolayer.com ? Operational
galaga.3.mongolayer.com ? Operational
Legacy - AWS - EU West 1 Operational
lamppost.0.mongolayer.com ? Operational
lamppost.1.mongolayer.com ? Operational
lamppost.2.mongolayer.com ? Operational
lamppost.3.mongolayer.com ? Operational
lamppost.4.mongolayer.com Operational
lamppost.5.mongolayer.com Operational
lamppost.6.mongolayer.com ? Operational
lamppost.8.mongolayer.com ? Operational
lamppost.9.mongolayer.com ? Operational
lamppost.10.mongolayer.com Operational
lamppost.11.mongolayer.com Operational
lamppost.12.mongolayer.com Operational
lamppost.14.mongolayer.com Operational
hatch.50.mongolayer.com Operational
cockney.5.mongolayer.com Operational
cockney.4.mongolayer.com Operational
cockney.3.mongolayer.com Operational
cockney.2.mongolayer.com Operational
cockney.1.mongolayer.com Operational
cockney.0.mongolayer.com Operational
lamppost.16.mongolayer.com Operational
lamppost.17.mongolayer.com Operational
Legacy - AWS - US East 1 Operational
candidate.5.mongolayer.com Operational
candidate.15.mongolayer.com Operational
candidate.14.mongolayer.com Operational
candidate.16.mongolayer.com ? Operational
candidate.18.mongolayer.com Operational
candidate.19.mongolayer.com Operational
candidate.20.mongolayer.com Operational
candidate.32.mongolayer.com Operational
candidate.33.mongolayer.com Operational
candidate.34.mongolayer.com Operational
candidate.35.mongolayer.com ? Operational
candidate.36.mongolayer.com Operational
candidate.37.mongolayer.com ? Operational
candidate.38.mongolayer.com ? Operational
candidate.39.mongolayer.com ? Operational
candidate.41.mongolayer.com ? Operational
candidate.42.mongolayer.com Operational
candidate.43.mongolayer.com ? Operational
candidate.45.mongolayer.com ? Operational
candidate.44.mongolayer.com ? Operational
candidate.46.mongolayer.com ? Operational
candidate.47.mongolayer.com ? Operational
candidate.48.mongolayer.com ? Operational
candidate.49.mongolayer.com Operational
candidate.50.mongolayer.com Operational
candidate.51.mongolayer.com Operational
candidate.52.mongolayer.com Operational
candidate.53.mongolayer.com Operational
candidate.54.mongolayer.com Operational
candidate.55.mongolayer.com Operational
candidate.56.mongolayer.com Operational
candidate.57.mongolayer.com Operational
candidate.59.mongolayer.com Operational
candidate.60.mongolayer.com Operational
candidate.61.mongolayer.com Operational
candidate.62.mongolayer.com Operational
candidate.63.mongolayer.com ? Operational
candidate.64.mongolayer.com Operational
candidate.65.mongolayer.com Operational
candidate.66.mongolayer.com Operational
candidate.67.mongolayer.com Operational
candidate.68.mongolayer.com Operational
capital.0.mongolayer.com Operational
capital.1.mongolayer.com Operational
capital.2.mongolayer.com Operational
capital.3.mongolayer.com ? Operational
capital.5.mongolayer.com Operational
capital.6.mongolayer.com Operational
capital.7.mongolayer.com Operational
candidate.0.mongolayer.com ? Operational
candidate.1.mongolayer.com Operational
candidate.2.mongolayer.com Operational
candidate.3.mongolayer.com Operational
candidate.4.mongolayer.com Operational
candidate.6.mongolayer.com Operational
candidate.7.mongolayer.com Operational
candidate.10.mongolayer.com ? Operational
candidate.11.mongolayer.com ? Operational
candidate.12.mongolayer.com Operational
candidate.13.mongolayer.com Operational
candidate.17.mongolayer.com Operational
candidate.21.mongolayer.com Operational
candidate.40.mongolayer.com ? Operational
Legacy - AWS - US West 2 Operational
lighthouse.0.mongolayer.com ? Operational
lighthouse.1.mongolayer.com ? Operational
lighthouse.2.mongolayer.com ? Operational
lighthouse.3.mongolayer.com ? Operational
lighthouse.4.mongolayer.com ? Operational
lighthouse.5.mongolayer.com ? Operational
alcatraz.1.mongolayer.com ? Operational
alcatraz.0.mongolayer.com Operational
Legacy - Softlayer - Dallas - 05 Operational
horace.0.mongolayer.com Operational
horace.1.mongolayer.com Operational
Softlayer jp-tok Region Operational
sl-jp-tok-m02.dblayer.com Operational
Softlayer dal12 Region Operational
sl-us-south-1-data.67.dblayer.com Operational
sl-us-south-1-portal.52.dblayer.com Operational
sl-us-south-1-data.76.dblayer.com Operational
sl-us-south-1-data.64.dblayer.com Operational
sl-us-south-1-portal.49.dblayer.com Operational
sl-us-south-1-utility.47.dblayer.com Operational
sl-us-south-1-memory.25.dblayer.com Operational
sl-us-south-1-utility.32.dblayer.com Operational
sl-us-south-1-portal.55.dblayer.com Operational
sl-us-south-1-utility.50.dblayer.com Operational
sl-us-south-1-portal.34.dblayer.com Operational
sl-us-south-1-utility.35.dblayer.com Operational
sl-us-south-1-data.46.dblayer.com Operational
sl-us-south-1-memory.16.dblayer.com Operational
sl-us-south-1-data.73.dblayer.com Operational
Softlayer dal13 Region Operational
sl-us-south-1-portal.53.dblayer.com Operational
sl-us-south-1-data.65.dblayer.com Operational
sl-us-south-1-portal.56.dblayer.com Operational
sl-us-south-1-data.47.dblayer.com Operational
sl-us-south-1-utility.51.dblayer.com Operational
sl-us-south-1-portal.35.dblayer.com Operational
sl-us-south-1-utility.48.dblayer.com Operational
sl-us-south-1-utility.33.dblayer.com Operational
sl-us-south-1-memory.17.dblayer.com Operational
sl-us-south-1-data.68.dblayer.com Operational
sl-us-south-1-data.74.dblayer.com Operational
sl-us-south-1-utility.36.dblayer.com Operational
sl-us-south-1-portal.50.dblayer.com Operational
sl-us-south-1-data.77.dblayer.com Operational
sl-us-south-1-memory.26.dblayer.com Operational
sl-us-south-1-memory.29.dblayer.com Operational
Softlayer tok05 Region Operational
sl-jp-tok-d02.dblayer.com Operational
sl-jp-tok-p02.dblayer.com Operational
Softlayer fra05 Region Operational
sl-eu-de-1-data.17.dblayer.com Operational
sl-eu-de-1-data.20.dblayer.com Operational
sl-eu-de-1-memory.14.dblayer.com Operational
sl-eu-de-1-data.23.dblayer.com Operational
Softlayer fra02 Region Operational
sl-eu-de-1-memory.12.dblayer.com Operational
sl-eu-de-1-data.15.dblayer.com Operational
sl-eu-de-1-data.21.dblayer.com Operational
sl-eu-de-1-data.18.dblayer.com Operational
Softlayer london-02 Region Operational
sl-eu-lon-2-portal.13.dblayer.com Operational
sl-eu-lon-2-portal.9.dblayer.com Operational
sl-eu-lon-2-utility.9.dblayer.com Operational
sl-eu-lon-2-data.19.dblayer.com Operational
sl-eu-lon-2-memory.7.dblayer.com Operational
sl-eu-lon-2-data.17.dblayer.com Operational
sl-eu-lon-2-utility.10.dblayer.com Operational
sl-eu-lon-2-portal.14.dblayer.com Operational
sl-eu-lon-2-portal.11.dblayer.com Operational
sl-eu-lon-2-memory.9.dblayer.com Operational
sl-eu-lon-2-data.15.dblayer.com Operational
sl-eu-lon-2-data.16.dblayer.com Operational
sl-eu-lon-2-memory.8.dblayer.com Operational
sl-eu-lon-2-utility.11.dblayer.com Operational
sl-eu-lon-2-data.20.dblayer.com Operational
sl-eu-lon-2-portal.12.dblayer.com Operational
sl-eu-lon-2-data.18.dblayer.com Operational
sl-eu-lon-2-portal.10.dblayer.com Operational
Softlayer tok04 Region Operational
sl-jp-tok-d01.dblayer.com Operational
sl-jp-tok-m01.dblayer.com Operational
sl-jp-tok-p01.dblayer.com Operational
Softlayer syd01 Region Operational
sl-aus-syd-1-data.11.dblayer.com Operational
sl-aus-syd-1-data.13.dblayer.com Operational
sl-aus-syd-1-data.14.dblayer.com Operational
sl-aus-syd-1-data.12.dblayer.com Operational
sl-aus-syd-1-data.9.dblayer.com Operational
sl-aus-syd-1-data.10.dblayer.com Operational
Softlayer dal10 Region Operational
sl-us-south-1-data.66.dblayer.com Operational
sl-us-south-1-portal.48.dblayer.com Operational
sl-us-south-1-data.45.dblayer.com Operational
sl-us-south-1-data.75.dblayer.com Operational
sl-us-south-1-data.63.dblayer.com Operational
sl-us-south-1-memory.15.dblayer.com Operational
sl-us-south-1-utility.46.dblayer.com Operational
sl-us-south-1-portal.33.dblayer.com Operational
sl-us-south-1-utility.31.dblayer.com Operational
sl-us-south-1-utility.49.dblayer.com Operational
sl-us-south-1-portal.51.dblayer.com Operational
sl-us-south-1-portal.54.dblayer.com Operational
sl-us-south-1-data.72.dblayer.com Operational
sl-us-south-1-utility.34.dblayer.com Operational
sl-us-south-1-memory.24.dblayer.com Operational
Softlayer lon05 Region Operational
sl-eu-gb-p04.dblayer.com Operational
sl-eu-gb-m01.dblayer.com Operational
sl-eu-gb-d04.dblayer.com Operational
sl-eu-gb-d07.dblayer.com Operational
sl-eu-gb-d10.dblayer.com Operational
sl-eu-gb-d01.dblayer.com Operational
sl-eu-gb-p01.dblayer.com Operational
Softlayer dallas-09 Region Operational
sl-us-dal-9-utility.6.dblayer.com Operational
sl-us-dal-9-utility.2.dblayer.com Operational
sl-us-dal-9-utility.1.dblayer.com Operational
sl-us-dal-9-utility.7.dblayer.com Operational
sl-us-dal-9-portal.7.dblayer.com Operational
sl-us-dal-9-utility.0.dblayer.com Operational
Softlayer wdc06 Region Operational
sl-us-wdc-1-data.10.dblayer.com Operational
sl-us-wdc-1-data.7.dblayer.com Operational
Softlayer wdc07 Region Operational
sl-us-wdc-1-memory.5.dblayer.com Operational
sl-us-wdc-1-data.11.dblayer.com Operational
sl-us-wdc-1-data.8.dblayer.com Operational
Softlayer lon02 Region Operational
sl-eu-lon-2-memory.11.dblayer.com Operational
sl-eu-lon-2-memory.10.dblayer.com Operational
sl-eu-lon-2-memory.12.dblayer.com Operational
Softlayer lon04 Region Operational
sl-eu-gb-p03.dblayer.com Operational
sl-eu-gb-d03.dblayer.com Operational
sl-eu-gb-d06.dblayer.com Operational
sl-eu-gb-d09.dblayer.com Operational
sl-eu-gb-m00.dblayer.com Operational
sl-eu-gb-d00.dblayer.com Operational
sl-eu-gb-p00.dblayer.com Operational
gce europe-west1 Region Operational
gcp-europe-west1-data.5.dblayer.com Operational
gcp-europe-west1-data.3.dblayer.com Operational
gcp-europe-west1-data.4.dblayer.com Operational
gcp-europe-west1-cpu.3.dblayer.com Operational
gcp-europe-west1-cpu.5.dblayer.com Operational
gcp-europe-west1-cpu.4.dblayer.com Operational
Softlayer eu-de-1 Region Operational
sl-eu-de-1-portal.10.dblayer.com Operational
sl-eu-de-1-portal.12.dblayer.com Operational
sl-eu-de-1-portal.11.dblayer.com Operational
Softlayer fra04 Region Operational
sl-eu-de-1-data.16.dblayer.com Operational
sl-eu-de-1-data.22.dblayer.com Operational
sl-eu-de-1-memory.13.dblayer.com Operational
sl-eu-de-1-data.19.dblayer.com Operational
Softlayer lon06 Region Operational
sl-eu-gb-p05.dblayer.com Operational
sl-eu-gb-d08.dblayer.com Operational
sl-eu-gb-d11.dblayer.com Operational
sl-eu-gb-d05.dblayer.com Operational
sl-eu-gb-m02.dblayer.com Operational
sl-eu-gb-p02.dblayer.com Operational
sl-eu-gb-d02.dblayer.com Operational
Softlayer us-washingtondc-1 Region Operational
sl-us-wdc-1-memory.3.dblayer.com Operational
sl-us-wdc-1-data.5.dblayer.com Operational
sl-us-wdc-1-memory.4.dblayer.com Operational
sl-us-wdc-1-data.4.dblayer.com Operational
sl-us-wdc-1-data.3.dblayer.com Operational
Softlayer sydney-1 Region Operational
sl-aus-syd-1-portal.4.dblayer.com Operational
sl-aus-syd-1-utility.4.dblayer.com Operational
sl-aus-syd-1-portal.5.dblayer.com Operational
sl-aus-syd-1-utility.5.dblayer.com Operational
Softlayer wdc04 Region Operational
sl-us-wdc-1-data.9.dblayer.com Operational
sl-us-wdc-1-data.6.dblayer.com Operational
Softlayer tok02 Region Operational
sl-jp-tok-p00.dblayer.com Operational
sl-jp-tok-d00.dblayer.com Operational
sl-jp-tok-m00.dblayer.com Operational
Migration Service Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Jul 2, 2020
Emergency Maintenance - aws-ap-southeast-1-memory.1.dblayer.com
Resolved - The issue has been resolved and all systems are nominal.
Jul 2, 19:37 UTC
Monitoring - We have resolved the issue and are actively monitoring the situation.
Jul 2, 19:34 UTC
Identified - Beginning immediately Compose will be performing emergency maintenance on:

aws-ap-southeast-1-memory.1.dblayer.com

This emergeny maintenance includes non-portal hosts which, by the design of the Compose platform, should not affect the availability of your database deployments. No action on your part should be required before or during this maintenance. If during the maintenance you experience problems with your deployment, please contact us immediately at support@compose.com and we will work with you to resolve these issues.

These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

Affected deployments:

59fb5e348e3cd40016af9eed
5d4bdba72cfc336bedfef57e
5d56bdf41907b3000d55ccd2
5d752b5f2af8c2555c5106fa
5e00935e57dca4000d062dc3
5e1c2208c6ecdb0019f232fa
5e3b634b1c2221138b6ef592
5e7b48fafc2f9060ee3b243f
5ef61a748ffa9a0014ac7a61
5efc4185a2d707000e7fcc7c
5efc41e8f8263d28ac3419d5

If you have any questions about this maintenance, please email us at support@compose.com.
Jul 2, 19:25 UTC
Emergency Maintenance - aws-ap-southeast-1-utility.1.dblayer.com
Resolved - The issue has been resolved and all systems are nominal.
Jul 2, 19:25 UTC
Monitoring - We have resolved the issue and are actively monitoring the situation.
Jul 2, 19:19 UTC
Identified - Beginning immediately Compose will be performing emergency maintenance on:

aws-ap-southeast-1-utility.1.dblayer.com

This emergeny maintenance includes non-portal hosts which, by the design of the Compose platform, should not affect the availability of your database deployments. No action on your part should be required before or during this maintenance. If during the maintenance you experience problems with your deployment, please contact us immediately at support@compose.com and we will work with you to resolve these issues.

These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

Affected deployments:

58099d9257118a0019000004
586b46b2c38fc7001c000026
58762d93160bf2001a00003f
588345dc905a3e001700001e
589281427d9f440016000002
590830a84c4fb000154f7897
595eada310b7ac00116dd48b
59ae3d0c079e7a00170094e1
58ad03549dd6d7001600006a
5a1a5d02123a21519e1c1d00
5a54c0ca6f45c00014259443
5a55f6fdc607ae0019b96117
5a783c1dac6d770018f08fb1
5ac5e779ac188e00102d57b0
5ad32f17f0aec468f90f875c
5b5155dad48b64001d98cbe4
5b553255de49f900157f63d1
5b5ef84c36cc1a001a90ee04
5b7a60b4736508001dceffb8
5c91bc5e7849a7000b005951
5d62837477a27d000dcfff49
5dcd041adfa469000e1c1f67
5e147cc07d277633c92aaab1
5e301f37c8b297587bfad7d5
5e30fed78f598c6b1d8fef70
5e3b6ab10743cd001528e6dc
5e531dfff29ae8000e8e9cb2
5e69bec1bbb147000e83d490
5e6c61e8432c46001ae17888
5e7be4e59f80d0537eb41a56
5e7eab2d432c460dabe15478
5e917fc20aa32a01db402bbe
5e98555cdbfa8f001a81dedc
5e985cd312e002000e1a4e16
5ea25d35c4f077000e771f35
5ea31aaa67e3ba00143a58d4
5ea6fddb67e3ba00173aff75
5eaa807e4476cf000edea181
5ece67ff43f23a2a58623d02
5ece6d828f8a3f0011b2b979
5ee01280bc02bd49ecf04615
5eeb6acd879bcb00177a700b
5eec598d401af7000ffff7c5
5eecb3428fc3eb00173cade8
5ef4d0b7ba17db001a9424de
5efaf2281e43b1000e21048f

If you have any questions about this maintenance, please email us at support@compose.com.
Jul 2, 18:40 UTC
Emergency Maintenance - aws-ap-southeast-1-data.1.dblayer.com
Resolved - The issue has been resolved and all systems are nominal.
Jul 2, 14:10 UTC
Monitoring - We have resolved the issue and are actively monitoring the situation.
Jul 2, 13:58 UTC
Identified - Beginning immediately Compose will be performing emergency maintenance on:

aws-ap-southeast-1-data.1.dblayer.com

This emergeny maintenance includes non-portal hosts which, by the design of the Compose platform, should not affect the availability of your database deployments. No action on your part should be required before or during this maintenance. If during the maintenance you experience problems with your deployment, please contact us immediately at support@compose.com and we will work with you to resolve these issues.

These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

Affected deployments:

586b46b2c38fc7001c000026
58762d93160bf2001a00003f
588345dc905a3e001700001e
589281427d9f440016000002
58ad03549dd6d7001600006a
58b59e9284b41e001c000000
590830a84c4fb000154f7897
59ae3d0c079e7a00170094e1
5ac5e779ac188e00102d57b0
5ad32f17f0aec468f90f875c
5e50fb5bf29ae8000e8e4437
5e531dfff29ae8000e8e9cb2
5e7b48d01a02d158af9c9b48
5e7be4e59f80d0537eb41a56
5e985cd312e002000e1a4e16
5ea31aaa67e3ba00143a58d4
5ece67ff43f23a2a58623d02
5ece6d828f8a3f0011b2b979
5ee01280bc02bd49ecf04615
5eeb6acd879bcb00177a700b
5eec598d401af7000ffff7c5
5eecb3428fc3eb00173cade8

If you have any questions about this maintenance, please email us at support@compose.com.
Jul 2, 13:35 UTC
Emergency Maintenance - aws-ap-southeast-1-data.2.dblayer.com
Resolved - The issue has been resolved and all systems are nominal.
Jul 2, 00:54 UTC
Monitoring - We have resolved the issue and are actively monitoring the situation.
Jul 2, 00:54 UTC
Identified - Beginning immediately Compose will be performing emergency maintenance on:

aws-ap-southeast-1-data.2.dblayer.com

This emergeny maintenance includes non-portal hosts which, by the design of the Compose platform, should not affect the availability of your database deployments. No action on your part should be required before or during this maintenance. If during the maintenance you experience problems with your deployment, please contact us immediately at support@compose.com and we will work with you to resolve these issues.

These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

Affected deployments:

586b46b2c38fc7001c000026
58762d93160bf2001a00003f
588345dc905a3e001700001e
589281427d9f440016000002
58ad03549dd6d7001600006a
58b59e9284b41e001c000000
590830a84c4fb000154f7897
59ae3d0c079e7a00170094e1
5ac5e779ac188e00102d57b0
5ad32f17f0aec468f90f875c
5e7b48d01a02d158af9c9b48
5e7be4e59f80d0537eb41a56
5e985cd312e002000e1a4e16
5ea25d35c4f077000e771f35
5ea31aaa67e3ba00143a58d4
5ece67ff43f23a2a58623d02
5ece6d828f8a3f0011b2b979
5ee01280bc02bd49ecf04615
5eeb6acd879bcb00177a700b
5ef4d0b7ba17db001a9424de

If you have any questions about this maintenance, please email us at support@compose.com.
Jul 1, 20:27 UTC
Jul 1, 2020
Emergency Maintenance - aws-ap-southeast-1-memory.0.dblayer.com
Resolved - The issue has been resolved and all systems are nominal.
Jul 1, 19:29 UTC
Monitoring - We have resolved the issue and are actively monitoring the situation.
Jul 1, 19:29 UTC
Identified - Beginning immediately Compose will be performing emergency maintenance on:

aws-ap-southeast-1-memory.0.dblayer.com

This emergeny maintenance includes non-portal hosts which, by the design of the Compose platform, should not affect the availability of your database deployments. No action on your part should be required before or during this maintenance. If during the maintenance you experience problems with your deployment, please contact us immediately at support@compose.com and we will work with you to resolve these issues.

These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

Affected deployments:

58099d9257118a0019000004
595eada310b7ac00116dd48b
59fb5e348e3cd40016af9eed
5d4bdba72cfc336bedfef57e
5d56bdf41907b3000d55ccd2
5d752b5f2af8c2555c5106fa
5e00935e57dca4000d062dc3
5e1c2208c6ecdb0019f232fa
5e3b634b1c2221138b6ef592
5ef61a748ffa9a0014ac7a61
5efc4185a2d707000e7fcc7c
5efc41e8f8263d28ac3419d5

If you have any questions about this maintenance, please email us at support@compose.com.
Jul 1, 19:06 UTC
Emergency Maintenance - aws-ap-southeast-1-data.0.dblayer.com
Resolved - The issue has been resolved and all systems are nominal.
Jul 1, 18:54 UTC
Monitoring - We have resolved the issue and are actively monitoring the situation.
Jul 1, 18:44 UTC
Identified - Beginning immediately Compose will be performing emergency maintenance on:

aws-ap-southeast-1-data.0.dblayer.com

This emergeny maintenance includes non-portal hosts which, by the design of the Compose platform, should not affect the availability of your database deployments. No action on your part should be required before or during this maintenance. If during the maintenance you experience problems with your deployment, please contact us immediately at support@compose.com and we will work with you to resolve these issues.

These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

Affected deployments:

586b46b2c38fc7001c000026
58762d93160bf2001a00003f
588345dc905a3e001700001e
589281427d9f440016000002
58b59e9284b41e001c000000
590830a84c4fb000154f7897
59ae3d0c079e7a00170094e1
5ac5e779ac188e00102d57b0
5ad32f17f0aec468f90f875c
5e50fb5bf29ae8000e8e4437
5e531dfff29ae8000e8e9cb2
5e7eab2d432c460dabe15478
5e917fc20aa32a01db402bbe
5e98555cdbfa8f001a81dedc
5ece67ff43f23a2a58623d02
5ee01280bc02bd49ecf04615
5eeb6acd879bcb00177a700b
5eec598d401af7000ffff7c5
5eecb3428fc3eb00173cade8

If you have any questions about this maintenance, please email us at support@compose.com.
Jul 1, 18:23 UTC
Jun 30, 2020
Emergency Maintenance - gcp-us-east1-data.4.dblayer.com
Resolved - The issue has been resolved and all systems are nominal.
Jun 30, 10:30 UTC
Monitoring - We have resolved the issue and are actively monitoring the situation.
Jun 30, 10:27 UTC
Update - Running some repairs on the re-created capsules to ensure data is fully replicated.
Jun 30, 09:58 UTC
Update - All capsules are now back up and running.
Jun 30, 09:57 UTC
Update - Capsules have been re-created. Deployments are returning to full health.
Jun 30, 09:51 UTC
Update - It's not been possible to recover this instance so we are rebuilding as new.
Jun 30, 09:45 UTC
Update - We are still working with GCP support to see if the instance can be recovered.
Jun 30, 00:52 UTC
Update - All capsules are now back up and running.
Jun 30, 00:31 UTC
Update - Creating a separate status page for just this host as a continuation of this earlier outage: https://status.compose.com/incidents/hvbgyq4mdl05

We are still working with GCP support to see if the instance can be recovered.
Jun 29, 22:05 UTC
Identified - Beginning immediately Compose will be performing emergency maintenance on:

gcp-us-east1-data.4.dblayer.com

This emergeny maintenance includes non-portal hosts which, by the design of the Compose platform, should not affect the availability of your database deployments. No action on your part should be required before or during this maintenance. If during the maintenance you experience problems with your deployment, please contact us immediately at support@compose.com and we will work with you to resolve these issues.

These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

Affected deployments:

58ec23860d96980016823f24
58f56116460ef0001512cec7
58f7fa07753b2c00167a3882
5916480672891e000f262cde
592a302b0460bfb18b77ba5e
593d636d77d12b0012ad49d6
598875c733fbeb031800427b
59b30124874a1c00140191fa
59b99fbff163f200140000a7
59b99fd0f163f200140000c3
59ba6a2c58f3db0026003d84
59bf94da76c94f001400153f
59d44745b89b34001400544b
5ba012f5ef7b2900111f73a3
5c658b080ae82f736164b176
5e01ccce44b97000196aa50e
5e444aae1c22214ade6f355b
5e444fee0743cd3da129092a
5e64a1bd0743cd74f25fbcac

If you have any questions about this maintenance, please email us at support@compose.com.
Jun 29, 22:04 UTC
Jun 29, 2020
Suspected Google Cloud Platform outage in us-east1-c
Resolved - We are closing this status page out and we've opened one just for the remaining host: https://status.compose.com/incidents/6p5byj9kbt86
Jun 29, 22:06 UTC
Update - The issue with gcp-us-east1-data.4.dblayer.com has been escalated to the Google Compute Engine product team.
Jun 29, 21:53 UTC
Update - We've a ticket open with Google to see if gcp-us-east1-data.4 can be recovered.
Jun 29, 20:00 UTC
Update - We've just gcp-us-east1-data.4 remaining offline. It's been automatically terminated by Google, but hasn't completed migration yet.
Jun 29, 18:49 UTC
Update - We've the majority of the hosts up now.
Jun 29, 18:38 UTC
Update - We have been able to recover networking on some instances by rebooting them. We are working through those still listed as Major outage.
Jun 29, 18:26 UTC
Update - We've seen a few hosts come back, but the majority remain inaccessible. Google still have the related networking incident open.
Jun 29, 18:16 UTC
Identified - Upstream incidents are here:

- https://status.cloud.google.com/incident/compute/20004
- https://status.cloud.google.com/incident/cloud-networking/20005
Jun 29, 16:04 UTC
Update - It's been confirmed by Google that it's a known issue in us-east1-c. As of right now their status page doesn't show it, but it's a known issue via internal support.
Jun 29, 15:38 UTC
Update - We are seeing some hosts being auto-migrated
Jun 29, 15:28 UTC
Investigating - Our monitoring has identified issues in the us-east1-c zone for Google Cloud Platform. We are trying to confirm whether it's an upstream issue. This should not affect deployment availability.
Jun 29, 15:22 UTC
Jun 28, 2020

No incidents reported.

Jun 27, 2020

No incidents reported.

Jun 26, 2020

No incidents reported.

Jun 25, 2020
Emergency Maintenance - gcp-us-east1-memory.0.dblayer.com
Resolved - The issue has been resolved and all systems are nominal.
Jun 25, 09:37 UTC
Monitoring - We have resolved the issue and are actively monitoring the situation.
Jun 25, 09:27 UTC
Update - Host is back up and capsules are being restarted
Jun 25, 09:20 UTC
Update - We are performing a quick reboot on this host. Deployments have been failed over.
Jun 25, 09:13 UTC
Identified - Beginning immediately Compose will be performing emergency maintenance on:

gcp-us-east1-memory.0.dblayer.com

This emergeny maintenance includes non-portal hosts which, by the design of the Compose platform, should not affect the availability of your database deployments. No action on your part should be required before or during this maintenance. If during the maintenance you experience problems with your deployment, please contact us immediately at support@compose.com and we will work with you to resolve these issues.

These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

Affected deployments:

57d98909fe7ea8001d00000a
57d98980168a800019000003
57e93125bf49b4be17000004
57e98d095d7d780019000003
5855203706058d0019000011
5877d8d218cd6f001800007b
589cdc9d8903980018000006
58a481479faba1001900002b
58bed9b9fc8027001600000d
59bc4d4999c4430020000d9e
5acbbd2fcaacf4025e14c341
5aefc1d5587d0a0015ef9c90
5af312757852906382d9c439
5b272da3594c6933ae755389
5c0ef353de2c21619f0bd42f
5c4632490bd4cc000bbb8a2e
5ca465787e000b000bbb4444
5d0741bce9f8b5000b36f8b2
5d10dbae3c0f0d1ad3dc1570
5d24a65f92fc21000d70a247
5d24b79e0004cc000dfa1a27
5d4bd446c045f03bb5cc1635
5d529f748f2aff01d6c5e79a
5d5d5a314c496c0a5c9d9aca
5d92f1d7247cdf10a7bb4677
5d93e03e7654d174ab478ae6
5d93e6d4247cdf20d3bb4d18
5dc18b52e2fd3c3430f70a45
5dc19d91b938875f2cfdf021
5ddc20528043b52325f30613

If you have any questions about this maintenance, please email us at support@compose.com.
Jun 25, 09:12 UTC
Emergency Maintenance - gcp-us-east1-memory.4.dblayer.com
Resolved - The issue has been resolved and all systems are nominal.
Jun 25, 00:19 UTC
Monitoring - We have resolved the issue and are actively monitoring the situation.
Jun 25, 00:17 UTC
Identified - Beginning immediately Compose will be performing emergency maintenance on:

gcp-us-east1-memory.4.dblayer.com

This emergeny maintenance includes non-portal hosts which, by the design of the Compose platform, should not affect the availability of your database deployments. No action on your part should be required before or during this maintenance. If during the maintenance you experience problems with your deployment, please contact us immediately at support@compose.com and we will work with you to resolve these issues.

These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

Affected deployments:

58f6d15b6c05800014c057c1
5903bc994e883b000ec6b7e7
5916482a632b310012ea4756
5973ec0b1f19f6001209cc2b
59b99fc858f3db001e000119
59e7960dbede700019ce789b
59fc6e2086ff7600148338d6
5afa57cd31c6510019db5649
5afa5883e120fecb655f4fe0
5b9bf5589434e045730eef62
5ca478db7e000b000ebb41a4
5d4bd4778f2aff5572c63a00
5dc18b52e2fd3c3430f70a45
5dc19d91b938875f2cfdf021
5e8760d91a02d145ae9c2e62
5e87a41bfc2f9000143f1be2
5ee9c014f7c22d473b3b785f

If you have any questions about this maintenance, please email us at support@compose.com.
Jun 25, 00:03 UTC
Emergency Maintenance - gcp-europe-west1-memory.2.dblayer.com
Resolved - The issue has been resolved and all systems are nominal.
Jun 25, 00:01 UTC
Monitoring - We have resolved the issue and are actively monitoring the situation.
Jun 25, 00:00 UTC
Identified - Beginning immediately Compose will be performing emergency maintenance on:

gcp-europe-west1-memory.2.dblayer.com

This emergeny maintenance includes non-portal hosts which, by the design of the Compose platform, should not affect the availability of your database deployments. No action on your part should be required before or during this maintenance. If during the maintenance you experience problems with your deployment, please contact us immediately at support@compose.com and we will work with you to resolve these issues.

These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

Affected deployments:

57bdebf5df06bf0016000000
5970bf39e0da4900157400bb
5970c0af7c61c9000e7b148b
59bff7b4d55aa30014000a19
59bffb2c1781ed00140009f3
59e88a71cf91530024859270
5a4b87c6c28d0a001897a0c1
5a4bdea99f505f00100c2ff0
5a786c24c92efc001176cdd3
5ab8e425372c0e0018fabdad
5e3d38ae20cdcf22caffe873
5e46d9db20cdcf4632009f6d
5e46db403dd82b632db0bcc2
5e46dddef29ae84e978aed83
5e484a3920cdcf6c76000576

If you have any questions about this maintenance, please email us at support@compose.com.
Jun 24, 23:33 UTC
Jun 24, 2020
Emergency Maintenance - gcp-europe-west1-memory.4.dblayer.com
Resolved - The issue has been resolved and all systems are nominal.
Jun 24, 22:16 UTC
Monitoring - We have resolved the issue and are actively monitoring the situation.
Jun 24, 22:02 UTC
Identified - Beginning immediately Compose will be performing emergency maintenance on:

gcp-europe-west1-memory.4.dblayer.com

This emergeny maintenance includes non-portal hosts which, by the design of the Compose platform, should not affect the availability of your database deployments. No action on your part should be required before or during this maintenance. If during the maintenance you experience problems with your deployment, please contact us immediately at support@compose.com and we will work with you to resolve these issues.

These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

Affected deployments:

5b7dffb01c1073000edf8d8d
5beb1c41efc41e000eb4627a
5c6a6820287d83000bd8d3f2
5cf8df3e37f68951fc398e42
5d14d921f1f92e0016bbfd83
5d384f1f47954d384baafc2e
5d517daeb046e47e4c6e9de9
5d83566a02e5aa459a2a904a
5d978b95247cdf72b9bc34c9
5d978dfe07cd0035966ddaca
5d9c9a8407cd00633c6e435d
5d9c9cf607cd001cdc6dc150
5d9db43a02e5aa0f992afd3f
5d9dc28b9c337455dc74861f
5dee58dc44b97000160dd07b
5e6774e40cf2ce382332eedd
5e7e6c2bfc2f9010c33ac7b9
5e7e6dd79f80d006fcb371bc
5ecf6abd2b462d0017daf661

If you have any questions about this maintenance, please email us at support@compose.com.
Jun 24, 21:44 UTC
Emergency Maintenance - gcp-us-east1-memory.7.dblayer.com
Resolved - The issue has been resolved and all systems are nominal.
Jun 24, 21:42 UTC
Monitoring - We have resolved the issue and are actively monitoring the situation.
Jun 24, 21:23 UTC
Identified - Beginning immediately Compose will be performing emergency maintenance on:

gcp-us-east1-memory.7.dblayer.com

This emergeny maintenance includes non-portal hosts which, by the design of the Compose platform, should not affect the availability of your database deployments. No action on your part should be required before or during this maintenance. If during the maintenance you experience problems with your deployment, please contact us immediately at support@compose.com and we will work with you to resolve these issues.

These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

Affected deployments:

5a32b5e051e4fe001803a728
5a45116827b04a001408c048
5a455cb027b04a001408c6ec
5a4c2f430a09d0001ba1d4da
5a57be30ceb7750011960593
5a5ab6450bb58f0016e495f9
5a6ca02aac6d770018ecca02
5af312757852906382d9c439
5b271225594c6933b1753b75
5b272da3594c6933ae755389
5c0ef353de2c21619f0bd42f
5c1994ccde2c21619f0d9eae
5c4a30920bd4cc0011bc42f7
5c524e53dba5b900111e9d13
5c5752318f946100117ce13a
5c587d7adba5b9000e1faec4
5d3b69801ba39037267c45f2
5d6fdfac63a21a000d1f589f
5d8250ae9c337442c0735c7a
5ea09281dea248001700a2a4
5ea8a3912272b30011aa6493
5ea8abc5daa9dc00147544cc
5ea8ef5cb66691001167cf37
5ee019b12b462d612fdb66d6

If you have any questions about this maintenance, please email us at support@compose.com.
Jun 24, 21:07 UTC
Emergency Maintenance - gcp-us-east1-memory.6.dblayer.com
Resolved - The issue has been resolved and all systems are nominal.
Jun 24, 16:59 UTC
Monitoring - We have resolved the issue and are actively monitoring the situation.
Jun 24, 16:58 UTC
Identified - Beginning immediately Compose will be performing emergency maintenance on:

gcp-us-east1-memory.6.dblayer.com

This emergeny maintenance includes non-portal hosts which, by the design of the Compose platform, should not affect the availability of your database deployments. No action on your part should be required before or during this maintenance. If during the maintenance you experience problems with your deployment, please contact us immediately at support@compose.com and we will work with you to resolve these issues.

These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

Affected deployments:

5a45116827b04a001408c048
5a455cb027b04a001408c6ec
5a4c2f430a09d0001ba1d4da
5a57be30ceb7750011960593
5a58e2c6c607ae0011ba4ac1
5a6ca02aac6d770018ecca02
5a6ca0dfac6d770010ebdd36
5b1478ead297985d60508a4c
5b147964d297985d60508a6a
5c4a30920bd4cc0011bc42f7
5c5752318f946100117ce13a
5d3925c20ef45e0019755a82
5d3b69801ba39037267c45f2
5d4c1b62b046e42f456e5c4d
5e3a454e0743cd000e7e3c6c
5e444936f29ae8476d8aac18
5e444c99f29ae841a98ad137
5ea09281dea248001700a2a4
5ea8a3912272b30011aa6493
5ea8ef5cb66691001167cf37
5ee019b12b462d612fdb66d6
5ee9c014f7c22d473b3b785f

If you have any questions about this maintenance, please email us at support@compose.com.
Jun 24, 16:43 UTC
Emergency Maintenance - gcp-europe-west1-memory.5.dblayer.com
Resolved - The issue has been resolved and all systems are nominal.
Jun 24, 15:57 UTC
Monitoring - We have resolved the issue and are actively monitoring the situation.
Jun 24, 15:57 UTC
Identified - Beginning immediately Compose will be performing emergency maintenance on:

gcp-europe-west1-memory.5.dblayer.com

This emergeny maintenance includes non-portal hosts which, by the design of the Compose platform, should not affect the availability of your database deployments. No action on your part should be required before or during this maintenance. If during the maintenance you experience problems with your deployment, please contact us immediately at support@compose.com and we will work with you to resolve these issues.

These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

Affected deployments:

5af1599b587d0a7f19f0be49
5b3a3ec32c93b300115a2cf5
5beb1c41efc41e000eb4627a
5c6a6820287d83000bd8d3f2
5ce57725949851000b30aab8
5cf8df3e37f68951fc398e42
5d08c9e5e9f8b5001136f79e
5d14d921f1f92e0016bbfd83
5d83566a02e5aa459a2a904a
5d978b95247cdf72b9bc34c9
5d9db43a02e5aa0f992afd3f
5dee58dc44b97000160dd07b
5e6774e40cf2ce382332eedd
5e7e6c2bfc2f9010c33ac7b9
5e7e6dd79f80d006fcb371bc
5e9ec0ae52332e00118f356f
5ea8e8762272b3001aaa7239
5eb945dac1353b001134b6cb
5ecf6abd2b462d0017daf661
5ee241943b34af6e4c1297f1

If you have any questions about this maintenance, please email us at support@compose.com.
Jun 24, 15:30 UTC
Emergency Maintenance - gcp-us-east1-memory.5.dblayer.com
Resolved - The issue has been resolved and all systems are nominal.
Jun 24, 15:28 UTC
Monitoring - We have resolved the issue and are actively monitoring the situation.
Jun 24, 15:27 UTC
Identified - Beginning immediately Compose will be performing emergency maintenance on:

gcp-us-east1-memory.5.dblayer.com

This emergeny maintenance includes non-portal hosts which, by the design of the Compose platform, should not affect the availability of your database deployments. No action on your part should be required before or during this maintenance. If during the maintenance you experience problems with your deployment, please contact us immediately at support@compose.com and we will work with you to resolve these issues.

These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

Affected deployments:

5903bc994e883b000ec6b7e7
5916482a632b310012ea4756
59429b1aaac64b0011f575d5
596d483de20fa300114c97dd
5973ec0b1f19f6001209cc2b
59849583c647430344001d05
5984e36b630a3b02f000216f
59949b086772f7001400329b
59b99fc858f3db001e000119
59bc4d4999c4430020000d9e
5aefc1d5587d0a0015ef9c90
5afa5883e120fecb655f4fe0
5b9bf5589434e045730eef62
5ca465787e000b000bbb4444
5ca478db7e000b000ebb41a4
5cd1ddeebef8c1001895e84b
5d0741bce9f8b5000b36f8b2
5d0cec3f0f4dc400136249ff
5d10dbae3c0f0d1ad3dc1570
5d1165fd88f478000ddb0d4a
5d24a65f92fc21000d70a247
5d24b79e0004cc000dfa1a27
5d3925c20ef45e0019755a82
5d3b69801ba39037267c45f2
5d4bd446c045f03bb5cc1635
5d4bd4778f2aff5572c63a00
5d4c1b62b046e42f456e5c4d
5d529f748f2aff01d6c5e79a
5d5d5a314c496c0a5c9d9aca
5d6fdf83d95592000d661778
5d6fdfac63a21a000d1f589f
5d92f1d7247cdf10a7bb4677

If you have any questions about this maintenance, please email us at support@compose.com.
Jun 24, 15:03 UTC
Emergency Maintenance - gcp-europe-west1-memory.1.dblayer.com
Resolved - The issue has been resolved and all systems are nominal.
Jun 24, 14:56 UTC
Monitoring - We have resolved the issue and are actively monitoring the situation.
Jun 24, 14:48 UTC
Identified - Beginning immediately Compose will be performing emergency maintenance on:

gcp-europe-west1-memory.1.dblayer.com

This emergeny maintenance includes non-portal hosts which, by the design of the Compose platform, should not affect the availability of your database deployments. No action on your part should be required before or during this maintenance. If during the maintenance you experience problems with your deployment, please contact us immediately at support@compose.com and we will work with you to resolve these issues.

These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

Affected deployments:

57b5bedfc67f5c0019000004
59e88a71cf91530024859270
59edd9a02f942800196227e8
5a26954d2b98130018056652
5a4b87c6c28d0a001897a0c1
5a7813a4ed40e20014c79eae
5a786c24c92efc001176cdd3
5ab8e425372c0e0018fabdad
5e3d38ae20cdcf22caffe873
5e46d9db20cdcf4632009f6d
5e46db403dd82b632db0bcc2
5e46dddef29ae84e978aed83
5e484a3920cdcf6c76000576
5ea8e8762272b3001aaa7239

If you have any questions about this maintenance, please email us at support@compose.com.
Jun 24, 14:22 UTC
Emergency Maintenance - gcp-us-east1-memory.2.dblayer.com
Resolved - The issue has been resolved and all systems are nominal.
Jun 24, 14:56 UTC
Monitoring - We have resolved the issue and are actively monitoring the situation.
Jun 24, 14:23 UTC
Identified - Beginning immediately Compose will be performing emergency maintenance on:

gcp-us-east1-memory.2.dblayer.com

This emergeny maintenance includes non-portal hosts which, by the design of the Compose platform, should not affect the availability of your database deployments. No action on your part should be required before or during this maintenance. If during the maintenance you experience problems with your deployment, please contact us immediately at support@compose.com and we will work with you to resolve these issues.

These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

Affected deployments:

57d98909fe7ea8001d00000a
57d98980168a800019000003
57e93125bf49b4be17000004
57e98d095d7d780019000003
5855203706058d0019000011
5876e24f77419d001600006a
5877d8d218cd6f001800007b
589cdc9d8903980018000006
58a481479faba1001900002b
599317c3de96550018000c77
59931d66de96550014000e00
5acbbd2fcaacf4025e14c341
5af312757852906382d9c439
5b1478ead297985d60508a4c
5c1994ccde2c21619f0d9eae
5c4632490bd4cc000bbb8a2e
5dc18b52e2fd3c3430f70a45
5dc19d91b938875f2cfdf021

If you have any questions about this maintenance, please email us at support@compose.com.
Jun 24, 14:09 UTC
Emergency Maintenance - gcp-europe-west1-data.2.dblayer.com
Resolved - The issue has been resolved and all systems are nominal.
Jun 24, 10:48 UTC
Monitoring - We have resolved the issue and are actively monitoring the situation.
Jun 24, 10:42 UTC
Update - Host is back up. Capsules are being restarted.
Jun 24, 10:38 UTC
Update - Performing a quick reboot again. Deployments have been failed over.
Jun 24, 10:29 UTC
Identified - Beginning immediately Compose will be performing emergency maintenance on:

gcp-europe-west1-data.2.dblayer.com

This emergeny maintenance includes non-portal hosts which, by the design of the Compose platform, should not affect the availability of your database deployments. No action on your part should be required before or during this maintenance. If during the maintenance you experience problems with your deployment, please contact us immediately at support@compose.com and we will work with you to resolve these issues.

These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

Affected deployments:

5771482ae38bed001d00000d
57861f760b78740019000007
57b4443e6d273b0016000007
57bd5402e2ff190016000003
57d93705401591001c000008
57e24b9c2b85d8001f000014
57fcb16971c66d001f000012
58089a71028b01001c00001a
581f5521e07a31001c00003f
58219b0dce03cc0018000042
5823288c5201fc001600005e
582450870ca53a001a00000d
5836e5f4dc2d5b0019000036
5868e42bc38fc7001c00001b
586e2013b96bdc0017000017
587112d977419d001600000e
58da9de437d7d6000efaf576
59195dc6632b310015ea476d
5939233e67ef6800152f3571
5979bc3defaafb00143654db
599ee330f32fb6001000d80f
59a52cda65c417001501a344
59c7d93a0f28980015010b75
59d36db7c948ca0026006308
5a15eb9953888300180fdfd3
5a296ce2eb06d800246536bc
5a30e85e9ad0e6001858e863
5ab0f625821ffb00110daa20
5aba3444384ccd00189cc246
5ac64fa93d580a024ccb3a6d
5afd6f3c208ba400157e6276
5b06644d3a1e660027e37b28
5b2763c6f98b190021dc9594
5b38b6d214d08c0019064b7a
5b3b3c13a8b1ad00196ae65a
5b47dc0ebd93fc001560e93a
5b556e851c0fc2001d130aa5
5bab91b98807bd2dda53dc70
5bb1da7e8807bd7e57536a3a
5c07daaff342900017dcbff1
5c6a64aec1b403000b5aa058
5e484aaf3dd82b52b1b14d73
5e7e0a72432c460011e468d8
5e7e3a6efc2f9048f33c30a3
5e9ebfcf4c9f40214071cb19
5eb1580eb666910014692101
5eb260572272b30011abfe2a
5eb26077b666912400688429
5ed78d812b462d0011dc3045
5edf556b4fbd582a1b51e596
5ee0c60ca7d6e569fc7b2a45
5ee78b1fbc02bd49ecf17155

If you have any questions about this maintenance, please email us at support@compose.com.
Jun 24, 10:29 UTC
Emergency Maintenance - gcp-europe-west1-data.5.dblayer.com
Resolved - The issue has been resolved and all systems are nominal.
Jun 24, 10:47 UTC
Monitoring - We have resolved the issue and are actively monitoring the situation.
Jun 24, 10:42 UTC
Update - Host is back up. Capsules are being restarted.
Jun 24, 10:38 UTC
Update - Performing a quick reboot again. Deployments have been failed over.
Jun 24, 10:29 UTC
Identified - Beginning immediately Compose will be performing emergency maintenance on:

gcp-europe-west1-data.5.dblayer.com

This emergeny maintenance includes non-portal hosts which, by the design of the Compose platform, should not affect the availability of your database deployments. No action on your part should be required before or during this maintenance. If during the maintenance you experience problems with your deployment, please contact us immediately at support@compose.com and we will work with you to resolve these issues.

These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

Affected deployments:

5cc017a86a7402699393d55f
5d43dd528f2aff0019c58ec9
5d4ab18ec045f02ae8cc0bca
5d566f9b8453960013b7661a
5d6902b5807d34000de3e44b
5d6e37cc11b979449e06b13d
5d8c084fa33a4519cecbdce8
5d8c0bd59c33747bb4748e60
5dc53d99312020000d3a87f7
5dcd77da9ba01f00161b9cf2
5e15eb4357dca462a104e322
5e38e37af29ae8000e665354
5e53121e1c22210bfa70133e
5e5906f3f29ae8000e8f95ec
5e6213430743cd4d94602a34

If you have any questions about this maintenance, please email us at support@compose.com.
Jun 24, 10:28 UTC
Emergency Maintenance - gcp-us-east1-data.5.dblayer.com
Resolved - The issue has been resolved and all systems are nominal.
Jun 24, 10:47 UTC
Monitoring - We have resolved the issue and are actively monitoring the situation.
Jun 24, 10:42 UTC
Update - Host is back up. Capsules are being restarted.
Jun 24, 10:38 UTC
Update - Performing a quick reboot again. Deployments have been failed over.
Jun 24, 10:29 UTC
Identified - Beginning immediately Compose will be performing emergency maintenance on:

gcp-us-east1-data.5.dblayer.com

This emergeny maintenance includes non-portal hosts which, by the design of the Compose platform, should not affect the availability of your database deployments. No action on your part should be required before or during this maintenance. If during the maintenance you experience problems with your deployment, please contact us immediately at support@compose.com and we will work with you to resolve these issues.

These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

Affected deployments:

58cad0b69407120011b450d7
58ec23860d96980016823f24
58f56116460ef0001512cec7
58f7fa07753b2c00167a3882
5916480672891e000f262cde
592a302b0460bfb18b77ba5e
593d636d77d12b0012ad49d6
5ad8e64ac826350010310938
5b16ee5d1ef7ce00116bab94
5d3b67adcd507e00101f32d7
5d4b8fd6c045f07d97cc84ec
5d9ce3ff9c337406e47347c6
5daf755a16baa94d6253bd28
5e3a4436f29ae8001a8aa86d
5e444aae1c22214ade6f355b
5e444fee0743cd3da129092a
5e64a1bd0743cd74f25fbcac
5e872b4cfc2f9020f03bc0a7

If you have any questions about this maintenance, please email us at support@compose.com.
Jun 24, 10:28 UTC
Emergency Maintenance - gcp-us-east1-data.8.dblayer.com
Resolved - The issue has been resolved and all systems are nominal.
Jun 24, 10:47 UTC
Monitoring - We have resolved the issue and are actively monitoring the situation.
Jun 24, 10:42 UTC
Update - Host is back up. Capsules are being restarted.
Jun 24, 10:38 UTC
Update - Performing a quick reboot again. Deployments have been failed over.
Jun 24, 10:29 UTC
Identified - Beginning immediately Compose will be performing emergency maintenance on:

gcp-us-east1-data.8.dblayer.com

This emergeny maintenance includes non-portal hosts which, by the design of the Compose platform, should not affect the availability of your database deployments. No action on your part should be required before or during this maintenance. If during the maintenance you experience problems with your deployment, please contact us immediately at support@compose.com and we will work with you to resolve these issues.

These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

Affected deployments:

5a0464f9c53eff00230218ee
5a26bfb2e7217e00183efa1e
5a2fde7c12608300107c50d8
5a66aac6bce8bd00193b3231
5a6ca24eed40e20010c43c23
5a6ca28972babf0014ce21ba
5ac4f4ad542c300a607e4dbd
5aefc32c7852906e0ed9db99
5b45da0ba8d92a00118a7bfa
5b4861c6f9c8d50019c34c60
5b644c3cf509f5001182ca5e
5ba012f5ef7b2900111f73a3
5ba013754ce0d90d9ad15b6e
5c19635df27619638b65893a
5c211939d23f94000b09e7e7
5c463091b011eb000f9a21ea
5c4631bb906fc70011d7f2b7
5c658b080ae82f736164b176
5e01ccce44b97000196aa50e
5ea8a7bfdaa9dc00177544ab
5ee154eaf7c22d7c5e391d90
5ee7a7efbc02bd2520ef8d43
5ee8f9f92b462d612fdcc1c4

If you have any questions about this maintenance, please email us at support@compose.com.
Jun 24, 10:28 UTC
Emergency Maintenance - gcp-europe-west1-data.1.dblayer.com
Resolved - The issue has been resolved and all systems are nominal.
Jun 24, 09:39 UTC
Monitoring - We have resolved the issue and are actively monitoring the situation.
Jun 24, 09:31 UTC
Update - Host is back up. Capsules are being restarted.
Jun 24, 09:26 UTC
Update - We are performing a quick reboot on this host. Deployments have been failed over.
Jun 24, 09:18 UTC
Identified - Beginning immediately Compose will be performing emergency maintenance on:

gcp-europe-west1-data.1.dblayer.com

This emergeny maintenance includes non-portal hosts which, by the design of the Compose platform, should not affect the availability of your database deployments. No action on your part should be required before or during this maintenance. If during the maintenance you experience problems with your deployment, please contact us immediately at support@compose.com and we will work with you to resolve these issues.

These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

Affected deployments:

57a07eaf27c91e001600000c
57b4443e6d273b0016000007
57fcb16971c66d001f000012
58089a71028b01001c00001a
581f5521e07a31001c00003f
58219b0dce03cc0018000042
5823288c5201fc001600005e
582450870ca53a001a00000d
5836e5f4dc2d5b0019000036
5868e42bc38fc7001c00001b
586e2013b96bdc0017000017
587112d977419d001600000e
58da9de437d7d6000efaf576
59195dc6632b310015ea476d
5922af03d704b3000ed6260a
5939233e67ef6800152f3571
5979bc3defaafb00143654db
599ee330f32fb6001000d80f
59a52cda65c417001501a344
59a81793861ea70011000f7c
59c7d93a0f28980015010b75
59d36db7c948ca0026006308
5a15eb9953888300180fdfd3
5a30e85e9ad0e6001858e863
5ab0f625821ffb00110daa20
5aba3444384ccd00189cc246
5ac64fa93d580a024ccb3a6d
5afd6f3c208ba400157e6276
5b06644d3a1e660027e37b28
5b2763c6f98b190021dc9594
5b38b6d214d08c0019064b7a
5b3b3c13a8b1ad00196ae65a
5b47dc0ebd93fc001560e93a
5b556e851c0fc2001d130aa5
5b9231ba422e4d001e7a255a
5ba3f0d42f9a3d000efac9c8
5bab91b98807bd2dda53dc70
5bb1da7e8807bd7e57536a3a
5c07daaff342900017dcbff1
5c6a64aec1b403000b5aa058

If you have any questions about this maintenance, please email us at support@compose.com.
Jun 24, 09:17 UTC
Emergency Maintenance - gcp-europe-west1-data.4.dblayer.com
Resolved - The issue has been resolved and all systems are nominal.
Jun 24, 09:39 UTC
Monitoring - We have resolved the issue and are actively monitoring the situation.
Jun 24, 09:31 UTC
Update - Host is back up. Capsules are being restarted.
Jun 24, 09:26 UTC
Update - We are performing a quick reboot on this host. Deployments have been failed over.
Jun 24, 09:18 UTC
Identified - Beginning immediately Compose will be performing emergency maintenance on:

gcp-europe-west1-data.4.dblayer.com

This emergeny maintenance includes non-portal hosts which, by the design of the Compose platform, should not affect the availability of your database deployments. No action on your part should be required before or during this maintenance. If during the maintenance you experience problems with your deployment, please contact us immediately at support@compose.com and we will work with you to resolve these issues.

These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

Affected deployments:

5cc017a86a7402699393d55f
5d43dd528f2aff0019c58ec9
5d4ab18ec045f02ae8cc0bca
5d6e37cc11b979449e06b13d
5d8c084fa33a4519cecbdce8
5d8c0bd59c33747bb4748e60
5dc53d99312020000d3a87f7
5dcd77da9ba01f00161b9cf2
5e15eb4357dca462a104e322
5e38e37af29ae8000e665354
5e484aaf3dd82b52b1b14d73
5e53121e1c22210bfa70133e
5e5906f3f29ae8000e8f95ec
5e6213430743cd4d94602a34
5e7e0a72432c460011e468d8
5e7e3a6efc2f9048f33c30a3
5e9ebfcf4c9f40214071cb19
5eb1580eb666910014692101
5ed78d812b462d0011dc3045
5edf556b4fbd582a1b51e596
5ee0c60ca7d6e569fc7b2a45

If you have any questions about this maintenance, please email us at support@compose.com.
Jun 24, 09:17 UTC
Emergency Maintenance - gcp-us-east1-data.4.dblayer.com
Resolved - The issue has been resolved and all systems are nominal.
Jun 24, 09:39 UTC
Monitoring - We have resolved the issue and are actively monitoring the situation.
Jun 24, 09:31 UTC
Update - Host is back up. Capsules are being restarted.
Jun 24, 09:26 UTC
Update - We are performing a quick reboot on this host. Deployments have been failed over.
Jun 24, 09:18 UTC
Identified - Beginning immediately Compose will be performing emergency maintenance on:

gcp-us-east1-data.4.dblayer.com

This emergeny maintenance includes non-portal hosts which, by the design of the Compose platform, should not affect the availability of your database deployments. No action on your part should be required before or during this maintenance. If during the maintenance you experience problems with your deployment, please contact us immediately at support@compose.com and we will work with you to resolve these issues.

These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

Affected deployments:

58cad0b69407120011b450d7
58ec23860d96980016823f24
58f56116460ef0001512cec7
58f7fa07753b2c00167a3882
5916480672891e000f262cde
592a302b0460bfb18b77ba5e
593d636d77d12b0012ad49d6
598875c733fbeb031800427b
59b30124874a1c00140191fa
59b99fbff163f200140000a7
59b99fd0f163f200140000c3
59ba6a2c58f3db0026003d84
59bf94da76c94f001400153f
59d44745b89b34001400544b
5ba012f5ef7b2900111f73a3
5c658b080ae82f736164b176
5e01ccce44b97000196aa50e
5e444aae1c22214ade6f355b
5e444fee0743cd3da129092a
5e64a1bd0743cd74f25fbcac

If you have any questions about this maintenance, please email us at support@compose.com.
Jun 24, 09:17 UTC
Emergency Maintenance - gcp-us-east1-data.7.dblayer.com
Resolved - The issue has been resolved and all systems are nominal.
Jun 24, 09:39 UTC
Monitoring - We have resolved the issue and are actively monitoring the situation.
Jun 24, 09:31 UTC
Update - Host is back up. Capsules are being restarted.
Jun 24, 09:26 UTC
Update - We are performing a quick reboot on this host. Deployments have been failed over.
Jun 24, 09:18 UTC
Identified - Beginning immediately Compose will be performing emergency maintenance on:

gcp-us-east1-data.7.dblayer.com

This emergeny maintenance includes non-portal hosts which, by the design of the Compose platform, should not affect the availability of your database deployments. No action on your part should be required before or during this maintenance. If during the maintenance you experience problems with your deployment, please contact us immediately at support@compose.com and we will work with you to resolve these issues.

These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

Affected deployments:

5a0464f9c53eff00230218ee
5a18b266123a2100101e52e1
5a26bfb2e7217e00183efa1e
5a2fde7c12608300107c50d8
5aa0bd4d58b8c80014c19838
5ac4f4ad542c300a607e4dbd
5ade27607ddf5667dd2453b5
5ade27ed1f50d00015b75903
5aefc32c7852906e0ed9db99
5af364442fe7880011e8c15f
5af3b3082fe7880011e8eb0c
5b0279d2c664a1001559ed12
5b14792528f5501ea1068e68
5c19635df27619638b65893a
5c211939d23f94000b09e7e7
5c463091b011eb000f9a21ea
5cd1dd96bef8c1001b95e338
5cd1ddc5152fa3000e482c07
5cdad659ea914a00112ca457
5d3b67adcd507e00101f32d7
5d4b8fd6c045f07d97cc84ec
5d9ce3ff9c337406e47347c6
5daf755a16baa94d6253bd28
5e3a4436f29ae8001a8aa86d
5ea8a7bfdaa9dc00177544ab
5ee154eaf7c22d7c5e391d90
5ee7a7efbc02bd2520ef8d43
5ee8f9f92b462d612fdcc1c4

If you have any questions about this maintenance, please email us at support@compose.com.
Jun 24, 09:17 UTC
Emergency Maintenance - gcp-europe-west1-data.0.dblayer.com
Resolved - The issue has been resolved and all systems are nominal.
Jun 24, 08:51 UTC
Monitoring - We have resolved the issue and are actively monitoring the situation.
Jun 24, 08:47 UTC
Update - Host is back up and capsules are being restarted.
Jun 24, 08:43 UTC
Update - We going to perform a quick reboot on this host. Deployments have been gracefully failed over.
Jun 24, 08:30 UTC
Identified - Beginning immediately Compose will be performing emergency maintenance on:

gcp-europe-west1-data.0.dblayer.com

This emergeny maintenance includes non-portal hosts which, by the design of the Compose platform, should not affect the availability of your database deployments. No action on your part should be required before or during this maintenance. If during the maintenance you experience problems with your deployment, please contact us immediately at support@compose.com and we will work with you to resolve these issues.

These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

Affected deployments:

5771482ae38bed001d00000d
57861f760b78740019000007
57a07eaf27c91e001600000c
57bd5402e2ff190016000003
57d93705401591001c000008
57e24b9c2b85d8001f000014
57fcb16971c66d001f000012
58089a71028b01001c00001a
581f5521e07a31001c00003f
58219b0dce03cc0018000042
5823288c5201fc001600005e
582450870ca53a001a00000d
5836e5f4dc2d5b0019000036
5868e42bc38fc7001c00001b
586e2013b96bdc0017000017
587112d977419d001600000e
58da9de437d7d6000efaf576
59195dc6632b310015ea476d
5922af03d704b3000ed6260a
5939233e67ef6800152f3571
5979bc3defaafb00143654db
599ee330f32fb6001000d80f
59a52cda65c417001501a344
59a81793861ea70011000f7c
59c7d93a0f28980015010b75
59d36db7c948ca0026006308
5a15eb9953888300180fdfd3
5a296ce2eb06d800246536bc
5a30e85e9ad0e6001858e863
5ab0f625821ffb00110daa20
5afd6f3c208ba400157e6276
5b06644d3a1e660027e37b28
5b47dc0ebd93fc001560e93a
5b9231ba422e4d001e7a255a
5ba3f0d42f9a3d000efac9c8
5bab91b98807bd2dda53dc70
5bb1da7e8807bd7e57536a3a
5c07daaff342900017dcbff1
5c6a64aec1b403000b5aa058
5e7e0a72432c460011e468d8
5e7e3a6efc2f9048f33c30a3
5e9ebfcf4c9f40214071cb19
5eb1580eb666910014692101
5eb260572272b30011abfe2a
5eb26077b666912400688429

If you have any questions about this maintenance, please email us at support@compose.com.
Jun 24, 08:29 UTC
Emergency Maintenance - gcp-europe-west1-data.3.dblayer.com
Resolved - The issue has been resolved and all systems are nominal.
Jun 24, 08:51 UTC
Monitoring - We have resolved the issue and are actively monitoring the situation.
Jun 24, 08:47 UTC
Update - Host is back up and capsules are being restarted.
Jun 24, 08:43 UTC
Update - We going to perform a quick reboot on this host. Deployments have been gracefully failed over.
Jun 24, 08:30 UTC
Identified - Beginning immediately Compose will be performing emergency maintenance on:

gcp-europe-west1-data.3.dblayer.com

This emergeny maintenance includes non-portal hosts which, by the design of the Compose platform, should not affect the availability of your database deployments. No action on your part should be required before or during this maintenance. If during the maintenance you experience problems with your deployment, please contact us immediately at support@compose.com and we will work with you to resolve these issues.

These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

Affected deployments:

5cc017a86a7402699393d55f
5d566f9b8453960013b7661a
5d6902b5807d34000de3e44b
5d6e37cc11b979449e06b13d
5d8c084fa33a4519cecbdce8
5d8c0bd59c33747bb4748e60
5dc53d99312020000d3a87f7
5dcd77da9ba01f00161b9cf2
5e15eb4357dca462a104e322
5e38e37af29ae8000e665354
5e484aaf3dd82b52b1b14d73
5e53121e1c22210bfa70133e
5e5906f3f29ae8000e8f95ec
5e6213430743cd4d94602a34
5ed78d812b462d0011dc3045
5edf556b4fbd582a1b51e596
5ee0c60ca7d6e569fc7b2a45
5ee78b1fbc02bd49ecf17155

If you have any questions about this maintenance, please email us at support@compose.com.
Jun 24, 08:29 UTC
Emergency Maintenance - gcp-us-east1-data.3.dblayer.com
Resolved - The issue has been resolved and all systems are nominal.
Jun 24, 08:51 UTC
Monitoring - We have resolved the issue and are actively monitoring the situation.
Jun 24, 08:47 UTC
Update - Host is back up and capsules are being restarted.
Jun 24, 08:43 UTC
Update - We going to perform a quick reboot on this host. Deployments have been gracefully failed over.
Jun 24, 08:30 UTC
Identified - Beginning immediately Compose will be performing emergency maintenance on:

gcp-us-east1-data.3.dblayer.com

This emergeny maintenance includes non-portal hosts which, by the design of the Compose platform, should not affect the availability of your database deployments. No action on your part should be required before or during this maintenance. If during the maintenance you experience problems with your deployment, please contact us immediately at support@compose.com and we will work with you to resolve these issues.

These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

Affected deployments:

58ec23860d96980016823f24
58f56116460ef0001512cec7
58f7fa07753b2c00167a3882
5916480672891e000f262cde
598875c733fbeb031800427b
59b2f9261e021a00190154bd
59b30124874a1c00140191fa
59b6c7af0deffb001800014e
5d3b67adcd507e00101f32d7
5e3a4436f29ae8001a8aa86d
5e444aae1c22214ade6f355b
5e444fee0743cd3da129092a
5e64a1bd0743cd74f25fbcac
5e872b4cfc2f9020f03bc0a7

If you have any questions about this maintenance, please email us at support@compose.com.
Jun 24, 08:30 UTC
Emergency Maintenance - gcp-us-east1-data.6.dblayer.com
Resolved - The issue has been resolved and all systems are nominal.
Jun 24, 08:51 UTC
Monitoring - We have resolved the issue and are actively monitoring the situation.
Jun 24, 08:47 UTC
Update - Host is back up and capsules are being restarted.
Jun 24, 08:44 UTC
Update - We going to perform a quick reboot on this host. Deployments have been gracefully failed over.
Jun 24, 08:30 UTC
Identified - Beginning immediately Compose will be performing emergency maintenance on:

gcp-us-east1-data.6.dblayer.com

This emergeny maintenance includes non-portal hosts which, by the design of the Compose platform, should not affect the availability of your database deployments. No action on your part should be required before or during this maintenance. If during the maintenance you experience problems with your deployment, please contact us immediately at support@compose.com and we will work with you to resolve these issues.

These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

Affected deployments:

5a0464f9c53eff00230218ee
5a18b266123a2100101e52e1
5a26bfb2e7217e00183efa1e
5a2fde7c12608300107c50d8
5a66aac6bce8bd00193b3231
5a6ca24eed40e20010c43c23
5a6ca28972babf0014ce21ba
5aa0bd4d58b8c80014c19838
5ac4f4ad542c300a607e4dbd
5ad8e64ac826350010310938
5ade27607ddf5667dd2453b5
5ade27ed1f50d00015b75903
5aeb06a17852907030d8b18a
5aefc32c7852906e0ed9db99
5b14792528f5501ea1068e68
5b45da0ba8d92a00118a7bfa
5b4861c6f9c8d50019c34c60
5ba012f5ef7b2900111f73a3
5ba013754ce0d90d9ad15b6e
5c19635df27619638b65893a
5c211939d23f94000b09e7e7
5c463091b011eb000f9a21ea
5c4631bb906fc70011d7f2b7
5c658b080ae82f736164b176
5cd1dd96bef8c1001b95e338
5e01ccce44b97000196aa50e
5ea8a7bfdaa9dc00177544ab
5ee154eaf7c22d7c5e391d90
5ee8f9f92b462d612fdcc1c4

If you have any questions about this maintenance, please email us at support@compose.com.
Jun 24, 08:29 UTC
Jun 23, 2020
Migration service partial outage
Resolved - This incident has been resolved.
Jun 23, 20:08 UTC
Investigating - We are currently investigating this issue.
Jun 23, 15:22 UTC
Emergency Maintenance - gcp-us-east1-memory.8.dblayer.com
Resolved - The issue has been resolved and all systems are nominal.
Jun 23, 16:16 UTC
Monitoring - Beginning immediately Compose will be performing emergency maintenance on:

gcp-us-east1-memory.8.dblayer.com

This emergeny maintenance includes non-portal hosts which, by the design of the Compose platform, should not affect the availability of your database deployments. No action on your part should be required before or during this maintenance. If during the maintenance you experience problems with your deployment, please contact us immediately at support@compose.com and we will work with you to resolve these issues.

These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

Affected deployments:

5a32b5e051e4fe001803a728
5a45116827b04a001408c048
5a455cb027b04a001408c6ec
5a58e2c6c607ae0011ba4ac1
5a5ab6450bb58f0016e495f9
5a6ca0dfac6d770010ebdd36
5b271225594c6933b1753b75
5b272da3594c6933ae755389
5b58b23ea1ee500015b1ad03
5ba013c24ce0d90d9ad15b91
5c4a30920bd4cc0011bc42f7
5c524e53dba5b900111e9d13
5c5752318f946100117ce13a
5c587d7adba5b9000e1faec4
5d8250ae9c337442c0735c7a
5d82511102e5aa00152af4c3
5e3a43e80cf2ce001132a93d
5e3a454e0743cd000e7e3c6c
5e444936f29ae8476d8aac18
5e4449e920cdcf289b00dc44
5e444c99f29ae841a98ad137
5e444ea120cdcf5266fff45a
5e8760d91a02d145ae9c2e62
5e87a41bfc2f9000143f1be2
5ea09281dea248001700a2a4
5ea8a3912272b30011aa6493
5ea8abc5daa9dc00147544cc
5ee019b12b462d612fdb66d6
5ee9c014f7c22d473b3b785f

If you have any questions about this maintenance, please email us at support@compose.com.
Jun 23, 16:04 UTC
Emergency Maintenance - gcp-europe-west1-memory.0.dblayer.com
Resolved - The issue has been resolved and all systems are nominal.
Jun 23, 15:51 UTC
Monitoring - Beginning immediately Compose will be performing emergency maintenance on:

gcp-europe-west1-memory.0.dblayer.com

This emergeny maintenance includes non-portal hosts which, by the design of the Compose platform, should not affect the availability of your database deployments. No action on your part should be required before or during this maintenance. If during the maintenance you experience problems with your deployment, please contact us immediately at support@compose.com and we will work with you to resolve these issues.

These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

Affected deployments:

57b5bedfc67f5c0019000004
57bdebf5df06bf0016000000
5970bf39e0da4900157400bb
5970c0af7c61c9000e7b148b
59bff7b4d55aa30014000a19
59bffb2c1781ed00140009f3
59edd9a02f942800196227e8
5a26954d2b98130018056652
5a4b87c6c28d0a001897a0c1
5a4bdea99f505f00100c2ff0
5a7813a4ed40e20014c79eae
5a786c24c92efc001176cdd3
5e3d38ae20cdcf22caffe873
5e46d9db20cdcf4632009f6d
5e46db403dd82b632db0bcc2
5e9ec0ae52332e00118f356f
5ee241943b34af6e4c1297f1

If you have any questions about this maintenance, please email us at support@compose.com.
Jun 23, 15:11 UTC
Emergency Maintenance - gcp-us-east1-data.0.dblayer.com
Resolved - The issue has been resolved and all systems are nominal.
Jun 23, 14:59 UTC
Monitoring - Beginning immediately Compose will be performing emergency maintenance on:

gcp-us-east1-data.0.dblayer.com

This emergeny maintenance includes non-portal hosts which, by the design of the Compose platform, should not affect the availability of your database deployments. No action on your part should be required before or during this maintenance. If during the maintenance you experience problems with your deployment, please contact us immediately at support@compose.com and we will work with you to resolve these issues.

These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

Affected deployments:

576c31ab343ff50019000007
5772dd2edf0df80016000003
57d9876826747c001c000000
57d98869168a800016000003
5807ca76028b010019000008
5807e80c16559a001900001a
5820ab495201fc0016000021
5822275fce03cc001e000063
584e047dd9a794001a00000d
5871360988f7700019000013
5876572518cd6f0018000064
587a7ecfee893b0019000001
58816b47905a3e001a000007
5893216fba6d4d0016000002
58b71bf45f9780001d000003
58b7286e5f9780001600000a
58bed9edbe0cfc0017000010
58bf0973ea05940019000003
58c345f483a377001c00001c
58c34643bfe7fc001600001a
59b99fbff163f200140000a7
59b99fd0f163f200140000c3
59ba6a2c58f3db0026003d84
59bf94da76c94f001400153f
59d44745b89b34001400544b
5af364442fe7880011e8c15f
5af3b3082fe7880011e8eb0c
5b0279d2c664a1001559ed12
5b16ee5d1ef7ce00116bab94
5b644c3cf509f5001182ca5e

If you have any questions about this maintenance, please email us at support@compose.com.
Jun 23, 14:16 UTC
Jun 22, 2020
Emergency Maintenance - gcp-us-east1-memory.1.dblayer.com
Resolved - The issue has been resolved and all systems are nominal.
Jun 22, 15:38 UTC
Monitoring - We have resolved the issue and are actively monitoring the situation.
Jun 22, 15:38 UTC
Identified - Beginning immediately Compose will be performing emergency maintenance on:

gcp-us-east1-memory.1.dblayer.com

This emergeny maintenance includes non-portal hosts which, by the design of the Compose platform, should not affect the availability of your database deployments. No action on your part should be required before or during this maintenance. If during the maintenance you experience problems with your deployment, please contact us immediately at support@compose.com and we will work with you to resolve these issues.

These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.

Affected deployments:

57e93125bf49b4be17000004
57e98d095d7d780019000003
5876e24f77419d001600006a
5877d8d218cd6f001800007b
589cdc9d8903980018000006
58bed9b9fc8027001600000d
59429b1aaac64b0011f575d5
5b1478ead297985d60508a4c
5b147964d297985d60508a6a
5ba013c24ce0d90d9ad15b91
5d0741bce9f8b5000b36f8b2
5d92f1d7247cdf10a7bb4677
5d93e03e7654d174ab478ae6
5d93e6d4247cdf20d3bb4d18
5ddc20528043b52325f30613
5de8d0fbbacdc04b8345fb07
5e01ccce44b97000196aa50e
5e3a43e80cf2ce001132a93d
5e3a454e0743cd000e7e3c6c
5e444936f29ae8476d8aac18
5e4449e920cdcf289b00dc44
5e444c99f29ae841a98ad137
5e444ea120cdcf5266fff45a

If you have any questions about this maintenance, please email us at support@compose.com.
Jun 22, 13:37 UTC
Jun 21, 2020

No incidents reported.

Jun 20, 2020

No incidents reported.

Jun 19, 2020

No incidents reported.

Jun 18, 2020

No incidents reported.

← Incident History Powered by Statuspage