3 ms·

Isn't the "DNS errors causing service disruption" an old incident from April 6th? There is something strange going on at the moment, though, but not sure it ha

Isn't the "DNS errors causing service disruption" an old incident from April 6th? There is something strange going on at the moment, though, but not sure it has to do with DNS. I actually tried set up my first cert about 10 hours ago with Let's Encrypt, and got a variety of ungraceful errors with the same configuration. Only one was related to DNS. Most were code 500 from the api servers.

viraptor 11y ago
Their status page is broken. You can see the actual issue on the history page instead, or specifically https://letsencrypt.status.io/pages/incident/55957a99e800baa4470002da/570fe5aafe92599160001098 https://letsencrypt.status.io/pages/incident/55957a99e800baa... April 14, 2016 12:47PM MDT April 14, 2016 6:47PM UTC [Investigating] We have noticed an increased number of errors. We are investigating now. April 14, 2016 1:21PM MDT April 14, 2016 7:21PM UTC [Resolved] Systems have fully recovered and all services appear to be operating nominally. Cause seems to have been a transient hardware failure and further investigation is under way. Or at least the most recent issue... they both marked it as resolved and "further investigation is under way". Should be "investigating/monitoring" instead?
antouank 11y ago
I don't know what the exact title should be. If you see here, https://letsencrypt.status.io/pages/history/55957a99e800baa4470002da https://letsencrypt.status.io/pages/history/55957a99e800baa4... , there's a "Investigating interruption of issuances" event from yesterday. I had problem with getting certificates yesterday. Seems to be working today, but I just thought it's interesting to see what happened.