Can't connect to acme-staging-v01.api.letsencrypt.org

[Demeter]

Hello!
Permanently (from yesterday) have a error with certbot renew --dry-run:

Attempting to renew cert (mydomain) from /usr/local/etc/letsencrypt/renewal/mydomayn.conf produced an unexpected error: HTTPSConnectionPool(host=‘acme-staging-v02.api.letsencrypt.org’, port=443): Read timed out. (read timeout=45). Skipping.
__
root@server:~ # curl https://acme-staging-v02.api.letsencrypt.org -I
HTTP/1.1 504 Gateway Time-out
Server: AkamaiGHost
Mime-Version: 1.0
Content-Type: text/html
Content-Length: 176
Expires: Thu, 10 May 2018 04:30:47 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Thu, 10 May 2018 04:30:47 GMT
Connection: keep-alive

So, is there any problem with ACME server now?

[mnordhoff]

Yes, the staging environment is currently down for maintenance.

Production is working normally.

https://letsencrypt.status.io/

[Favicon]

Please, can we have some more information about this maintenance? The disruption has lasted a long time already and I can’t find any indication of when it should end. The status page (https://letsencrypt.status.io) says " information on current status and outages can be found at: community.letsencrypt.org" but on there the only reference to service status that I can see is a banner at the top linking back to the status page.

Is there a plan for when the staging environment should be back online?

[mhmeadows63]

This link for the Staging Downtime : Planned Maintenance suggests the scheduled window is May 9, 2018 14:00 - May 10, 2018 02:00 UTC

It now being May 10, 2018 12:00 UTC implies the scheduled 12hrs have overrun by some 10hrs.

A revised ETA would be very helpful - my interest is in acme-staging-v02.api.letsencrypt.org

[josh]

Our apologies for the staging API being down for so long. We have a team performing a major hardware migration and reconfiguration in the datacenter (DC) that hosts our staging infrastructure. That work did not complete in time, and we failed to update the status to reflect that. We are fixing it now.

Unlike our production infrastructure, which is spread across multiple DCs for redundancy, our staging infrastructure only exists in one DC. If we take that DC offline, as we did yesterday, staging goes down with it.

All production API traffic was moved to a second DC so it should all be working fine. It should not have been affected by this work at any point.

We will complete the work within the next eight hours, hopefully much less.

[bsutton]

Can we get another update.
Its now 10h post the possible eight hour window?

[Phil]

@bsutton and @mhmeadows63
Thank you both for being patient. The staging environment is back up and running. https://letsencrypt.status.io/pages/history/55957a99e800baa4470002da