Looking for an update now? Check the current status, or follow Harness for future changes.
62.5%of 56 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
55.2%
29
13
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 23Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Infrastructure as Code Management (IaCM)Infrastructure as Code Management (IaCM)Infrastructure as Code Management (IaCM)Infrastructure as Code Management (IaCM)
monitoring
We have reverted the change that caused this issue in all clusters.
investigating
We are continuing to investigate this issue.
investigating
We are currently investigating an issue reported in IACM pipelines in Prod-1 , Prod-2 ,Prod-4 and EU1 harness clusters.
Legacy Incident Archive
88 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
We are continuing to monitor for any further issues.
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
We are currently investigating this issue.
CI degradation with CI steps using AWS connector with inherited authentication
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are investigating a degradation in CI steps when using AWS connectors and inherited authentication.
March 2026
Feature Flag SDK authentication operations are running slow in Prod2
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are continuing to monitor for any further issues.
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
We are currently investigating this issue.
Degraded Performance for SCIM users during login.
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The issue has been identified and a fix is in place.
monitoring
The issue has been identified and a fix is in place. (Note: It is still in a degraded state)
investigating
The issue has been identified and a fix is in place.
Test Intelligence service is impacted in Prod1
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
We are currently investigating this issue.
FME SDK is experiencing elevated error rates for Impressions and events
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are now monitoring the results.
investigating
The issue started around ~6:45AM PT and the team is currently investigating
Degraded performance in CI Steps in Prod 2 and Prod 3
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
We are noticing degraded performance in CI Steps in Prod 2 and Prod 3 environments
The issue is intermittent. We are investigating the cause
Prod 2 - Customers may see some executions from March 11 in a "running" but hung state
Source not attested
Last archived state: resolved
View archived record details
identified
The issue has been identified and a fix is being implemented.
investigating
Customers may continue to see that some pipeline executions show that they are "running" even though they have completed, aborted, or failed as a result of yesterday's incident. (https://status.harness.io/incidents/4y4dl47v2qhc)
This behavior is a UI-only artifact from the incident and should not affect customers' ability to start new executions. We are working on clearing these artifacts.
