HCP Scheduled Maintenance
Maintenance has started. This maintenance will include rolling restarts of a back-end service affecting certain workflows for HCP Boundary, HCP Vault, Billing, and HCP Terraform synchronization with HCP. Customer Boundary and Vault clusters already running will continue normally. New cluster creation & deletion may timeout or be delayed during the maintenance window. Existing HCP Terraform organizations and runs will continue normally. Synchronization of new or changed organizations, projects, users, groups, access policies, and SSO settings from HCP may be delayed. Calculation of up to date cloud usage will be delayed. All other billing information and operations will still be accessible as usual via the portal.
The latest update from HashiCorp.
State
In progress
Started
Ongoing for
18 h 59 min
Worst impact
Maintenance
Timeline
3 updatesScheduled
16 h 11 min 85%
In progress
2 h 49 min 15%
Updates
Times in UTCAs posted by HashiCorp
Maintenance has started. This maintenance will include rolling restarts of a back-end service affecting certain workflows for HCP Boundary, HCP Vault, Billing, and HCP Terraform synchronization with HCP. Customer Boundary and Vault clusters already running will continue normally. New cluster creation & deletion may timeout or be delayed during the maintenance window. Existing HCP Terraform organizations and runs will continue normally. Synchronization of new or changed organizations, projects, users, groups, access policies, and SSO settings from HCP may be delayed. Calculation of up to date cloud usage will be delayed. All other billing information and operations will still be accessible as usual via the portal.
Maintenance has started
HCP services will undergo scheduled maintenance on Wednesday, November 18th 2026 beginning at 12:00 UTC through 17:00 UTC. This maintenance will include rolling restarts of a back-end service affecting certain workflows for HCP Boundary, HCP Vault, Billing, and HCP Terraform synchronization with HCP. Customer Boundary and Vault clusters already running will continue normally. New cluster creation & deletion may timeout or be delayed during the maintenance window. Existing HCP Terraform organizations and runs will continue normally. Synchronization of new or changed organizations, projects, users, groups, access policies, and SSO settings from HCP may be delayed. Calculation of up to date cloud usage will be delayed. All other billing information and operations will still be accessible as usual via the portal.
HashiCorp in the last 90 days
Full historyIncidents in 90 days
14
Days with an incident
18
Median duration
2 h 31 min
This incident
Not comparable
Other HashiCorp incidents
All incidentsHashiCorp·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.
HashiCorp·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.
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