Amazee 中断历史

1. 2026年10月27日 UTC 18:22monitoring

   我们目前正在对我们的系统进行例行维护。 在此期间,您在连接AI基础设施时可能会遇到短暂的中断或延迟.

2. 2026年10月27日 UTC 18:41resolved

   这一事件已经得到解决.

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

1. 2026年10月26日 UTC 19:52monitoring

   我们目前正在对我们的系统进行例行维护。 在此期间,您在连接AI基础设施时可能会遇到短暂的中断或延迟.

2. 2026年10月26日 UTC 20:12resolved

   这一事件已经得到解决.

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

1. 2026年10月21日 UTC 03:43investigating

   amazee.io意识到即将到来的关键PHP安全发布会修复两个CVE:CVE-2026-109618和CVE-2026-109619. 发布时间为2026年10月21日星期三,协调世界时14:00. 一旦有补丁,将更新Lagoon基础图像,并鼓励客户尽快重新部署. 详情请见上游PHP公告:https://www.php.net/archive/2026.php#2026-10-20-1. 我们正在监测局势并调查平台一级的缓解措施。 我们将更新这一状况网页,提供更多信息.

2. 2026年10月21日 UTC 10:51investigating

   我们利用我们管理的NGWAF为客户提供了虚拟补丁。 一旦有补丁,您仍应更新您的 Lagoon 基础图像 .

3. 2026年10月21日 UTC 14:44monitoring

   固定的PHP版本已经发布,并宣布了更多细节,包括缓解 https://www.php.net/archive/2026.php#2026-10-21-5. 我们正等待新版本发布到我们所有上游的依赖地区,然后才能发布新版本的Lagoon基站图像.

4. 2026年10月21日 UTC 17:22monitoring

   New Lagoon images are currently building. The required upstream Docker images have been released. We are currently building and testing version 26.10.0 of our Lagoon base images. The new images will be published shortly. We will provide a final update as soon as they are available for deployment.

5. 2026年10月21日 UTC 19:22monitoring

   Lagoon base images v26.10.0 are now published and available. Customers are advised to deploy their environments to patch the PHP vulnerabilities. We have increased resources to help reduce build queues, but expect wait times while all deployments are processed. We will continue to monitor deployment queues until operations normalize.

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

1. 2026年9月21日 UTC 11:06investigating

   我们正在调查一个问题 与我们的内部吸尘器登记

2. 2026年9月21日 UTC 11:43identified

   这一问题已经确定,一个解决办法正在实施之中.

3. 2026年9月21日 UTC 11:43identified

   我们正在继续努力解决这个问题。

4. 2026年9月21日 UTC 11:44monitoring

   一项措施已经执行,我们正在监测结果.

5. 2026年9月21日 UTC 14:49resolved

   这一事件已经得到解决.

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

1. 2026年9月15日 UTC 04:25investigating

   我们准备回旋回旋 CH4的Traefik迁移 来调查问题

2. 2026年9月15日 UTC 05:07monitoring

   倒转完成。 一些场地在倒塌期间可能比其他场地的停用时间更长.

3. 2026年9月15日 UTC 21:33resolved

   这一事件已经得到解决.

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

1. 2026年9月7日 UTC 22:16investigating

   我们正在进行入室移徙。 估计会出现最小的停电,我们很快就会恢复正常服务.

2. 2026年9月8日 UTC 00:14resolved

   这一事件已经得到解决.

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

1. 2026年7月27日 UTC 21:01investigating

   我们目前正在对我们的系统进行例行维护。 在此期间,您在连接AI基础设施时可能会遇到短暂的中断或延迟.

2. 2026年7月27日 UTC 23:13resolved

   这一事件已经得到解决.

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

1. 2026年7月23日 UTC 14:03investigating

   我们目前正在对我们的系统进行例行维护。 在此期间,您在连接AI基础设施时可能会遇到短暂的中断或延迟.

2. 2026年7月23日 UTC 17:55monitoring

   一项措施已经执行,我们正在监测结果.

3. 2026年7月24日 UTC 04:34resolved

   这一事件已经得到解决.

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

1. 2026年7月17日 UTC 16:50investigating

   我们注意到部署的等待时间有所增加,目前正在调查这一问题.

2. 2026年7月17日 UTC 16:55identified

   我们已查明拖延的原因,并正在执行这项措施.

3. 2026年7月17日 UTC 20:34monitoring

   一项固定措施已经执行,我们正在监测这一问题.

4. 2026年7月18日 UTC 14:01resolved

   这个问题已经得到解决.

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

1. 2026年7月8日 UTC 16:49monitoring

   We are currently conducting routine maintenance on our systems. During this time, you may experience brief interruptions or delays when connecting to the AI infrastructure.

2. 2026年7月8日 UTC 17:05resolved

   This incident has been resolved.

1. 2026年7月1日 UTC 14:03monitoring

   There is a delay in log processing and recent logs for events generated since July 1st may not be available. Real time logs can be accessed through the Lagoon CLI: https://docs.amazee.io/cloud/logging/#real-time-container-logs-via-lagoon-cli

2. 2026年7月1日 UTC 17:09resolved

   This incident has been resolved.

1. 2026年6月17日 UTC 02:39investigating

   We are currently investigating this issue.

2. 2026年6月17日 UTC 03:37identified

   The issue has been identified and we are working to address it.

3. 2026年6月17日 UTC 04:56monitoring

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

4. 2026年6月17日 UTC 04:57monitoring

   The access roles are resyncing and we are monitoring progress.

5. 2026年6月18日 UTC 02:00monitoring

   We are continuing to monitor the resync progress.

6. 2026年6月19日 UTC 02:32resolved

   This incident has been resolved.

1. 2026年6月1日 UTC 14:44monitoring

   TLS certificate provisioning and renewal may be delayed on affected clusters during this window. We are monitoring the upstream incident and will provide updates as the situation evolves. https://status.redhat.com/

2. 2026年6月2日 UTC 06:54resolved

   This incident has been resolved.

1. 2026年6月1日 UTC 14:07monitoring

   There is a delay in log processing and recent logs for events generated since June 1st may not be available. Real time logs can be accessed through the Lagoon CLI: https://docs.amazee.io/cloud/logging/#real-time-container-logs-via-lagoon-cli

2. 2026年6月1日 UTC 17:33resolved

   This incident has been resolved.

1. 2026年5月19日 UTC 02:09identified

   Drupal has announced an upcoming highly critical Drupal core security release affecting Drupal 10 and 11 (and EOL versions 8 and 9). Customer impact - Prepare now: Update to the latest patch release on your current supported Drupal version ahead of time to reduce time-to-patch. - Schedule a maintenance window: May 20, 17:00 - 21:00 UTC. Customers should be prepared to apply the security update immediately once released. - EOL Drupal versions: Drupal 8.9 and 9.5 will receive patch files only (temporary mitigation). Plan an urgent upgrade to a supported version. Drupal 7 is not affected. What we're doing We're treating this as a priority security event and preparing WAF/CDN mitigations ("virtual patches") where possible. These may provide partial/temporary protection; applying the upstream Drupal security update remains the primary mitigation. We’ll share updates here as more information becomes available. For more information, see the Drupal PSA: https://www.drupal.org/psa-2026-05-18

2. 2026年5月20日 UTC 19:26monitoring

   We’ve reviewed today’s Drupal-related release and do not currently anticipate deploying WAF/CDN mitigations ("virtual patches"). Based on our assessment, overall exposure appears more limited than initial thoughts. Customers should review the security release notes to determine their potential impact and update as soon as practical: https://www.drupal.org/sa-core-2026-004. We will continue monitoring the situation and provide updates necessary.

3. 2026年6月2日 UTC 06:54resolved

   This incident has been resolved.

1. 2026年5月7日 UTC 18:08identified

   We are currently experiencing an issue with cert-manager in affected clusters. The cert-manager controller pod is failing to start due to an image pull failure from quay.io (502 Bad Gateway), which is an external registry. Impact: New TLS certificates cannot be issued or renewed while cert-manager is unavailable. Existing certificates remain valid until their expiry. Services relying on automatic certificate provisioning may be affected if certificates expire during this window. https://status.redhat.com/

2. 2026年5月7日 UTC 18:24monitoring

   All clusters are able to pull cert-manager image, we are currently monitoring statuspage https://status.redhat.com/

3. 2026年5月7日 UTC 21:14resolved

   This incident has been resolved.

1. 2026年4月30日 UTC 01:33identified

   We are aware of CVE-2026-31431 / "Copy Fail" and have completed an initial assessment. We have not identified evidence of customer impact, service compromise, or active exploitation at this stage. We are prioritizing Linux kernel upgrades and will provide further updates if our assessment changes or if maintenance becomes necessary.

2. 2026年5月13日 UTC 06:01resolved

   Mitigations at the Linux kernel level have been rolled out across all regions.

1. 2026年4月29日 UTC 09:19investigating

   We are currently investigating a high error rate on the Fastly management API. This impacts deployments of new domains that are routed through Fastly. Existing setups on Fastly or traffic routing are not impacted.

2. 2026年4月29日 UTC 09:58investigating

   Fastly is investigating the API issues and updating their status page at: https://www.fastlystatus.com/incident/378511 Impact: Deployments with new domains that are routed through Fastly will continue to work, but the actual domain setup in Fastly will be delayed.

3. 2026年4月29日 UTC 11:15monitoring

   Fastly resolved the issue with their management API and we'll keep monitoring the situation.

4. 2026年4月29日 UTC 12:51resolved

   This incident has been resolved.

1. 2026年4月21日 UTC 12:09investigating

   We are currently investigating this issue.

2. 2026年4月21日 UTC 13:03resolved

   This incident has been resolved.

1. 2026年4月15日 UTC 04:19identified

   There was an issue with an EKS rollout during maintenance, we are actively addressing this issue.

2. 2026年4月15日 UTC 06:16monitoring

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

3. 2026年4月15日 UTC 07:24resolved

   This incident has been resolved.