CHYP.ai · ORBIT // Cloudy_Day Security Suite

Developer tools

Degraded / minor incident HashiCorp Cloud status

hashicorp.com · Official status page (Statuspage-compatible JSON)

FROM ALL SOURCES

HashiCorp Cloud's status page shows “Degraded / minor incident”; the vendor is resolved. User reports haven't spiked, so wide impact isn't visible yet.

confidence: low Vendor: minor issue · users: normal · routing: no data.

Vendor status vs. reality: Vendor reports an issue we don't see in crowd or routing data (it may be partial or internal)
The four clocks
ClockStartedRunning
Vendor clock when the vendor's open incident started30 days
Crowd clock when user reports began rising above normalnot seenn/a
Network clock when routing anomaly data first flagged itnot seenn/a
ORBIT clock when our checker first recorded the change2 h 23 min

Evidence

  • Official page: Degraded / minor incident (“All Systems Operational”). evidence confidence: high
  • Vendor stage: resolved on “GitHub and Other VCS workloads experiencing intermittent issues”. evidence confidence: high
  • User reports are within normal range (0 in 15 min). evidence confidence: low

What we don't know: what is happening inside HashiCorp Cloud's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp, providers it may run on (inferred). Routing data shows reachability, not whether the app works.

Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .

Cloudy_Day's take

Stage vs. health

The vendor's stage is “resolved”. Stage tells you where they are in their process; health is what users experience. Right now vendor: minor issue · users: normal · routing: no data. Vendor reports an issue we don't see in crowd or routing data (it may be partial or internal).

Who depends on whom

We don't map other services that depend on HashiCorp Cloud. Dependency chains are where single points of failure hide.

Identity & trust lens

Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.

For users

Check the official status page before changing settings or reinstalling. If you must act, use known-good bookmarks. Reporting what's broken on ORBIT helps everyone see the real footprint.

For security teams

Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on HashiCorp Cloud, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).

What to watch next

The vendor stage moving to “monitoring”, then “resolved”; the user-report curve falling back under baseline; and whether dependents start reporting issues.

Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with HashiCorp Cloud. No blame or attack claims without an official source. Generated .

INCIDENT REPLAY

GitHub and Other VCS workloads experiencing intermittent issues

major resolved · started · resolved

10 updates

  1. identified

    [GitHub.com](http://GitHub.com "GitHub.com") has acknowledged an issue causing intermittent issues accessing their API. This may cause VCS-based Terraform workloads to malfunction. We are monitoring GitHub status and will update this issue as we learn more. **Current impact state**: VCS workloads experiencing intermittent issues. **Action underway**: Awaiting word from [GitHub.com](http://GitHub.com "GitHub.com") **Next update time**: 17:30 UTC

  2. investigating

    We are continuing to receive reports of intermittent issues with VCS workloads, some of which are not hosted on [GitHub.com](http://GitHub.com "GitHub.com"). Our engineering team is investigating these issues. **Current impact state**: VCS workloads experiencing intermittent issues. **Action underway**: Awaiting word from [GitHub.com](http://GitHub.com "GitHub.com") **Next update time**: 18:00 UTC

  3. investigating

    Our engineering is continuing to investigate intermittent VCS-related failures. **Current impact state**: VCS related workloads experiencing intermittent issues. **Action underway**: Engineering team investigating. **Next update time**: 18:30 UTC

  4. monitoring

    Our engineers are no longer able to reproduce the issue and error counts have dropped off. We will continue to monitor for any further issues. If you experience any further problems please reach out to support. **Current impact state**: System in recovery. **Action underway**: Monitoring. **Next update time**: 19:00 UTC

  5. investigating

    Intermittent and some persistent VCS issues have been reproduced on some workspaces. Our engineering team is continuing to investigate. **Current impact state**: Intermittent issues on VCS workspaces are continuing to be observed. **Action underway**: Engineering team is working on reliably reproducing the issue. **Next update time**: 19:00 UTC

  6. identified

    Our engineering team has identified the tfc-agent release v1.33.2 as the cause of intermittent issues with VCS providers. We have downgraded the version to 1.33.1 for remote runs. If you are experiencing issues with self-hosted agents please downgrade to 1.33.1 until a new release is made to address the issue. **Current impact state**: Remote runs fully-functional. Affected self-hosted agents need to downgrade to tfc-agent version 1.33.1. Stacks users may experience a regression when using proxies with version 1.33.1. **Action underway**: Releasing a fixed tfc-agent version. **Next update time**: 19:45 UTC

  7. monitoring

    Downgrading tfc-agent to 1.33.1 has proven effective in eliminating the intermittent VCS failures. We will continue to monitor for any further impacts. A new release with a fix is in-progress and expected within 24 hours. If you are not affected, do not downgrade. If you experience further issues please contact support.

  8. resolved

    VCS connection issues should be mitigated by downgrading to tfc-agent 1.33.2. Our engineering team is still investigating the cause of this failure. If you do not have any VCS connection problems you do not need to downgrade to 1.33.1. We will release a new version of tfc-agent in the next 24 hours to fix the root cause.

  9. resolved

    One minor correction, VCS connection issues can be mitigated by downgrading tfc-agent from 1.33.2 to 1.33.1.

  10. resolved

    Today we released tfc-agent 1.33.3 to address the root cause of the failures we saw yesterday. A recent security patch to libcurl exposed a bug in the version of git we ship in the tfc-agent image. This causes some VCS setups to fail when the VCS provider issues an HTTP redirect. We've patched the bug in git. If you are using remote runs, you don't have to do anything, you're already on 1.33.3. If you downgraded to 1.33.1 to work around git-based VCS problems, you can safely upgrade to 1.33.3 now. Please contact support if you experience any further issues.

Official incident page ↗

Community comments (0)

Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.

No approved comments yet.

How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.

Where to next