HashiCorp Vault reported this minor-impact incident on its official status page on Jul 21, 2026, 10:32 UTC. It was resolved after 2h 12m.
Right now HashiCorp Vault is operational. Live HashiCorp Vault status →
GitHub has completed remediation of the SSH deploy key incident. Terraform runs using GitHub-hosted modules/sources over SSH have recovered, clone operations are functioning normally, and no further authentication failures are being observed.
GitHub has completed remediation of the incident affecting SSH deploy keys. Terraform runs using GitHub-hosted modules and sources over SSH have recovered, and clone operations are functioning normally. We are no longer observing related authentication failures and will continue monitoring.
GitHub has completed remediation of the incident affecting SSH deploy keys. Terraform runs using GitHub-hosted modules and sources over SSH have recovered, and clone operations are functioning normally. We are no longer observing related authentication failures and will continue monitoring.
We are investigating failures cloning GitHub-hosted Terraform modules and sources over SSH, caused by an ongoing upstream GitHub incident affecting SSH deploy keys. Runs using `git::ssh://` or `[email protected]:` sources may fail with Permission denied (publickey); HTTPS and registry-based sources are unaffected. We're tracking GitHub's remediation and will update as we learn more.
Our 5-minute checks didn't record a change in HashiCorp Vault's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.
Overlapping incidents aren't necessarily related.
HashiCorp Vault reported 15 incidents in the last 90 days, 8 of them major or critical. A typical incident lasted 2h 19m. See HashiCorp Vault's uptime and incident history