HCP Boundary Scheduled Maintenance
This maintenance is scheduled for routine infrastructure upgrades and software version updates. We expect this maintenance to complete in under 2 hours. Customers may experience service unavailability for the small duration during scheduled maintenance. Services will be restored upon completion of the maintenance activities. Updates will be posted as necessary throughout the maintenance period.
The latest update from HashiCorp.
State
Scheduled
Started
Ongoing for
12 h 26 min
Worst impact
Maintenance
Timeline
1 updateScheduled
12 h 26 min 100%
Updates
Times in UTCAs posted by HashiCorp
This maintenance is scheduled for routine infrastructure upgrades and software version updates. We expect this maintenance to complete in under 2 hours. Customers may experience service unavailability for the small duration during scheduled maintenance. Services will be restored upon completion of the maintenance activities. Updates will be posted as necessary throughout the maintenance period.
HashiCorp in the last 90 days
Full historyIncidents in 90 days
15
Days with an incident
19
Median duration
2 h 19 min
This incident
Not comparable
Other HashiCorp incidents
All incidentsHashiCorp·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.
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.
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