HashiCorp Uptime History
Measured by PulsAPI's own checks, not reported by HashiCorp. Every figure below is computed over the 95 days in the last 365 that PulsAPI actually observed, from 2026-05-22 to 2026-08-24. Days nobody watched are left out rather than counted as perfect.
HashiCorp Uptime at a Glance
- Measured uptime
- 98.60%
- Days with an issue
- 9
- Longest outage
- 132d 23h
- Mean recovery
- 6d 20h
across 95 observed days
days were not fully operational
single longest resolved incident
average time to resolve
Monthly HashiCorp Uptime
Each month is the mean of its observed days. The strongest month was May 2026 at 100.00%, the weakest June 2026 at 95.68%. Months with few observed days are marked, because a short month is not evidence of a good one.
| Month | Uptime | Uptime bar | Days observed |
|---|---|---|---|
| August 2026 | 99.95% | 24 | |
| July 2026 | 99.92% | 31 | |
| June 2026 | 95.68% | 30 | |
| May 2026 | 100.00% | 10partial |
How This HashiCorp Uptime Figure Is Measured
PulsAPI checks HashiCorp every 60 seconds and records the result. A day's uptime is the share of that day's checks that came back fully operational, so a 20-minute outage shows up as a dip rather than being rounded away. The window figure is the mean of those daily values.
Two things this deliberately is not. It is not HashiCorp's own published uptime, because vendors generally measure against their own SLA definitions, which usually exclude scheduled maintenance and often exclude partial degradation. And it is not a promise about the future: 95 days of history describes what happened, and the useful way to read it is alongside the incidents behind the dips.
Uptime measured this way is a mean of component uptimes where a vendor publishes components, so coverage matters as much as the percentage. That is why the observed-day count sits beside every figure on this page rather than in a footnote.
These measurements are published under CC BY 4.0. Quote or republish them freely, with attribution to PulsAPI.