Lets Encrypt 中断历史

1. 2026年6月4日 UTC 15:37resolved

   协调世界时2026年6月3日 16:05 识别 - 让我们加密的制作 API正在经历退化的性能. 我们重新调整了来自受灾数据中心的流量 客户根据API的呼叫和问题的间歇性质,可能偶尔遇到404和500个错误回复. 协调世界时2026年6月3日17:23 监测 - 所有系统的名义。 我们正在保持警惕 网络连接问题。 发行愉快. 世界协调时2026年6月4日 15:37 决定-

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

1. 2026年5月13日 UTC 20:32resolved

   协调世界时2026年5月8日18:37 调查 - 我们已意识到可能发生的事件,并正在关闭所有签发。 2026年5月8日 21:03 UTC监测 - 让我们加密恢复发布. 由于我们的"一代X"根到"新一代Y"根的交叉签名证书出现问题,所有发行都被转回"一代X"根证书. 这影响了我们的"tlsserver"和"短命"的ACME证书配置. 协调世界时2026年5月13日 20:32 解决 - 我们已经确认,我们跨认证的下属CA缺少目前需要的扩展密钥使用域。 我们撤消并重新发布X2/YR到X1,YE到X2的交叉符号. 这不会影响大多数用户。 我们不会撤销最终实体证书,因为这些证书仍然得到遵守。 然而,从我们的根 YE 和 YR 签发的任何证书,如果不在其链中更新交叉签名的中间体,则可能无法成功链到我们以前的根 X1 和 X2 上. 如果您有“tsserver”或“short life” ACME 简介签发的证书,我们建议更新这些证书。 我们的ACME 更新信息 API 正在信号 受影响的证书现在更新.

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

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

   March 16, 2026 17:36 UTC Investigating - To fulfill our required compliance obligations, we are performing an incident drill. During this drill, we are stopping issuance from staging. March 16, 2026 18:05 UTC Monitoring - We are resuming issuance. As part of our drill, we have dropped authorizations prior to the beginning of the drill. If you receive an error related to missing authorizations, retry issuance. March 16, 2026 18:05 UTC Monitoring - We are resuming issuance. As part of our drill, we have dropped authorizations prior to the beginning of the drill. If you receive an error related to missing authorizations, retry issuance. March 16, 2026 18:24 UTC Investigating - We are disabling staging issuance again for our incident drill. March 16, 2026 19:17 UTC Monitoring - We are resuming issuance. As part of our drill, we have expired all preexisting orders. If you receive an error, retry issuance with a new order. March 16, 2026 20:40 UTC Resolved - We have concluded our drill activities in staging for today, and issuance has appeared healthy for a while.

1. 2026年3月4日 UTC 23:03resolved

   March 4, 2026 19:44 UTC Scheduled - We will be performing maintenance on our staging database cluster and will be temporarily disabling issuance for the duration. March 4, 2026 19:59 UTC Active - We are beginning staging maintenance now. March 4, 2026 20:36 UTC Active - Maintenance is ongoing and will go past the initial time estimate, apologies for that. March 4, 2026 21:17 UTC Active - Maintenance is still ongoing. March 4, 2026 22:03 UTC Active - Maintenance is still ongoing. March 4, 2026 22:27 UTC Active - Maintenance is ongoing and we're keeping an eye on the progress. March 4, 2026 23:03 UTC Completed - Staging database maintenance was completed successfully and the API is back up and issuing certificates/CRLs. Happy staging issuance everybody reading this. Slow and steady amiright?

1. 2025年12月16日 UTC 16:28resolved

   December 16, 2025 16:01 UTC Identified - We have identified an issue with an internal service related to serving the production API. We are working to restore the service. December 16, 2025 16:17 UTC Monitoring - The production API services are stabilizing and successful issuance should be resuming shortly. December 16, 2025 16:28 UTC Resolved - Services have recovered.

1. 2025年12月10日 UTC 20:54resolved

   December 10, 2025 19:01 UTC Scheduled - We'll be performing routine maintenance in a High Assurance Datacenter 2. Some ACME clients may see elevated latencies. December 10, 2025 19:02 UTC Active - Maintenance will now begin. December 10, 2025 20:54 UTC Completed - Maintenance has been completed successfully.

1. 2025年12月10日 UTC 17:57resolved

   December 9, 2025 16:42 UTC Investigating - We are investigating some requests experiencing high latency when making requests to the API. December 9, 2025 16:58 UTC Investigating - We have shifted traffic out of high assurance data center 2 so that it is no longer serving requests and API latency looks normal. We are continuing to investigate root cause. December 9, 2025 23:05 UTC Identified - We have shifted traffic back to both data centers and are continuing to monitor for any unusual API responses or latency. December 10, 2025 00:28 UTC Monitoring - We have reshaped some traffic and continue to monitor for any recurrences of API latency and increases in 503 responses. December 10, 2025 17:57 UTC Resolved -