Infragraph Service and UI down
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.
The latest update from HashiCorp.
State
Resolved
Started
88 d ago
2026-08-05 15:11 UTC
Lasted
27 min
until 2026-08-05 15:39 UTC
Worst impact
Major outage
Timeline
3 updatesInvestigating
17 min 60%
Monitoring
11 min 40%
Updates
Times in UTCAs posted by 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.
Our Engineering team has implemented a fix to resolve the issue. We are monitoring the situation closely and will post an update as soon as the issue is fully resolved.
We are aware of and investigating reports of degraded performance. Our team is working to identify and resolve the issue. We will post updates with more information as it becomes available.
HashiCorp in the last 90 days
Full historyIncidents in 90 days
16
Days with an incident
21
Median duration
2 h 29 min
This incident
82% 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.cc/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.cc/feed.xml?providers=hashicorp/feed subscribe https://outages.cc/feed.xml?providers=hashicorpFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane