Histórico de interrupções do Lets Encrypt

1. 4 Mezheven 2026 da 15:37 UTCresolved

   3 de Junho de 2026 16:05 UTC Identificado - A API de produção do Let's Encrypt está experimentando desempenho degradado. Redireccionamos o tráfego do centro de dados afectado. Os clientes podem ter encontrado esporadicamente 404 e 500 respostas de erro, dependendo da chamada API e da natureza intermitente do problema. 3 de Junho de 2026 17:23 UTC Monitoramento - Todos os sistemas nominais. Estamos sempre atentos aos problemas de conectividade de rede. Feliz emissão. 4 de junho de 2026 15:37 UTC Resolução -

Traduzido automaticamente da atualização oficial do incidente.

1. 13 Mae 2026 da 20:32 UTCresolved

   8 de maio de 2026 18:37 UTC Investigação - Fomos informados de um incidente potencial e estamos a encerrar toda a emissão. 8 de Maio de 2026 21:03 UTC Monitoring - Let's Encriptar retomou a emissão. Devido a um problema com o certificado de assinatura cruzada da nossa raiz da Geração X para a nossa nova raiz da Geração Y, toda a emissão foi trocada de volta para o nosso certificado de raiz da Geração X. Isso afeta nossos perfis de certificados "tlsserver" e "shortlived" ACME. 13 de Maio de 2026 20:32 UTC Resolvido - Identificamos que nossos CAs subordinados com certificação cruzada estão faltando Campos de Uso de Chave Extendida (EKU) que agora são necessários. Estamos revogando e reissando nossos sinais cruzados de X2/YR por X1, e YE por X2. Isso não afetará a maioria dos assinantes do Let’s. Não vamos revogar os certificados de finalidade, uma vez que ainda estão em conformidade. No entanto, quaisquer certificados emitidos a partir das nossas raízes YE e YR não podem encadear com sucesso as nossas raízes anteriores X1 e X2 sem um intermediário com assinatura cruzada atualizado em sua cadeia. Se você tem um certificado emitido pelo “tlsserver” ou perfis ACME de curta duração, recomendamos renová-los. Nossa API de informação de renovação ACME está sinalizando certificados afetados para renovar agora.

Traduzido automaticamente da atualização oficial do incidente.

1. 16 Meurzh 2026 da 20:40 UTCresolved

   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. 4 Meurzh 2026 da 23:03 UTCresolved

   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. 16 Kerzu 2025 da 16:28 UTCresolved

   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. 10 Kerzu 2025 da 20:54 UTCresolved

   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. 10 Kerzu 2025 da 17:57 UTCresolved

   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 -