Istoricul incidentelor Lets Encrypt

1. 4 iunie 2026 la 15:37 UTCresolved

   3 iunie 2026 16:05 UTC Identificat - Să Criptăm producția API se confruntă cu performanțe degradate. Am redirecţionat traficul din centrul de date afectat. Clienții pot fi întâlnit sporadic 404 și 500 de răspunsuri de eroare în funcție de apelul API și natura intermitentă a problemei. 3 iunie 2026 17:23 UTC Monitorizare - Toate sistemele nominale. Rămânem vigilenţi cu privire la problemele legate de conectivitatea reţelei. O emisiune fericită. 4 iunie 2026 15:37 UTC Rezolvat -

Traducere automată din actualizarea oficială a incidentului.

1. 13 mai 2026 la 20:32 UTCresolved

   8 mai 2026 18:37 UTC Investigaţii - Am fost informaţi despre un potenţial incident şi închidem toate emisiunile. 8 mai 2026 21:03 UTC Monitoring - Să cripteze a reluat emisiunea. Din cauza unei probleme cu certificatul semnat încrucişat de la rădăcina noastră Generaţia X la noua noastră rădăcină de generaţie Y, toată emisiunea a fost schimbată înapoi la certificatul nostru de rădăcină Generaţia X. Acest lucru afectează profilurile noastre de certificat ACME "Tlsserver" și "Shortlived." 13 mai 2026 20:32 UTC Rezolvat - Ne-am identificat că CA-urile noastre subordonate certificate încrucișat lipsesc câmpuri de utilizare extinsă a cheii (EKU), care sunt acum necesare. Revocăm şi reemitem semnele noastre încrucişate de X2/YR până la X1 şi YE până la X2. Acest lucru nu va afecta cele mai Lets cripta abonați. Nu vom revoca certificatele de entitate finală, deoarece acestea sunt încă conforme. Cu toate acestea, orice certificate emise din rădăcinile noastre YE și YR nu pot lega cu succes rădăcinile noastre anterioare X1 și X2 fără un intermediar trans-semnat actualizat în lanțul lor. Dacă aveți un certificat eliberat de către Tlsserver sau de profilele ACME, vă recomandăm să le reînnoiți. ACME Reînnoirea noastră Informații API este de semnalizare certificate afectate pentru a reînnoi acum.

Traducere automată din actualizarea oficială a incidentului.

1. 16 martie 2026 la 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 martie 2026 la 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 decembrie 2025 la 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 decembrie 2025 la 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 decembrie 2025 la 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 -