HCP Terraform – Elevated 502 Bad Gateway Errors
HCP Terraform shows elevated 502 Bad Gateway errors. Some customers cannot access the service or run Terraform operations. HashiCorp is investigating the issue.
State
Investigating
Started
Ongoing for
34 min
Worst impact
Degraded
Timeline
1 updateInvestigating
34 min 100%
Updates
Times in UTCAs posted by HashiCorp
We are aware of and investigating reports of degraded performance. **Current impact state:** Customers are experiencing 502 Bad Gateway errors while accessing HCP Terraform. Some customers may be unable to access the service or execute Terraform operations. **Action underway:** Our team is actively investigating the issue to identify the root cause and restore normal service functionality. **Next update time:** 09:07 UTC (in one hour).
HashiCorp in the last 90 days
Full historyIncidents in 90 days
12
Days with an incident
20
Median duration
2 h 45 min
This incident
79% shorter than the median
Other HashiCorp incidents
All incidentsHashiCorp·GitHub and Other VCS workloads experiencing intermittent issues
Today we released tfc-agent 1.33.3 to address the root cause of the failures we saw yesterday. A recent security patch to libcurl exposed a bug in the version of git we ship in the tfc-agent image. This causes some VCS setups to fail when the VCS provider issues an HTTP redirect. We've patched the bug in git. If you are using remote runs, you don't have to do anything, you're already on 1.33.3. If you downgraded to 1.33.1 to work around git-based VCS problems, you can safely upgrade to 1.33.3 now. Please contact support if you experience any further issues.
HashiCorp·Terraform Runs Failing
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.
HashiCorp·HCP Vault Azure: Cluster Updates and Creation
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.
HashiCorp·Users unable to access releases.hashicorp.con
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.
HashiCorp·HCP Terraform Returning 404s
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.
Follow HashiCorp
Your coding agent knows when HashiCorp is down, and tells you when a failure is theirs, not yours. You can also get HashiCorp incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "hashicorp" and tell me if HashiCorp has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=hashicorp/feed subscribe https://outages.live/feed.xml?providers=hashicorpFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane