CHYP.ai · ORBIT // Cloudy_Day Security Suite

Developer tools

Operational Harness status

harness.io · Official status page (Statuspage-compatible JSON)

FROM ALL SOURCES

No sign of a widespread Harness problem right now; every source we read is quiet.

confidence: medium Vendor: operational · users: normal · routing: no data.

Vendor status vs. reality: Vendor status and outside signals roughly agree

Regions mentioned: Platform

The four clocks
ClockStartedRunning
Vendor clock when the vendor's open incident started52 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 changenot seenn/a

Evidence

  • Official page: Operational (“All Systems Operational”). evidence confidence: high
  • Vendor stage: postmortem on “SSO login failures for the published Harness Okta application”. 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 Harness' 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 “postmortem”. Stage tells you where they are in their process; health is what users experience. Right now vendor: operational · users: normal · routing: no data. Vendor status and outside signals roughly agree.

Who depends on whom

We don't map other services that depend on Harness. 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

Nothing points to a broad problem. If it's broken for you, try “Is it just me?” and check your own network first.

For security teams

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

What to watch next

Any new vendor incident, a jump in user reports above baseline, or trouble at the providers Harness may depend on.

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

INCIDENT REPLAY

SSO login failures for the published Harness Okta application

none postmortem · started · resolved

6 updates

  1. investigating

    We are currently investigating this issue.

  2. identified

    The issue has been identified and a fix is being implemented.

  3. identified

    We identified an issue that applies only to SP-initiated login through the published Harness Okta application. After a recent update to that application, those login attempts returned an HTTP 400 error when the configured SSO URL was missing from Additional ACS URLs. General SAML 2.0 configurations in Okta are not affected. Immediate Solutions: Use IDP-initiated login. Start the login from the Harness application tile in Okta. Or Add your Harness SSO URL to Additional ACS URLs in the published Harness Okta application.

  4. identified

    We identified an issue that applies only to SP-initiated login through the published Harness Okta application. After a recent update to that application, those login attempts returned an HTTP 400 error when the configured SSO URL was missing from Additional ACS URLs. General SAML 2.0 configurations in Okta are not affected. Immediate Solutions: Use IDP-initiated login. Start the login from the Harness application tile in Okta. Or Add your Harness SSO URL to Additional ACS URLs in the published Harness Okta application.

  5. resolved

    This incident has been resolved.

  6. postmortem

    # 1. Summary Starting September 29, 2026, customers who sign in to Harness through the published Harness application in the Okta Integration Network \(OIN\) were unable to complete SP-initiated SSO login. Affected users received an HTTP 400 error from Okta instead of being signed in. The issue was introduced by a change in how Okta validated the requested reply \(ACS\) URL for existing installations of the published Harness application. Workarounds were published within an hour of the first report, and every affected customer was unblocked. # 2. Impact ‌ * Impact was limited to customers using the published Harness application from the Okta Integration Network for SP-initiated login \(starting sign-in from Harness\). Those attempts returned an HTTP 400 error from Okta. * IdP-initiated login, started from the Harness tile in Okta, continued to work throughout. * Customers using their own

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