Lets Encrypt driftsforstyrrelser

1. 4. juni 2026 kl. 15.37 UTCresolved

   3. juni 2026 16: 05 UTC Identificeret - Lad os Krypt produktion API oplever forringet ydeevne. Vi har omdirigeret trafikken fra det berørte datacenter. Klienter kan have sporadisk stødt 404 og 500 fejlsvar afhængigt af API opkald og intermitterende karakter af problemet. 3. juni 2026 17: 23 UTC Overvågning - Alle systemer nominelle. Vi holder øje med netværksforbindelser. Tillykke med udstedelsen. 4. juni 2026 15: 37 UTC Opløst -

Automatisk oversat fra den officielle hændelsesopdatering.

1. 13. maj 2026 kl. 20.32 UTCresolved

   8. maj 2026 18: 37 UTC Undersøgelse - Vi er blevet gjort opmærksom på en potentiel hændelse og lukker ned for al udstedelse. 8. maj 2026 21: 03 UTC Monitoring - Lad os Krypt har genoptaget udstedelsen. På grund af et problem med det krydsunderskrevne certifikat fra vores generation X-rod til vores nye generation Y-rod, er al udstedelse blevet skiftet tilbage til vores generation X-rodcertifikat. Dette påvirker vores "tlsserver" og "kortlivede" ACME certifikat profiler. 13. maj 2026 20: 32 UTC Resolved - Vi har identificeret, at vores krydscertificerede underordnede CA 'er mangler Extended Key Usage (EKU) felter, som nu er nødvendige. Vi tilbagekalder og genudsender vores krydstegn på X2 / YR af X1, og YE af X2. Dette vil ikke påvirke de fleste Let' s Kryptér abonnenter. Vi vil ikke tilbagekalde enhedens certifikater, da de stadig er i overensstemmelse. Alle certifikater, der er udstedt fra vores rødder YE og YR, kan dog ikke kædes sammen med vores tidligere rødder X1 og X2 uden et opdateret krydssigneret mellemled i deres kæde. Hvis du har et certifikat udstedt af "tlsserver" eller "kortlivede" ACME profiler, anbefaler vi at forny dem. Vores ACME Renewal Information API signalerer berørte certifikater til fornyelse nu.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 16. marts 2026 kl. 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. marts 2026 kl. 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. december 2025 kl. 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. december 2025 kl. 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. december 2025 kl. 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 -