Cloud 66 の障害履歴

1. 2026年8月24日 19:08 UTCidentified

   DigitalOceanのIPv6範囲は、Googleクラウドストレージへのアクセスからブロックされます。 これは、パブリックIPv6アドレスを持つサーバーを持っているCSv1とCSv2の顧客は現在、サーバーに新しいBuildGridイメージをプルすることはできません.

2. 2026年8月24日 19:24 UTCidentified

   GCSは、内部の問題がデジタルオーシャンIPv6の範囲をブロックし、現在解像度で動作していることを確認しました.

3. 2026年8月25日 16:06 UTCidentified

   GCSでは、問題の解決をお待ちしています.

公式のインシデント更新を自動翻訳しています。

1. 2026年8月24日 16:24 UTCidentified

   DigitalOceanのIPv6範囲は、Googleクラウドストレージへのアクセスからブロックされます。 これは、パブリックIPv6アドレスを持つサーバーを持っているCSv1とCSv2の顧客は現在、サーバーに新しいBuildGridイメージをプルすることはできません.

2. 2026年8月24日 19:06 UTCidentified

   この問題の修正には引き続き取り組んでいます。

公式のインシデント更新を自動翻訳しています。

1. 2025年6月12日 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. 2025年6月12日 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. 2025年1月2日 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. 2025年1月2日 12:25 UTCidentified

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

3. 2025年1月2日 12:25 UTCinvestigating

   We are currently investigating this issue.

4. 2025年1月2日 15:45 UTCresolved

   This incident has been resolved.

1. 2024年6月28日 1:35 UTCinvestigating

   We are currently investigating a number of stuck deployments.

2. 2024年6月28日 1: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. 2024年6月28日 13:46 UTCresolved

   This incident has now been resolved.

1. 2024年5月13日 8: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. 2024年5月14日 11:48 UTCinvestigating

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

3. 2024年5月20日 15:07 UTCresolved

   The CustomConfig git backend migration has been completed

1. 2024年3月19日 10:07 UTCinvestigating

   We are investigating issues affecting some production systems.

2. 2024年3月19日 10:09 UTCinvestigating

   We are continuing to investigate this issue.

3. 2024年3月19日 10:13 UTCresolved

   This incident has been resolved.

1. 2023年5月9日 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. 2023年5月9日 15:21 UTCresolved

   This incident has been resolved.

1. 2023年4月26日 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. 2023年4月26日 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. 2023年4月26日 16:37 UTCmonitoring

   We are waiting on Google resolutions

4. 2023年4月27日 8:22 UTCresolved

   Maestro installations are working as expected again

1. 2022年10月6日 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. 2022年10月6日 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. 2022年10月7日 22:26 UTCresolved

   Issue confirmed to be fixed by GitHub.

1. 2022年9月14日 20:15 UTCidentified

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

2. 2022年9月15日 17:03 UTCidentified

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

3. 2022年9月16日 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. 2022年10月6日 14:50 UTCresolved

   This incident has been resolved.

1. 2022年9月9日 7:20 UTCidentified

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

2. 2022年9月9日 8:51 UTCresolved

   This incident has been resolved.

3. 2022年9月9日 9: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. 2022年9月6日 11:53 UTCinvestigating

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

2. 2022年9月6日 11:57 UTCresolved

   This incident has been resolved.

1. 2022年8月30日 9: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. 2022年8月30日 15:11 UTCidentified

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

3. 2022年8月31日 9:15 UTCmonitoring

   We are continuing to monitor this incident

4. 2022年9月5日 8:21 UTCresolved

   This incident has been resolved.