You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We got a large volume of issues related to this, so I'd like to consolidate them to a single issue. Thanks to everyone who reported this issue! https://status.hashicorp.com/ is the canonical location for status updates but I'm updating here because of how many folks reported issues to this issue tracker.
There was outage impacting releases.hashicorp.com and registry downloads. Users impacted by this have been getting HTTP 403 and 404 errors downloading Terraform releases and providers via the registry.
Engineers have a good understanding of what happened and have a fix in place. I'm watching the internal incident room, and as of 12:59 PM EST the incident appears to be resolved, and engineers are monitoring error rates to confirm that it is indeed fixed.
The text was updated successfully, but these errors were encountered:
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
ghost
locked as resolved and limited conversation to collaborators
May 1, 2021
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We got a large volume of issues related to this, so I'd like to consolidate them to a single issue. Thanks to everyone who reported this issue! https://status.hashicorp.com/ is the canonical location for status updates but I'm updating here because of how many folks reported issues to this issue tracker.
There was outage impacting releases.hashicorp.com and registry downloads. Users impacted by this have been getting HTTP 403 and 404 errors downloading Terraform releases and providers via the registry.
Engineers have a good understanding of what happened and have a fix in place. I'm watching the internal incident room, and as of 12:59 PM EST the incident appears to be resolved, and engineers are monitoring error rates to confirm that it is indeed fixed.
The text was updated successfully, but these errors were encountered: