Outage in Compose

Emergency Maintenance - aws-us-east-1-data.66.dblayer.com

Resolved Major
November 03, 2022 - Started over 1 year ago - Lasted 25 minutes
Official incident page

Need to monitor Compose outages?
Stay on top of outages with IsDown. Monitor the official status pages of all your vendors, SaaS, and tools, including Compose, and never miss an outage again.
Start Free Trial

Outage Details

Beginning immediately Compose will be performing emergency maintenance on: aws-us-east-1-data.66.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: 5b0cd7233a1e660023e48d91 5b1061366626cb0019c5972c 5b11d49328f550001906c80a 5b1694ed6626cb0011c68e53 5b16d1331ef7ce00196baa50 5b16e070d297988f4c5016ac 5b1a93c1c6cc47001e628910 5b1acec2ddb12300158f1b2d 5b294147bd3159001263aa01 5b58b81ca1ee500011b1b098 5b58c3cb36cc1a00128fdcd3 5ba18a4b700794000e939c40 5e29c61e35f16d0016818a7d 5e2f2f7c4dc0bf430d02f9dc 5e3893a1f29ae8000e6639a6 5e3a7db70743cd001a7e59b9 5e3c74430cf2ce000e330ba1 5e3d7ec31c22211d106f2234 5e3dce9a3dd82b222fb0b8bc 5e4114ed1c22213a556f0aee 5e42a2bc20cdcf4632fffe59 5e4d52e01c22210bfa6f45f5 5e54fb613dd82b419fb0ecc3 5e7bb30e432c4662a2e1bb04 5e7cdf59432c462bcee30b49 5e7cf4921a02d158af9cef3b 5e90dc212e1ab91c5b24ad8e 5e946291432c467e43e22346 5e967a2f95267053057c3547 5ea89014d53a410014253ddd 5ebd6c6812948a00172663ae 5edd361ea7d6e533ce7bcfd5 5ededeb42b462d612fdb3936 5edf83e5a7d6e533ce7c20fd 5ee2b04a2b462d7190db718c 5eeb73ef8fc3eb00143c7e02 5eebf29f8fc3eb00113c975f 5ef0b60e99afc900172ceaff 5ef229d9b517c70011672a2b 5ef2edac53aa030011aa1456 5ef6d61280b721001838e004 615cb5b87d1696000d02acf9 615dd3c02b5347000df44292 61604852feb377000b46039b 61b367d00dbc22000db6809a 61b9269c822a9e000a44a423 61ba246cb1bf94000e31cf19 61bcdb1d556164000aad2b04 61d079d2822a9e000b45f21e 626be85215c2eb000adc6dfb 627d1e4cb6fb6d000a8002dd 6283bb28407590000faebafd 6297a5feaac4b8000ecb4832 62a9fc8a4adb57000d6ba2a9 5be3095db771350011418b9c 5c5dfdd4c1b403000e584f85 5c61a0190ae82f000b65db14 5bbdadee248a18000b062e22 5bcd3bd32142160018fb36d3 5c079d82f27619638b623b9e 5c734acff95331001cdd9315 5d6f88e542852f001951ad3a 5efb6037f8263d001834c171 5efc3f851e43b1000e2139e2 6132260ff084f3000ccd6301 6137d7d8151f49000997d8a1 5ef165b3b20ad2001add45c4 5ef3ebd78f0db9001767bba5 5ef90fd6f8263d0012347e09 59225482eab3f2000edf4fcf 5ed90862f7c22d00143a67b3 5eea061e2b462d206ddb90c0 617e604f7d04e3000b1aaeaa 61e5f05f21e01d000c0efca0 61e8775bdd7005000d5fc930 5ee3b17b4fbd58001a53968e 5ee53ba0f7c22d028c399ed6 5ee5a7382b462d7190dbd657 5ee60a78bc02bd4ca1f10700 5ee61073bc02bd49ecf1310a 5ee7b4f6bc02bd4ca1f1505d 5ee7cf64f7c22d591d3ad49b 5ee90effbc02bd2520efc3f1 5ee9770ca7d6e57f877c121a 5ef2679c53aa030011aa0737 5ef703441e43b10017207294 5eebb524e0b06c00144b8b31 5efcabcc1e43b10017214632 5b69223f9fb185001f42ad73 61e87a17a86347000e1d54a9 6283af00e65c88000eb4b50b 5ee2ae02bc02bd088bef665b If you have any questions about this maintenance, please email us at support@compose.com.
Latest Updates ( sorted recent to last )
IDENTIFIED over 1 year ago - at 11/03/2022 02:40PM

Beginning immediately Compose will be performing emergency maintenance on:

aws-us-east-1-data.66.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:

5b0cd7233a1e660023e48d91
5b1061366626cb0019c5972c
5b11d49328f550001906c80a
5b1694ed6626cb0011c68e53
5b16d1331ef7ce00196baa50
5b16e070d297988f4c5016ac
5b1a93c1c6cc47001e628910
5b1acec2ddb12300158f1b2d
5b294147bd3159001263aa01
5b58b81ca1ee500011b1b098
5b58c3cb36cc1a00128fdcd3
5ba18a4b700794000e939c40
5e29c61e35f16d0016818a7d
5e2f2f7c4dc0bf430d02f9dc
5e3893a1f29ae8000e6639a6
5e3a7db70743cd001a7e59b9
5e3c74430cf2ce000e330ba1
5e3d7ec31c22211d106f2234
5e3dce9a3dd82b222fb0b8bc
5e4114ed1c22213a556f0aee
5e42a2bc20cdcf4632fffe59
5e4d52e01c22210bfa6f45f5
5e54fb613dd82b419fb0ecc3
5e7bb30e432c4662a2e1bb04
5e7cdf59432c462bcee30b49
5e7cf4921a02d158af9cef3b
5e90dc212e1ab91c5b24ad8e
5e946291432c467e43e22346
5e967a2f95267053057c3547
5ea89014d53a410014253ddd
5ebd6c6812948a00172663ae
5edd361ea7d6e533ce7bcfd5
5ededeb42b462d612fdb3936
5edf83e5a7d6e533ce7c20fd
5ee2b04a2b462d7190db718c
5eeb73ef8fc3eb00143c7e02
5eebf29f8fc3eb00113c975f
5ef0b60e99afc900172ceaff
5ef229d9b517c70011672a2b
5ef2edac53aa030011aa1456
5ef6d61280b721001838e004
615cb5b87d1696000d02acf9
615dd3c02b5347000df44292
61604852feb377000b46039b
61b367d00dbc22000db6809a
61b9269c822a9e000a44a423
61ba246cb1bf94000e31cf19
61bcdb1d556164000aad2b04
61d079d2822a9e000b45f21e
626be85215c2eb000adc6dfb
627d1e4cb6fb6d000a8002dd
6283bb28407590000faebafd
6297a5feaac4b8000ecb4832
62a9fc8a4adb57000d6ba2a9
5be3095db771350011418b9c
5c5dfdd4c1b403000e584f85
5c61a0190ae82f000b65db14
5bbdadee248a18000b062e22
5bcd3bd32142160018fb36d3
5c079d82f27619638b623b9e
5c734acff95331001cdd9315
5d6f88e542852f001951ad3a
5efb6037f8263d001834c171
5efc3f851e43b1000e2139e2
6132260ff084f3000ccd6301
6137d7d8151f49000997d8a1
5ef165b3b20ad2001add45c4
5ef3ebd78f0db9001767bba5
5ef90fd6f8263d0012347e09
59225482eab3f2000edf4fcf
5ed90862f7c22d00143a67b3
5eea061e2b462d206ddb90c0
617e604f7d04e3000b1aaeaa
61e5f05f21e01d000c0efca0
61e8775bdd7005000d5fc930
5ee3b17b4fbd58001a53968e
5ee53ba0f7c22d028c399ed6
5ee5a7382b462d7190dbd657
5ee60a78bc02bd4ca1f10700
5ee61073bc02bd49ecf1310a
5ee7b4f6bc02bd4ca1f1505d
5ee7cf64f7c22d591d3ad49b
5ee90effbc02bd2520efc3f1
5ee9770ca7d6e57f877c121a
5ef2679c53aa030011aa0737
5ef703441e43b10017207294
5eebb524e0b06c00144b8b31
5efcabcc1e43b10017214632
5b69223f9fb185001f42ad73
61e87a17a86347000e1d54a9
6283af00e65c88000eb4b50b
5ee2ae02bc02bd088bef665b

If you have any questions about this maintenance, please email us at support@compose.com.

Easily monitor Compose and all your third-party status pages

With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.

Start free trial

No credit card required · Cancel anytime · 3170 services available

Integrations with Slack Microsoft Teams Google Chat Datadog PagerDuty Zapier Discord Webhook

Setup in 5 minutes or less

How much time you'll save your team, by having the outages information close to them?

14-day free trial · No credit card required · Cancel anytime