Some of HCP Boundary Clusters might be seeing degraded performance.
Some HCP Boundary clusters may have degraded performance. HashiCorp reports that the incident is under investigation.
State
Investigating
Started
Ongoing for
36 min
Worst impact
Degraded
Timeline
3 updatesInvestigating
36 min 100%
Updates
Times in UTCAs posted by HashiCorp
We are aware of and investigating reports of degraded performance. **Current impact state**: Some HCP Boundary Clusters may experience degraded performance. **Action underway**: Team is continuing to investigate the incident. **Next update time**: 2030 UTC
We are aware of and investigating reports of degraded performance. **Current impact state**: Some of HCP Boundary Clusters might be seeing degraded performance. **Action underway**: Team is investigating the incident. **Next update time**: 1930 UTC
We are aware of and investigating reports of degraded performance. **Current impact state**: Some of HCP Boundary Clusters might be seeing degraded performance. **Action underway**: Team is investigating the incident. **Next update time**: (Always use UTC)
HashiCorp in the last 90 days
Full historyIncidents in 90 days
14
Days with an incident
18
Median duration
2 h 45 min
This incident
78% shorter than the median
Other HashiCorp incidents
All incidentsHashiCorp·Emergency Maintenance Notification – HCP Radar
Emergency maintenance on the HCP Radar service caused brief unavailability of billing, metering, and onboarding agent flows. HashiCorp reports that the maintenance is resolved and all services operate normally. The outage lasted about 6 hours and 5 minutes.
HashiCorp·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.
HashiCorp·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.
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