HYOK, Private VCS, and Private Run Tasks returning 403 errors
HashiCorp reports that requests through the tfc-agent return 403 errors. This affected HYOK, Private VCS, and Private Run Tasks. HashiCorp later reported that the service resumed 403 errors, and the team investigates again.
State
Resolved
Started
Lasted
36 min
Worst impact
Partial outage
Timeline
5 updatesInvestigating
28 min 76%
Identified
9 min 24%
Updates
Times in UTCAs posted by HashiCorp
After a brief recovery the service has resumed emitting 403 errors at a high rate. Our engineering team is investigating. **Next update time**: 04:30 UTC
Our Engineering team has resolved the issue. The previous fix was incomplete and rolled back by a legacy deployment process, but the fix is now permanently rolled out. If you continue to experience issues, please contact support.
Our Engineering team has resolved the issue. All systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team.
Our Engineering team has identified the cause and we are actively working on a fix. **Action underway**: Restoring service. **Next update time**: 04:10 UTC
We are aware of elevated 403 errors being returned when requests are forwarded through the tfc-agent. This may impact HYOK, Private VCS, and Private Run Tasks. **Action underway**: Our engineers are investigating the cause now. **Next update time**: 03:55 UTC
HashiCorp in the last 90 days
Full historyIncidents in 90 days
12
Days with an incident
18
Median duration
2 h 32 min
This incident
76% shorter than the median
Other HashiCorp incidents
All incidentsHashiCorp·HCP Boundary Scheduled Maintenance
HCP Boundary service availability may be affected during scheduled maintenance on Saturday November 14th 2026, starting at 2:00 PM UTC. HashiCorp expects the work to take under 2 hours. The incident is resolved because the notice was posted for a future date.
HashiCorp·HCP Terraform – Elevated 502 Bad Gateway Errors
HCP Terraform had 502 Bad Gateway errors that caused degraded performance for some customers. HashiCorp reports that the issue is resolved. The outage lasted about 111 minutes, from 08:13 to 10:04 UTC on 5 November 2026.
HashiCorp·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.
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