Skip to main content
HashiCorp logo

Is HashiCorp Down?

No — HashiCorp is up

Reachable from all 8 checked regions

Average response time: 542ms

Last checked · checks run every 6 hours

Official status page: https://status.hashicorp.com

HashiCorp uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
403ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 23 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

23-day clean streak
Aug 22: no data
Aug 23: no data
Aug 24: no data
Aug 25: no data
Aug 26: no data
Aug 27: no data
Aug 28: no data
Aug 29: 100.00% uptime, 24 checks
Aug 30: 100.00% uptime, 32 checks
Aug 31: 100.00% uptime, 32 checks
Sep 1: 100.00% uptime, 32 checks
Sep 2: 100.00% uptime, 32 checks
Sep 3: 100.00% uptime, 31 checks
Sep 4: 100.00% uptime, 21 checks
Sep 5: 100.00% uptime, 29 checks
Sep 6: 100.00% uptime, 32 checks
Sep 7: 100.00% uptime, 23 checks
Sep 8: 100.00% uptime, 38 checks
Sep 9: 100.00% uptime, 29 checks
Sep 10: 100.00% uptime, 37 checks
Sep 11: 100.00% uptime, 32 checks
Sep 12: 100.00% uptime, 32 checks
Sep 13: 100.00% uptime, 32 checks
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 31 checks
Sep 16: 100.00% uptime, 32 checks
Sep 17: 100.00% uptime, 32 checks
Sep 18: 100.00% uptime, 31 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 16 checks
Aug 22 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

arn
264ms
DNS 152ms TCP 1ms TLS 4ms TTFB 251ms
bom
2783ms
DNS 237ms TCP 289ms TLS 294ms TTFB 1309ms
cdg
130ms
DNS 63ms TCP 1ms TLS 5ms TTFB 119ms
dfw
242ms
DNS 140ms TCP 1ms TLS 3ms TTFB 221ms
ewr
249ms
DNS 148ms TCP 3ms TLS 11ms TTFB 223ms
fra
180ms
DNS 88ms TCP 5ms TLS 9ms TTFB 156ms
gru
261ms
DNS 168ms TCP 1ms TLS 6ms TTFB 247ms
iad
230ms
DNS 160ms TCP 2ms TLS 6ms TTFB 211ms

What HashiCorp does

HashiCorp builds infrastructure tooling: Terraform for provisioning, Vault for secrets, Consul for service networking, Boundary for access and Packer for image builds. Most are available both as software you run yourself and as managed services on the HashiCorp Cloud Platform. Its status page covers the hosted side, plus the Terraform Registry and the releases site that distributes binaries.

What an outage looks like

HCP Terraform runs queue without starting, or plans fail while fetching modules and providers from the Terraform Registry. Vault Dedicated and Consul Dedicated clusters become unreachable from the portal. A distinct failure is the Releases component: CI jobs that download HashiCorp binaries fail at that step even though running clusters and workloads are untouched.

What to do about it

Check status.hashicorp.com and find the specific product, since HCP Vault Dedicated and HCP Consul Dedicated each carry more than twenty components of their own. The page covers HashiCorp Cloud Platform services, the Terraform Registry, Vagrant Cloud and Releases. Keep a local mirror or cache of providers and binaries if registry and release fetches are what block your pipelines.

Is it down for everyone, or just you?

If this page says HashiCorp is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

AWS
AWS
GitHub
GitHub
Datadog
Datadog
DigitalOcean
DigitalOcean

HashiCorp outage FAQ

Is my self-managed Vault or Consul affected when HashiCorp is down?
HashiCorp's status page lists HCP products, the Terraform Registry, Vagrant Cloud and Releases. Software you run on your own infrastructure is not reported there, so an HCP incident tells you nothing about your own clusters either way. Diagnose self-managed installations from your own monitoring rather than from the vendor page.
My terraform plan fails downloading providers. Is HashiCorp down?
Check the Terraform Registry component, which is reported separately from HCP Terraform. Provider and module downloads come from the registry, so a registry incident breaks plans and applies everywhere, including on self-managed Terraform, while HCP Terraform workspaces may look fine. A local provider mirror removes this dependency for future runs.
Our CI cannot download the Terraform binary. Is that the same outage?
Possibly not. Releases is its own component, covering the site that distributes HashiCorp binaries, and it carries several sub-components. A Releases incident breaks any pipeline step that fetches a binary at build time while your running Vault, Consul and Terraform workloads continue untouched. Caching binaries in your own artifact store avoids it.
Why does HCP Terraform work while HCP Vault is down?
They are separate services with separate status components. HashiCorp lists HCP Portal, HCP API, HCP Boundary, HCP Consul Dedicated, HCP Infragraph, HCP Packer, HCP Vault Dedicated, HCP Vault Radar, HCP Waypoint and HCP Terraform individually. Incidents are routinely scoped to one product, so read the row for the service you actually use.
How granular is HashiCorp's status page?
More granular than the summary suggests. HCP Vault Dedicated is reported across twenty-three components and HCP Consul Dedicated across twenty-two, with Infragraph and Releases carrying their own sub-components. An all-clear banner can sit above a single failing sub-component, so expand the product you depend on rather than trusting the headline.

How we measure this

  • We request HashiCorp's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where HashiCorp publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when HashiCorp goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required