Skip to content

Incident detail

Terraform Runs Failing to Fetch GitHub Sources Over SSH

Resolved incidentMinor

Timeline window

to

Get alerted the next time HashiCorp Cloud breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Timeline

Incident updates

Every update HashiCorp Cloud posted, oldest to newest, exactly as it appeared on their official status page.

  1. Investigating

    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 `git@github.com:` 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.

  2. 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.

  3. 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.

  4. Resolved

    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.

Keep exploring

More from HashiCorp Cloud

Neighboring incidents on HashiCorp Cloud's timeline and the rest of their record on OutageDeck.