Live

HCP Boundary Scheduled Maintenance

MaintenanceOfficial update

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 update
15:5519:0222:0801:1504:21
MaintenanceUpdate postedTimes in UTC

Scheduled

12 h 26 min 100%

Updates

Times in UTC

As posted by HashiCorp

Scheduled

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 history
90 days agoToday

Incidents in 90 days

15

Days with an incident

19

Median duration

2 h 19 min

This incident

Not comparable

How long each incident lasted, on the day it started. The outlined bar is this incident.

5 days
median 2 h 19 min
90 days agoToday

Other HashiCorp incidents

All incidents

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.

Prompt
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.

RSS
https://outages.live/feed.xml?providers=hashicorp
Slack
/feed subscribe https://outages.live/feed.xml?providers=hashicorp

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane