Live / HashiCorp / Incident
HashiCorp: Some of HCP Boundary Clusters might be seeing degraded performance.
HashiCorp · hashicorp.comMinor incidentResolved2026-11-15 21:56 UTC
Public — what happened
Summary
HashiCorp said some HCP Boundary clusters might be running slower than normal, starting around 19:12 UTC on 2026-11-15. Later in the incident it said a few customers could see intermittent problems when logging in to the Boundary console. By 20:56 UTC the company said its engineers had found the cause and were working on a fix, and at 21:28 UTC it said a fix was in place and being watched. The incident was marked resolved at 21:56 UTC.
Timeline
- Started — 2026-11-15 19:12 UTC
- Investigating — 2026-11-15 19:13 UTC (3 updates)
- Identified — 2026-11-15 20:56 UTC
- Monitoring — 2026-11-15 21:28 UTC
- Resolved — 2026-11-15 21:56 UTC · 2h 43m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach HashiCorp against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for HashiCorp: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the HashiCorp report →
More from HashiCorp
Covered in The Squid’s Ink, Week 47, 2026, our weekly internet health report.