CheckUpstream measured HashiCorp at 99.538% availability across 2814 independent checks (global · releases). 13 incidents were recorded in the past 12 months; the most recent resolved 16 days ago after 3 days. Status signals are polled from HashiCorp's official Atlassian Statuspage status page, alongside independent probes and community reports.
30 days measured availability how this is computed
99.538%
global · releases · n=2814 · p95 521ms (30d)
Share of our own checks against HashiCorp endpoints that returned HashiCorp's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
Vendor disclosed: 8 incidents · 21 of 30 days with none posted · 1d 16h of declared impact
Fewer incidents in the last 30 days than 11% of 232 tracked services.
Share of each window with no impact declared by HashiCorp
7d
100.000%
30d
94.336%
90d
97.753%
180d
98.877%
1y
99.446%
Downtime like this can be refundable
If you're a paying HashiCorp customer, outages in these windows may count against HashiCorp's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
Track your HashiCorp entitlement →Does HashiCorp actually matter to you?
A HashiCorp outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →From 8 incidents HashiCorp published and resolved in the last 30 days, measured between their own start and resolution times. It describes how long HashiCorp takes to close an incident they have acknowledged — not how often they have them, and not how available they were.
Aug 15, 17:08 UTC · resolved in 2d 19h · Resolved
Aug 13, 17:50 UTC · resolved in 1h 19m · Resolved
Aug 12, 21:45 UTC · resolved in 1h 30m · Resolved
Aug 6, 08:40 UTC · resolved in 11h 59m · Resolved
Live HashiCorp status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/hashicorp)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
HashiCorp is currently Operational. CheckUpstream tracks HashiCorp in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
HashiCorp's last resolved incident started 16 days ago and lasted 2d 19h (degraded performance).
Looking for the live "is HashiCorp down" view? See the HashiCorp Live status page.
Aug 5, 20:09 UTC · resolved in 1d · Resolved
Aug 5, 19:08 UTC · resolved in 1d 1h · Resolved
Aug 5, 15:11 UTC · resolved in 28m · Resolved
Aug 5, 00:05 UTC · resolved in 1h 55m · Resolved
Jul 30, 23:06 UTC · resolved in 2h 29m · Resolved
Jul 29, 12:56 UTC · resolved in 7h 49m · Resolved
Jul 29, 00:09 UTC · resolved in 21m · Resolved
Jul 28, 17:13 UTC · resolved in 36m · Resolved
HashiCorp's 30-day measured availability is 99.538%, from CheckUpstream's own probes against HashiCorp endpoints. It is the share of checks that returned the expected response, not a figure taken from HashiCorp's status page.
Sign up to CheckUpstream and add HashiCorp to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll HashiCorp's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.