All Systems Operational
Web Application
?
Operational
REST API
?
Operational
Softlayer aus-sydney-1 Region
Operational
Softlayer aus-sydney-1 Region Clusters
Operational
Softlayer eu-frankfurt-2 Region
Operational
Softlayer eu-frankfurt-2 Region Clusters
Operational
Softlayer eu-london-2 Region
Operational
Softlayer eu-london-2 Region
Operational
Softlayer us-dallas-09 Region
Operational
Softlayer us-dallas-9 Region Clusters
Operational
sl-us-dal-9-portal.4.dblayer.com
Operational
Softlayer us-south-1 Region
Operational
Softlayer us-south-1 Region Clusters
Operational
AWS ap-southeast-2 Region
Operational
AWS ap-southeast-2 Region Clusters
?
Operational
AWS eu-west-1 Region
Operational
AWS eu-west-1 Region Clusters
?
Operational
AWS us-east-1 Region
Operational
AWS us-east-1 Region Clusters
?
Operational
AWS us-west-2 Region
Operational
AWS us-west-2 Region Clusters
?
Operational
Google Cloud us-east-1 Region
Operational
Google Cloud us-east-1 Region Clusters
Operational
Softlayer us-east-1 Region
Operational
Softlayer us-east-1 Region Clusters
Operational
AWS eu-central-1 Region
Operational
AWS eu-central-1 Region Clusters
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
Scheduled Maintenance - sl-eu-fra-2-portal.2.dblayer.com, sl-eu-lon-2-portal.2.dblayer.com, aws-eu-central-1-portal.2.dblayer.com, and aws-eu-west-1-portal.0.dblayer.com
Apr 25, 00:00-03:00 UTC
Beginning at 2018-04-25 0000 UTC and ending at 2018-04-25 0300 UTC, scheduled maintenance will be performed on sl-eu-fra-2-portal.2.dblayer.com, sl-eu-lon-2-portal.2.dblayer.com, aws-eu-central-1-portal.2.dblayer.com, and aws-eu-west-1-portal.0.dblayer.com. These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.
ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.
In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).
We estimate that the maintenance on each host will take 1 hour.
If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 20:32 UTC
ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.
In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).
We estimate that the maintenance on each host will take 1 hour.
If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 20:32 UTC
Scheduled Maintenance - sl-us-dal-9-portal.1.dblayer.com, sl-us-south-1-portal.0.dblayer.com, sl-us-south-1-portal.11.dblayer.com, sl-us-south-1-portal.14.dblayer.com, and sl-us-south-1-portal.17.dblayer.com
Apr 25, 03:00-06:00 UTC
Beginning at 2018-04-25 0300 UTC and ending at 2018-04-25 0600 UTC, scheduled maintenance will be performed on sl-us-dal-9-portal.1.dblayer.com, sl-us-south-1-portal.0.dblayer.com, sl-us-south-1-portal.11.dblayer.com, sl-us-south-1-portal.14.dblayer.com, and sl-us-south-1-portal.17.dblayer.com. These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.
ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.
In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).
We estimate that the maintenance on each host will take 1 hour.
If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 20:49 UTC
ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.
In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).
We estimate that the maintenance on each host will take 1 hour.
If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 20:49 UTC
Scheduled Maintenance - sl-us-dal-9-portal.2.dblayer.com, sl-us-south-1-portal.18.dblayer.com, sl-us-south-1-portal.21.dblayer.com, sl-us-south-1-portal.5.dblayer.com, and sl-us-south-1-portal.8.dblayer.com
Apr 25, 06:00-09:00 UTC
Beginning at 2018-04-25 0600 UTC and ending at 2018-04-25 0900 UTC, scheduled maintenance will be performed on sl-us-dal-9-portal.2.dblayer.com, sl-us-south-1-portal.18.dblayer.com, sl-us-south-1-portal.21.dblayer.com, sl-us-south-1-portal.5.dblayer.com, and sl-us-south-1-portal.8.dblayer.com. These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.
ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.
In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).
We estimate that the maintenance on each host will take 1 hour.
If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 20:57 UTC
ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.
In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).
We estimate that the maintenance on each host will take 1 hour.
If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 20:57 UTC
Scheduled Maintenance - sl-aus-syd-1-portal.2.dblayer.com and aws-ap-southeast-1-portal.0.dblayer.com
Apr 25, 09:00-12:00 UTC
Beginning at 2018-04-25 0900 UTC and ending at 2018-04-25 1200 UTC, scheduled maintenance will be performed on sl-aus-syd-1-portal.2.dblayer.com and aws-ap-southeast-1-portal.0.dblayer.com. These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.
ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.
In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).
We estimate that the maintenance on each host will take 1 hour.
If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 21:01 UTC
ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.
In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).
We estimate that the maintenance on each host will take 1 hour.
If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 21:01 UTC
Scheduled Maintenance - sl-aus-syd-1-portal.3.dblayer.com and aws-ap-southeast-1-portal.1.dblayer.com
Apr 25, 15:00-18:00 UTC
Beginning at 2018-04-25 1500 UTC and ending at 2018-04-25 1800 UTC, scheduled maintenance will be performed sl-aus-syd-1-portal.3.dblayer.com and aws-ap-southeast-1-portal.1.dblayer.com. These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.
ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.
In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).
We estimate that the maintenance on each host will take 1 hour.
If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 21:10 UTC
ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.
In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).
We estimate that the maintenance on each host will take 1 hour.
If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 21:10 UTC
Scheduled Maintenance - sl-eu-fra-2-portal.3.dblayer.com, sl-eu-lon-2-portal.1.dblayer.com, aws-ap-southeast-1-portal.2.dblayer.com, aws-eu-central-1-portal.2.dblayer.com, and aws-eu-west-1-portal.1.dblayer.com
Apr 25, 21:00 - Apr 26, 00:00 UTC
Beginning at 2018-04-25 2100 UTC and ending at 2018-04-26 0000 UTC, scheduled maintenance will be performed sl-eu-fra-2-portal.3.dblayer.com, sl-eu-lon-2-portal.1.dblayer.com, aws-ap-southeast-1-portal.2.dblayer.com, aws-eu-central-1-portal.2.dblayer.com, and aws-eu-west-1-portal.1.dblayer.com. These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.
ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.
In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).
We estimate that the maintenance on each host will take 1 hour.
If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 21:17 UTC
ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.
In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).
We estimate that the maintenance on each host will take 1 hour.
If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 21:17 UTC
Scheduled Maintenance - sl-eu-lon-2-portal.3.dblayer.com, aws-eu-west-1-portal.2.dblayer.com, sl-eu-fra-2-memory.0.dblayer.com, aws-eu-west-1-portal.7.dblayer.com, and aws-eu-west-1-portal.9.dblayer.com
Apr 26, 00:00-03:00 UTC
Beginning at 2018-04-26 0000 UTC and ending at 2018-04-26 0300 UTC, scheduled maintenance will be performed on sl-eu-lon-2-portal.3.dblayer.com, aws-eu-west-1-portal.2.dblayer.com, sl-eu-fra-2-memory.0.dblayer.com, aws-eu-west-1-portal.7.dblayer.com, and aws-eu-west-1-portal.9.dblayer.com. These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.
ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.
In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).
We estimate that the maintenance on each host will take 1 hour.
If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 21:29 UTC
ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.
In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).
We estimate that the maintenance on each host will take 1 hour.
If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 21:29 UTC
Scheduled Maintenance - sl-us-dal-9-portal.3.dblayer.com, sl-us-south-1-portal.1.dblayer.com, sl-us-south-1-portal.10.dblayer.com, sl-us-south-1-portal.13.dblayer.com, and sl-us-south-1-portal.16.dblayer.com
Apr 26, 03:00-06:00 UTC
Beginning at 2018-04-26 0300 UTC and ending at 2018-04-26 0600 UTC, scheduled maintenance will be performed sl-us-dal-9-portal.3.dblayer.com, sl-us-south-1-portal.1.dblayer.com, sl-us-south-1-portal.10.dblayer.com, sl-us-south-1-portal.13.dblayer.com, and sl-us-south-1-portal.16.dblayer.com. These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.
ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.
In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).
We estimate that the maintenance on each host will take 1 hour.
If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 21:24 UTC
ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.
In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).
We estimate that the maintenance on each host will take 1 hour.
If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 21:24 UTC
Scheduled Maintenance - sl-us-dal-9-portal.4.dblayer.com, sl-us-south-1-portal.4.dblayer.com, sl-us-south-1-portal.7.dblayer.com, aws-us-east-1-portal.24.dblayer.com, and aws-us-east-1-portal.27.dblayer.com
Apr 26, 06:00-09:00 UTC
Beginning at 2018-04-26 0600 UTC and ending at 2018-04-26 0900 UTC, scheduled maintenance will be performed on sl-us-dal-9-portal.4.dblayer.com, sl-us-south-1-portal.4.dblayer.com, sl-us-south-1-portal.7.dblayer.com, aws-us-east-1-portal.24.dblayer.com, and aws-us-east-1-portal.27.dblayer.com. These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.
ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.
In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).
We estimate that the maintenance on each host will take 1 hour.
If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 21:32 UTC
ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.
In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).
We estimate that the maintenance on each host will take 1 hour.
If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 21:32 UTC
Scheduled Maintenance - sl-aus-syd-1-memory.1.dblayer.com and aws-ap-southeast-1-memory.0.dblayer.com
Apr 26, 12:00-15:00 UTC
Beginning at 2018-04-26 1200 UTC and ending at 2018-04-26 1500 UTC, scheduled maintenance will be performed on sl-aus-syd-1-memory.1.dblayer.com and aws-ap-southeast-1-memory.0.dblayer.com. These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.
ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.
In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).
We estimate that the maintenance on each host will take 1 hour.
If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 22:44 UTC
ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.
In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).
We estimate that the maintenance on each host will take 1 hour.
If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 22:44 UTC
Scheduled Maintenance - sl-aus-syd-1-memory.2.dblayer.com and aws-ap-southeast-1-memory.1.dblayer.com
Apr 26, 15:00-18:00 UTC
Beginning at 2018-04-26 1500 UTC and ending at 2018-04-26 1800 UTC, scheduled maintenance will be performed on sl-aus-syd-1-memory.2.dblayer.com and aws-ap-southeast-1-memory.1.dblayer.com. These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.
ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.
In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).
We estimate that the maintenance on each host will take 1 hour.
If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 22:57 UTC
ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.
In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).
We estimate that the maintenance on each host will take 1 hour.
If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 22:57 UTC
Scheduled Maintenance - aws-eu-west-1-portal.3.dblayer.com, sl-eu-lon-2-portal.4.dblayer.com, sl-eu-fra-2-memory.5.dblayer.com, aws-eu-central-1-memory.1.dblayer.com, and aws-eu-west-1-portal.2.dblayer.com
Apr 26, 21:00 - Apr 27, 00:00 UTC
Beginning at 2018-04-26 2100 UTC and ending at 2018-04-27 0000 UTC, scheduled maintenance will be performed on aws-eu-west-1-portal.3.dblayer.com, sl-eu-lon-2-portal.4.dblayer.com, sl-eu-fra-2-memory.5.dblayer.com, aws-eu-central-1-memory.1.dblayer.com, and aws-eu-west-1-portal.2.dblayer.com. These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.
ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.
In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).
We estimate that the maintenance on each host will take 1 hour.
If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 22:59 UTC
ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.
In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).
We estimate that the maintenance on each host will take 1 hour.
If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 22:59 UTC
Scheduled Maintenance - aws-eu-west-1-portal.4.dblayer.com, sl-eu-lon-2-portal.5.dblayer.com, sl-eu-fra-2-memory.1.dblayer.com, aws-eu-central-1-memory.2.dblayer.com, aws-eu-west-1-portal.8.dblayer.com
Apr 27, 00:00-03:00 UTC
Beginning at 2018-04-27 0000 UTC and ending at 2018-04-27 0300 UTC, scheduled maintenance will be performed on aws-eu-west-1-portal.4.dblayer.com, sl-eu-lon-2-portal.5.dblayer.com, sl-eu-fra-2-memory.1.dblayer.com, aws-eu-central-1-memory.2.dblayer.com, aws-eu-west-1-portal.8.dblayer.com. These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.
ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.
In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).
We estimate that the maintenance on each host will take 1 hour.
If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 21:53 UTC
ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.
In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).
We estimate that the maintenance on each host will take 1 hour.
If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 21:53 UTC
Scheduled Maintenance - sl-us-dal-9-portal.5.dblayer.com, aws-us-east-1-portal.31.dblayer.com, aws-us-east-1-portal.4.dblayer.com, aws-us-east-1-portal.6.dblayer.com, aws-us-east-1-portal.11.dblayer.com
Apr 27, 03:00-06:00 UTC
Beginning at 2018-04-27 0300 UTC and ending at 2018-04-27 0600 UTC, scheduled maintenance will be performed on sl-us-dal-9-portal.5.dblayer.com, aws-us-east-1-portal.31.dblayer.com, aws-us-east-1-portal.4.dblayer.com, aws-us-east-1-portal.6.dblayer.com, aws-us-east-1-portal.11.dblayer.com. These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.
ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.
In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).
We estimate that the maintenance on each host will take 1 hour.
If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 21:59 UTC
ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.
In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).
We estimate that the maintenance on each host will take 1 hour.
If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 21:59 UTC
Scheduled Maintenance - sl-us-dal-9-portal.6.dblayer.com, aws-us-east-1-portal.7.dblayer.com, aws-us-east-1-portal.12.dblayer.com, aws-us-east-1-portal.17.dblayer.com, aws-us-east-1-portal.19.dblayer.com
Apr 27, 06:00-09:00 UTC
Beginning at 2018-04-27 0600 UTC and ending at 2018-04-27 0900 UTC, scheduled maintenance will be performed on sl-us-dal-9-portal.6.dblayer.com, aws-us-east-1-portal.7.dblayer.com, aws-us-east-1-portal.12.dblayer.com, aws-us-east-1-portal.17.dblayer.com, aws-us-east-1-portal.19.dblayer.com. These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.
ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.
In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).
We estimate that the maintenance on each host will take 1 hour.
If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 22:05 UTC
ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.
In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).
We estimate that the maintenance on each host will take 1 hour.
If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 22:05 UTC
Scheduled Maintenance - sl-aus-syd-1-memory.3.dblayer.com, aws-ap-southeast-1-memory.2.dblayer.com
Apr 27, 12:00-15:00 UTC
Beginning at 2018-04-27 1200 UTC and ending at 2018-04-27 1500 UTC, scheduled maintenance will be performed on sl-aus-syd-1-memory.3.dblayer.com, aws-ap-southeast-1-memory.2.dblayer.com. These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.
ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.
In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).
We estimate that the maintenance on each host will take 1 hour.
If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 22:08 UTC
ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.
In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).
We estimate that the maintenance on each host will take 1 hour.
If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 22:08 UTC
Scheduled Maintenance - sl-aus-syd-1-data.0.dblayer.com, aws-ap-southeast-1-data.0.dblayer.com
Apr 27, 15:00-18:00 UTC
Beginning at 2018-04-27 1500 UTC and ending at 2018-04-27 1800 UTC, scheduled maintenance will be performed on sl-aus-syd-1-data.0.dblayer.com, aws-ap-southeast-1-data.0.dblayer.com. These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.
ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.
In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).
We estimate that the maintenance on each host will take 1 hour.
If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 22:12 UTC
ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.
In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).
We estimate that the maintenance on each host will take 1 hour.
If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 22:12 UTC
Scheduled Maintenance - sl-eu-lon-2-portal.6.dblayer.com, sl-eu-fra-2-memory.4.dblayer.com, aws-eu-central-data.5.dblayer.com, aws-eu-west-1-portal.10.dblayer.com, aws-eu-west-1-portal.5.dblayer.com
Apr 27, 21:00-23:00 UTC
Beginning at 2018-04-27 2100 UTC and ending at 2018-04-27 2300 UTC, scheduled maintenance will be performed on sl-eu-lon-2-portal.6.dblayer.com, sl-eu-fra-2-memory.4.dblayer.com, aws-eu-central-data.5.dblayer.com, aws-eu-west-1-portal.10.dblayer.com, aws-eu-west-1-portal.5.dblayer.com. These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.
ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.
In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).
We estimate that the maintenance on each host will take 1 hour.
If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 22:18 UTC
ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.
In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).
We estimate that the maintenance on each host will take 1 hour.
If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 22:18 UTC
Beginning at 2018-04-28 0000 UTC and ending at 2018-04-28 0300 UTC, scheduled maintenance will be performed on sl-us-dal-9-portal.7.dblayer.com, aws-us-east-1-portal.21.dblayer.com, aws-us-west-2-portal.0.dblayer.com, aws-us-east-1-portal.0.dblayer.com, aws-us-east-1-portal.2.dblayer.com, sl-eu-lon-portal.7.dblayer.com. These hosts and all capsules on them will be temporarily unavailable while the maintenance is being completed.
ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.
In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).
We estimate that the maintenance on each host will take 1 hour.
If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 22:32 UTC
ACTION REQUIRED: In order to not experience a disruption, ensure your application is configured to use all connection strings for your deployment. Your connection strings are shown on the deployment's user interface. If your application is configured to connect to all connection strings, deployments will remain operational.
In order to assess impact on a given instance, you can review the connection strings assigned to your deployment. For connection strings that end in composedb.com, use the nslookup utility to see what host the connection string is being serviced by (Example: nslookup ).
We estimate that the maintenance on each host will take 1 hour.
If you have questions about this maintenance, please contact support@compose.io.
Posted on Apr 20, 22:32 UTC