Vendor record
HashiCorp
Checked
Front door check counts and HashiCorp’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.
Front door checks
We send a request to a documented HashiCorp endpoint and count the checks that got the answer it is documented to give.
Front door reachable in 2,855 of 2,877 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.
2 more checks gave no clear answer and are not counted.
- Endpoint checked
- api.releases.hashicorp.com
- Scope
- releasesNo vendor region
- First check in this window
- Latest clear answer
Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every HashiCorp product, region or your app worked.
How we count front door checksHashiCorp says
Incident posts from HashiCorp’s status page, with its titles, impact levels and times. They say what HashiCorp chose to post, not what reached your app.
A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.
2
incidents HashiCorp posted, last 7 days
Most recent records · all dates
HCP Terraform Scheduled Maintenance (2026-11-14)
Not specifiedFirst seen by CheckUpstream
Closed in our record
Terraform Runs Failing
Not specifiedStarted, per HashiCorp
Closed in our record(28m)
HCP Vault Azure: Cluster Updates and Creation
Not specifiedStarted, per HashiCorp
Closed in our record(5d 6h)
Users unable to access releases.hashicorp.con
MajorHashiCorp’s postStarted, per HashiCorp
Closed in our record(57m)
HCP Terraform Returning 404s
CriticalHashiCorp’s postStarted, per HashiCorp
Closed in our record(2h 18m)
13 older records
Hashicorp Linux packages GPG key rotation
MajorHashiCorp’s postStarted, per HashiCorp
Closed in our record(7h 16m)
Errors creating new VCS workspaces with Bitbucket cloud provider
MinorHashiCorp’s postStarted, per HashiCorp
Closed in our record(3h 54m)
Delayed HCP Terraform Runs
MinorHashiCorp’s postStarted, per HashiCorp
Closed in our record(2d 19h)
Terraform AWS Provider v6.59.0 — errors during plan for aws_network_acl_rule resources
MinorHashiCorp’s postStarted, per HashiCorp
Closed in our record(1h 15m)
Issues When Downloading Terraform Providers
MinorHashiCorp’s postStarted, per HashiCorp
Closed in our record(1h 45m)
DR Cluster Creation Failures
Not specifiedHashiCorp’s postStarted, per HashiCorp
Closed in our record(2h 40m)
Infragraph Snapshot are stuck
MajorHashiCorp’s postStarted, per HashiCorp
Closed in our record(1h 58m)
HCP Terraform is unable to communicate with VCS endpoints using certain IP addresses.
MinorHashiCorp’s postStarted, per HashiCorp
Closed in our record(1d 1h)
Infragraph Service and UI down
CriticalHashiCorp’s postStarted, per HashiCorp
Closed in our record(27m)
HCP Terraform UI Not Loading
MajorHashiCorp’s postStarted, per HashiCorp
Closed in our record(1h 54m)
app.terraform.io is not loading
MajorHashiCorp’s postStarted, per HashiCorp
Closed in our record(2h 20m)
HCP Terraform Workspace Runs Failing with IAM Errors After AWS Provider Upgrade
MajorHashiCorp’s postStarted, per HashiCorp
Closed in our record(8h 7m)
Increased Load Times for HCP Portal
Not specifiedHashiCorp’s postStarted, per HashiCorp
Closed in our record(15h 41m)
Your code, your dependencies
See which of your code paths call HashiCorp
Connect GitHub or GitLab to find where your public or private repository uses HashiCorp. Review each match and your alert settings.
Free to start. No credit card.
Use this record on your site
Add HashiCorp status to your page.
Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.
Frequently Asked Questions
Is HashiCorp currently down?
HashiCorp's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.
When did HashiCorp last have an outage?
The most recent closed incident record began earlier today and spans 2h 40m. The vendor reported an incident. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.
Does CheckUpstream publish an uptime percentage for HashiCorp?
No. CheckUpstream checks HashiCorp’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.
How do I monitor HashiCorp in production?
Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.
How does CheckUpstream track HashiCorp?
This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.