Temporary limitations for users on Free Subscription
HashiCorp reports temporary limitations for free subscription users. These users cannot create new organizations, and some may have trouble with runs. Paid subscription users are not affected. HashiCorp implemented a fix and is monitoring the situation.
State
Monitoring
Started
Ongoing for
29 h 53 min
Worst impact
Degraded
Timeline
2 updatesMonitoring
29 h 53 min 100%
Updates
Times in UTCAs posted by HashiCorp
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.
Users on free subscription are temporarily unable to create new organizations. Some of these users may have trouble with runs. Users on paid subscription are not affected.
HashiCorp in the last 90 days
Full historyIncidents in 90 days
18
Days with an incident
22
Median duration
2 h 31 min
This incident
12× the median
Other HashiCorp incidents
All incidentsHashiCorp·New email and password account creation is no longer supported
New email and password account creation is unavailable on HashiCorp Cloud Platform (HCP). Existing users can still sign in and access HCP services. HashiCorp implemented a fix and is monitoring the situation.
HashiCorp·Elevated Errors in HCP Terraform
HCP Terraform users saw elevated errors in the HCP Terraform User Interface and the HCP Terraform API. HashiCorp reports that the incident is resolved and that the outage lasted about 4 hours and 25 minutes.
HashiCorp·HCP Terraform - Elevated error rates and latency
HCP Terraform had errors and increased latency in the Terraform runs and the HCP Terraform UI. HashiCorp reports that the incident is resolved and that it lasted 88 minutes.
HashiCorp·Remote Terraform runs failing
Remote Terraform runs queue or start slowly on HashiCorp remote execution. HashiCorp reports that this issue is resolved. The outage lasted about 2 hours.
HashiCorp·Some of HCP Boundary Clusters might be seeing degraded performance.
Some HCP Boundary Clusters had degraded performance. A few customers had intermittent problems when they logged in to the Boundary console. HashiCorp reports that the issue is resolved and that it lasted 2 hours and 43 minutes.
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