Historial de interrupciones de Lets Encrypt

1. June 4, 2026 at 3:37 PM UTCresolved

   3 de junio de 2026 16:05 UTC Identificado - Vamos a la API de producción de Encrypt está experimentando un rendimiento degradado. Hemos redirigido el tráfico del centro de datos afectado. Los clientes pueden haber encontrado sporádicamente 404 y 500 respuestas de error dependiendo de la llamada API y la naturaleza intermitente de la cuestión. 3 de junio de 2026 17:23 UTC Monitoreo - Todos los sistemas nominales. Nos mantenemos vigilantes de problemas de conectividad de red. Feliz emisión. 4 de junio de 2026 15:37 UTC Resolved -

Traducido automáticamente desde la actualización oficial del incidente.

1. May 13, 2026 at 8:32 PM UTCresolved

   8 de mayo de 2026 18:37 UTC Investigación - Hemos sido conscientes de un posible incidente y estamos cerrando toda emisión. May 8, 2026 21:03 UTC Monitoring - Vamos a Encrypt ha reanudado la emisión. Debido a un número con el certificado cruzado de nuestra raíz Generation X a nuestra nueva raíz Generation Y, toda emisión ha sido transferida a nuestro certificado raíz Generation X. Esto afecta a nuestros perfiles de certificados ACME "tlsserver" y "shortlived". Mayo 13, 2026 20:32 UTC Resolvidos - Hemos identificado que nuestros CAs subordinados certificados cruzados están desaparecidos campos de Uso Clave Extendido (EKU) que ahora son necesarios. Estamos revocando y reemitiendo nuestras transmisiones de X2/YR por X1, y YE por X2. Esto no afectará a la mayoría de los suscriptores de Encrypt. No vamos a revocar los certificados de end-entity, ya que siguen siendo compatibles. Sin embargo, cualquier certificado emitido a partir de nuestras raíces YE y YR no puede encadenar con éxito a nuestras anteriores raíces X1 y X2 sin un intermedio actualizado en su cadena. Si tiene un certificado emitido por los perfiles “tlsserver” o “shortlived” ACME, recomendamos renovarlos. Nuestra API de información de renovación ACME está señalizando certificados afectados para renovar ahora.

Traducido automáticamente desde la actualización oficial del incidente.

1. March 16, 2026 at 8:40 PM 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. March 4, 2026 at 11:03 PM 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. December 16, 2025 at 4:28 PM 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. December 10, 2025 at 8:54 PM 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. December 10, 2025 at 5:57 PM 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 -