Green Cloud Technologies 中断历史

1. 2026年9月3日 UTC 16:20resolved

   11:11 系统工程师将所有遗留下来的"绿云防御"客户通信转移到了我们的全球通信工具. 截止今天,2026年9月3日,我们有日落网站:https://status.grancld.net/. 所有今后的维护和事件通知将通过客户门户在11:11系统传送。 如果你还没有选择加入这些未来的维护和事件通信,请使用下面的链接来学习如何选择加入这些通信. 如何通过账户App登录和订阅通知:https://success.1111 systems.com/docs/11-service-information/service-status-in-the-count-app 如果您需要帮助, 请联系您的 11: 11 系统服务管理员( 可在 App 账户主页获取) .

自动翻译自官方事件更新。

1. 2026年9月2日 UTC 16:09resolved

   11:11 系统工程师将把所有遗留的"绿云防御"客户通信转移到我们的全球通信工具. https://status.grncld.net/ 2026年9月3日将所有维护及事故通知转移到您的客户门户网站。 客户必须选择加入,以便今后进行维修和发出事故通知。 请使用下面的链接来学习如何选择使用这些通信. 如果您需要帮助, 请联系您的 11: 11 系统服务管理员( 可在 App 账户主页获取) 。 如何通过账户App登录和订阅通知:https://success.1111 systems.com/docs/11-service-information/service-status-in-the-count-app

自动翻译自官方事件更新。

1. 2026年8月31日 UTC 19:13resolved

   11:11 系统工程师将把所有遗留的"绿云防御"客户通信转移到我们的全球通信工具. https://status.grncld.net/ 2026年9月3日将所有维护及事故通知转移到您的客户门户网站。 客户必须选择加入,以便今后进行维修和发出事故通知。 请使用下面的链接来学习如何选择使用这些通信. 如果您需要帮助, 请联系您的 11: 11 系统服务管理员( 可在 App 账户主页获取) 。 如何通过账户App登录和订阅通知:https://success.1111 systems.com/docs/11-service-information/service-status-in-the-count-app

自动翻译自官方事件更新。

1. 2026年8月26日 UTC 13:19resolved

   11:11 系统工程师将把所有遗留的"绿云防御"客户通信转移到我们的全球通信工具. https://status.grncld.net/ 2026年9月3日将所有维护及事故通知转移到您的客户门户网站。 客户必须选择加入,以便今后进行维修和发出事故通知。 请使用下面的链接来学习如何选择使用这些通信. 如果您需要帮助, 请联系您的 11: 11 系统服务管理员( 可在 App 账户主页获取) 。 如何通过账户App登录和订阅通知:https://success.1111 systems.com/docs/11-service-information/service-status-in-the-count-app

自动翻译自官方事件更新。

1. 2026年8月21日 UTC 16:23resolved

   11:11 系统工程师将把所有遗留的"绿云防御"客户通信转移到我们的全球通信工具. https://status.grncld.net/ 2026年9月3日将所有维护及事故通知转移到您的客户门户网站。 客户必须选择加入,以便今后进行维修和发出事故通知。 请使用下面的链接来学习如何选择使用这些通信. 如果您需要帮助, 请联系您的 11: 11 系统服务管理员( 可在 App 账户主页获取) 。 如何通过账户App登录和订阅通知:https://success.1111 systems.com/docs/11-service-information/service-status-in-the-count-app

自动翻译自官方事件更新。

1. 2026年5月26日 UTC 16:21resolved

   11:11 Systems engineers will be migrating all of the legacy Green Cloud Defense customer communications into our global communications tool. We will be sunsetting the site: https://status.grncld.net/ and transitioning all maintenance and incident notifications to your customer portal on 2 June 2026. Customers will be required to opt-in for future maintenance and incident notifications. Please use the link below to learn how to opt-in to these communications. If you require any help, please contact your 11:11 Systems Service Manager (available in the Account App home page). How to Opt-in and Subscribe to notifications via the Account App: https://success.1111systems.com/docs/11-11-services-information/service-status-in-the-account-app

1. 2026年5月25日 UTC 01:57resolved

   Due to a failure of a hypervisor compute node in our Atlanta data center supporting IaaS, a small number of virtual appliances were automatically restarted onto other compute nodes. This restart activity concluded by 9:40 pm Eastern Time. Please contact 11:11 Support if you have any questions regarding this incident.

1. 2026年5月19日 UTC 16:44resolved

   11:11 Systems engineers will be migrating all of the legacy Green Cloud Defense customer communications into our global communications tool. We will be sunsetting the site: https://status.grncld.net/ and transitioning all maintenance and incident notifications to your customer portal on 2 June 2026. Customers will be required to opt-in for future maintenance and incident notifications. Please use the link below to learn how to opt-in to these communications. If you require any help, please contact your 11:11 Systems Service Manager (available in the Account App home page). How to Opt-in and Subscribe to notifications via the Account App: https://success.1111systems.com/docs/11-11-services-information/service-status-in-the-account-app

1. 2026年5月15日 UTC 15:47resolved

   11:11 Systems engineers will be migrating all of the legacy Green Cloud Defense customer communications into our global communications tool. We will be sunsetting the site: https://status.grncld.net/ and transitioning all maintenance and incident notifications to your customer portal on 2 June 2026. Customers will be required to opt-in for future maintenance and incident notifications. Please use the link below to learn how to opt-in to these communications. If you require any help, please contact your 11:11 Systems Service Manager (available in the Account App home page). How to Opt-in and Subscribe to notifications via the Account App: https://success.1111systems.com/docs/11-11-services-information/service-status-in-the-account-app

1. 2026年4月28日 UTC 17:23resolved

   11:11 Systems engineers will be migrating all of the legacy Green Cloud Defense customer communications into our global communications tool. We will be sunsetting the site: https://status.grncld.net/ and transitioning all maintenance and incident notifications to your customer portal on 2 June 2026. Customers will be required to opt-in for future maintenance and incident notifications. Please use the link below to learn how to opt-in to these communications. If you require any help, please contact your 11:11 Systems Service Manager (available in the Account App home page). How to Opt-in and Subscribe to notifications via the Account App: https://success.1111systems.com/docs/11-11-services-information/service-status-in-the-account-app

1. 2026年3月18日 UTC 18:39identified

   11:11 engineers have identified an issue affecting VPG's replicating to the Houston environment. VPG's will have an error message indicating no connection to VCD, however replication is still happening. Engineers have engaged the vendor for this issue.

2. 2026年3月18日 UTC 19:41monitoring

   A fix has been implemented and we are monitoring the results.

3. 2026年3月18日 UTC 21:19resolved

   This incident has been resolved.

1. 2025年12月15日 UTC 21:18identified

   Due to a failure of a hypervisor compute node in our Houston data center supporting IaaS, a small number of virtual appliances were automatically restarted onto other compute nodes. This restart activity concluded by 4:16 pm Eastern Time. Please contact 11:11 Support if you have any questions regarding this incident.

2. 2025年12月15日 UTC 21:29resolved

   This incident has been resolved.

1. 2025年11月3日 UTC 22:54resolved

   Due to a failure of a hypervisor compute node in our Atlanta data center supporting IaaS, a small number of virtual appliances were automatically restarted onto other compute nodes. This restart activity concluded by 5:54 pm Eastern Time. Please contact 11:11 Support if you have any questions regarding this incident.

1. 2025年10月31日 UTC 15:52resolved

   Due to a failure of a hypervisor compute node in our Nashville data center supporting IaaS, a small number of virtual appliances were automatically restarted onto other compute nodes. This restart activity concluded by 11:42 am Eastern Time. Please contact 11:11 Support if you have any questions regarding this incident.

1. 2025年9月6日 UTC 17:55resolved

   Due to a failure of a hypervisor compute node in our Greenville, SC data center supporting IaaS, a small number of virtual appliances were automatically restarted onto other compute nodes. This restart activity concluded by 1:52pm Eastern Time. Please contact 11:11 Support if you have any questions regarding this incident.

1. 2025年9月2日 UTC 14:26resolved

   Due to a failure of a hypervisor compute node in our Atlanta Datacenter supporting IaaS, a small number of virtual appliances were automatically restarted onto other compute nodes. This restart activity concluded by 10:11 am Eastern Time. Please contact 11:11 Support if you have any questions regarding this incident.

1. 2025年8月18日 UTC 19:35investigating

   We are aware of an issue in which customer emails are not being converted into tickets for our support teams. If you require urgent assistance, please use Account App, phone or chat to contact a member of your support team. Engineers are engaged and working to resolve the issue. The next update will be provided as information becomes available.

2. 2025年8月19日 UTC 15:54resolved

   Engineers identified and resolved the issue affecting ticket generation from customer emails. There will be no further updates to this event.

1. 2025年7月18日 UTC 20:21investigating

   11:11 Engineers are currently aware of an issue with one of the repositories supporting this location. While engineers work to clear this issue, we recommend that if customers have a backup job that is failing to this location, run a full backup of their job.

2. 2025年7月22日 UTC 21:47investigating

   11:11 Engineers continue to work on the affected repository in this location. We will provide further updates as they are available.

3. 2025年8月26日 UTC 15:02resolved

   This incident has been resolved.

1. 2025年6月10日 UTC 17:55investigating

   Engineers are aware of an issue current in the GSP datacenter and are currently investigating.

2. 2025年6月10日 UTC 19:08identified

   11:11 engineers have identified the issue in the Greenville datacenter and are working to remediate. Customers should start to see some recovery, but full recovery will take additional time as engineers continue to work through this incident.

3. 2025年6月10日 UTC 20:21identified

   11:11 engineers are currently rebooting hosts in this environment to aid in recovery. Some customer VM's may be rebooted as part of that process. Another update will be posted once reboots are completed.

4. 2025年6月10日 UTC 21:51monitoring

   11:11 engineers completed host reboots and have confirmed systems are is now normal. All customer functionality has been restored. Engineers will monitor the environment for continued stability.

5. 2025年6月11日 UTC 21:37resolved

   The environment has remained stable and all services continue to remain operational. This incident is now resolved. If you have any questions, please contact our Support Helpdesk for additional assistance. If you continue to experience any errors or issues, please contact our Support Helpdesk for additional assistance.

1. 2025年5月16日 UTC 21:50resolved

   Due to a failure of a hypervisor compute node in our Atlanta, GA data center supporting IaaS, a small number of virtual appliances were automatically restarted onto other compute nodes. This restart activity concluded by 5:45pm Eastern Time. Please contact 11:11 Support if you have any questions regarding this incident.