Historia awarii Cloud 66

1. 24 sierpnia 2026 19:08 UTCidentified

   Seria IPv6 DigitalOcean wydaje się blokować dostęp do Google Cloud Storage. Oznacza to, że klienci CSv1 i CSv2, którzy posiadają serwery o publicznych adresach IPv6, nie są obecnie w stanie wyciągnąć nowych obrazów BuildGrid na swoje serwery.

2. 24 sierpnia 2026 19:24 UTCidentified

   GCS potwierdziło, że wewnętrzny problem powoduje zablokowanie zakresu DigitalOcean IPv6 i obecnie pracuje nad rozwiązaniem.

3. 25 sierpnia 2026 16:06 UTCidentified

   Nadal czekamy na GCS, aby rozwiązać tę kwestię.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 24 sierpnia 2026 16:24 UTCidentified

   Seria IPv6 DigitalOcean wydaje się blokować dostęp do Google Cloud Storage. Oznacza to, że klienci CSv1 i CSv2, którzy posiadają serwery o publicznych adresach IPv6, nie są obecnie w stanie wyciągnąć nowych obrazów BuildGrid na swoje serwery.

2. 24 sierpnia 2026 19:06 UTCidentified

   Kontynuujemy prace nad rozwiązaniem tego problemu.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 12 czerwca 2025 19:09 UTCinvestigating

   Google authentication issues is having issues causing login and access issues for our systems and customers. We are investigating the impact and mitigation strategies.

2. 12 czerwca 2025 20:30 UTCresolved

   The underlying issue with GCP seems to be resolved, and we are not seeing further issues with the logins and other systems.

1. 2 stycznia 2025 12:24 UTCinvestigating

   We are aware of problems when scaling/creating Kubernetes clusters. This appears to be caused by new rate limits imposed by docker hub. The team are working on a solution.

2. 2 stycznia 2025 12:25 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 2 stycznia 2025 12:25 UTCinvestigating

   We are currently investigating this issue.

4. 2 stycznia 2025 15:45 UTCresolved

   This incident has been resolved.

1. 28 czerwca 2024 01:35 UTCinvestigating

   We are currently investigating a number of stuck deployments.

2. 28 czerwca 2024 01:50 UTCmonitoring

   We have identified the issue causing the deployments to be stuck and fixed the issue. This was caused by a database failure at our cloud provider which we are investigating and monitoring.

3. 28 czerwca 2024 13:46 UTCresolved

   This incident has now been resolved.

1. 13 maja 2024 08:27 UTCinvestigating

   We are aware of issues with our CustomConfig git repositories. This issue impacts direct git access to the CustomConfig git repository. Direct access to CustomConfig pages via the web dashboard and API is not affected. We are investigating the root cause of the problem.

2. 14 maja 2024 11:48 UTCinvestigating

   Applications are able to be deployed, but the CustomConfig backend is not available for the moment.

3. 20 maja 2024 15:07 UTCresolved

   The CustomConfig git backend migration has been completed

1. 19 marca 2024 10:07 UTCinvestigating

   We are investigating issues affecting some production systems.

2. 19 marca 2024 10:09 UTCinvestigating

   We are continuing to investigate this issue.

3. 19 marca 2024 10:13 UTCresolved

   This incident has been resolved.

1. 9 maja 2023 11:45 UTCmonitoring

   Github is experiencing some API outages, deployments don't currently appear to be affected. We are monitoring (https://www.githubstatus.com/)

2. 9 maja 2023 15:21 UTCresolved

   This incident has been resolved.

1. 26 kwietnia 2023 15:36 UTCinvestigating

   Water intrusion in a data center in europe-west9 has caused a multi-cluster failure and has led to a shutdown of multiple zones. We expect general unavailability of the europe-west9 region. There is no current ETA for recovery of operations in the europe-west9 region at this time, but it is expected to be an extended outage. Customers are advised to failover to other regions if they are impacted.

2. 26 kwietnia 2023 16:03 UTCinvestigating

   Due to a major outage in Google Cloud (https://status.cloud.google.com/regional/europe) - Kubernetes installations may fail on installations on servers located in the same region, regardless of the cloud, due to Kubernetes images themselves being hosted on Google Cloud

3. 26 kwietnia 2023 16:37 UTCmonitoring

   We are waiting on Google resolutions

4. 27 kwietnia 2023 08:22 UTCresolved

   Maestro installations are working as expected again

1. 6 października 2022 13:07 UTCinvestigating

   Currently, GitHub is having an issue with listing repositories while using the Cloud 66 Github app. As a workaround while this issue is ongoing. 1. Remove the Github installation. 2. Manually configure SSH key access to Github, please see the link below. https://help.cloud66.com/rails/how-to-guides/common-tools/access-your-code#manually-configuring-github-access

2. 6 października 2022 14:52 UTCidentified

   The issue has been identified and a fix is being implemented and this should resolve the issue for most users. If the error is still persisting, please use the workaround provided: 1. Remove the Github installation. 2. Manually configure SSH key access to Github, please see the link below. https://help.cloud66.com/rails/how-to-guides/common-tools/access-your-code#manually-configuring-github-access

3. 7 października 2022 22:26 UTCresolved

   Issue confirmed to be fixed by GitHub.

1. 14 września 2022 20:15 UTCidentified

   The team is aware that some Buildgrid pushes are taking longer than normal, and are working on a mitigation strategy

2. 15 września 2022 17:03 UTCidentified

   Our engineering team is continuing to look into mitigations for this issue.

3. 16 września 2022 11:47 UTCmonitoring

   The team has completed the first part of the mitigation strategy for intermittent slow Buildgrid pushes. We are now monitoring ongoing performance.

4. 6 października 2022 14:50 UTCresolved

   This incident has been resolved.

1. 9 września 2022 07:20 UTCidentified

   The issue has been identified and a fix is being implemented.

2. 9 września 2022 08:51 UTCresolved

   This incident has been resolved.

3. 9 września 2022 09:00 UTCpostmortem

   At approximately 07:00 UTC we started to perform a minor system quality-of-life backend update. The update had unintended consequences on an older system component which hadn’t been changed in a while. The component was to do with agent server communications, and it ended up disabled after the update. Although the same component was unaffected during testing in dev/staging and passed UAT, it turned out that there was a necessarily different configuration around rewrites in production that caused the issue. The nature of the update meant that rolling back wasn’t straightforward, so the team resolved to fix the incompatibility in-place, and as such were unable to stop the erroneous “server down” notifications that then went out. The issue was resolved approximate 1 hour later. at 08:00 UTC - after which time servers would have started to appear as “online” again. Subsequent to this outage, the difference in configuration has been added to our operations processes, such that this will not occur again. Our apologies for the inconvenience and concern that this may have created!

1. 6 września 2022 11:53 UTCinvestigating

   GitHub is having an outage at this time. This may adversely affect Deployments.

2. 6 września 2022 11:57 UTCresolved

   This incident has been resolved.

1. 30 sierpnia 2022 09:09 UTCidentified

   From Azure (https://status.azure.com/en-gb/status) Starting at approximately 06:00 UTC on 30 Aug 2022, a number of customers running Ubuntu 18.04 (bionic) VMs recently upgraded to systemd version 237-3ubuntu10.54 reported experiencing DNS errors when trying to access their resources. Reports of this issue are confined to this single Ubuntu version.

2. 30 sierpnia 2022 15:11 UTCidentified

   Azure is recommending that affected customers reboot their servers to obtain an updated DHCP lease to resolve this issue

3. 31 sierpnia 2022 09:15 UTCmonitoring

   We are continuing to monitor this incident

4. 5 września 2022 08:21 UTCresolved

   This incident has been resolved.