HashiCorp outage, 5 November 2026

HCP Terraform - Elevated 502 Bad Gateway Errors

Started
Resolved
5 Nov 2026, 10:04 UTC (after 1 h 51 min)
Impact
Minor

Is this still happening?

No. HashiCorp marked this incident resolved on 5 Nov 2026, 10:04 UTC, 1 h 51 min after it began.

Right now: HashiCorp reports all systems operational. (as of 5 Nov, 14:45 UTC) Live HashiCorp status

Last update from HashiCorp

Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team.

5 Nov 2026, 10:04 UTC

Similar HashiCorp incidents

Earlier incidents with the same affected part or wording - useful to see how long this kind of problem usually takes.

  1. , resolved after 8 h 7 min

    HCP Terraform Workspace Runs Failing with IAM Errors After AWS Provider Upgrade

  2. , still open

    HCP Terraform Scheduled Maintenance (2026-11-14)

  3. , resolved after 2 h 18 min

    HCP Terraform Returning 404s

  4. , resolved after 2 days

    Delayed HCP Terraform Runs

  5. , resolved after 1 h 15 min

    Terraform AWS Provider v6.59.0 - errors during plan for aws_network_acl_rule resources

Other recent HashiCorp incidents

  1. GitHub and Other VCS workloads experiencing intermittent issuesPostmortem

  2. Terraform Runs Failing

  3. HCP Vault Azure: Cluster Updates and Creation

  4. Users unable to access releases.hashicorp.con

  5. Degraded commit/content scans in HCP Vault Radar

  6. Hashicorp Linux packages GPG key rotation

  7. Errors creating new VCS workspaces with Bitbucket cloud provider

  8. Issues When Downloading Terraform Providers

All recorded HashiCorp incidents