Cronologia delle interruzioni di Lets Encrypt

1. 4 giugno 2026 alle ore 15:37 UTCresolved

   Giugno 3, 2026 16:05 UTC Identificata - Let's Encrypt's production API sta vivendo le prestazioni degradate. Abbiamo reindirizzato il traffico dal datacenter interessato. I client possono avere sporadicamente incontrato 404 e 500 risposte di errore a seconda della chiamata API e della natura intermittente del problema. 3 giugno 2026 17:23 UTC Monitoraggio - Tutti i sistemi nominali. Restiamo sempre vigili dei problemi di connettività di rete. Felice emissione. giugno 4, 2026 15:37 UTC Risolto -

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 13 maggio 2026 alle ore 20:32 UTCresolved

   8 maggio 2026 18:37 UTC Investigare - Siamo stati resi consapevoli di un potenziale incidente e stanno chiudendo tutta l'emissione. 8 maggio 2026 21:03 UTC Monitoring - Let's Encrypt ha ripreso l'emissione. A causa di un problema con il certificato cross-signed dalla nostra radice X di Generazione alla nostra nuova radice Y di Generazione, tutto l'emissione è stata spostata al nostro certificato radice X di Generazione. Ciò influisce sui nostri profili certificati ACME "tlsserver" e "shortlived". 13 maggio 2026 20:32 UTC Risolto - Abbiamo identificato che le nostre CA subordinate certificate trasversali mancano campi Extended Key Use (EKU) che sono ora necessari. Stiamo evocando e riscuotendo i nostri cross-signs di X2/YR di X1 e YE di X2. Questo non influenzerà la maggior parte degli abbonati Let’s Encrypt. Non rivocheremo i certificati di end-entity, in quanto sono ancora conformi. Tuttavia, qualsiasi certificato rilasciato dalle nostre radici YE e YR non può incatenare con successo alle nostre radici precedenti X1 e X2 senza un intermedio cross-signed aggiornato nella loro catena. Se hai un certificato rilasciato dai profili ACME “tlsserver” o “shortlived”, ti consigliamo di rinnovarli. Il nostro ACME Renewal Information API segnala i certificati interessati per rinnovare ora.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 16 marzo 2026 alle ore 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 marzo 2026 alle ore 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 dicembre 2025 alle ore 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 dicembre 2025 alle ore 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 dicembre 2025 alle ore 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 -