rewindex

CompaniesHashiCorpIncidents

HashiCorp: Some of HCP Boundary Clusters might be seeing degraded performance.

MinorStatus: resolvededitedStarted Resolved (2.7 h)6 updatesstatus.hashicorp.com (opens in new tab)

Affected components: HCP Boundary

Timeline of updates

  1. investigating

    We are aware of and investigating reports of degraded performance.

    Current impact state: Some of HCP Boundary Clusters might be seeing degraded performance.

    Action underway: Team is investigating the incident.

    Next update time: 1930 UTC

  2. investigating

    We are aware of and investigating reports of degraded performance.

    Current impact state: Some HCP Boundary Clusters may experience degraded performance.

    Action underway: Team is continuing to investigate the incident.

    Next update time: 2030 UTC

  3. investigating

    We are aware of and investigating reports of degraded performance.

    Current impact state: Few customers might see intermittent issues while login to Boundary console. The team has identified the cause for failure and trying to capture more details to confirm the issue.

    Action underway: Further investigation is continued

    Next update time: (Always use UTC)

  4. identifiedEdited

    Our Engineering team has identified the cause and we are actively working on a fix.

  5. monitoring

    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.

  6. resolved

    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.

Changes Rewindex caught on this incident

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

Rewindex captured this after the last checkpoint; the next run () commits it.

Impact, status and times are the vendor’s own, as last archived. View on status.hashicorp.com (opens in new tab).

Cite this

Status incident (vendor impact label: minor) posted by HashiCorp, started 2026-11-15 19:12 UTC, resolved after 2.7 h, 6 update(s); edited after publishing.

Title
Some of HCP Boundary Clusters might be seeing degraded performance.
Vendor
HashiCorp
Date
URL
https://rewindex.com/company/hashicorp/incidents/01M7GA12JE61D4EA96YY5HNA0H

HashiCorp profileRecent HashiCorp incidentsAll outages on November 15, 2026HashiCorp in November 2026MarkdownJSON