Harness Status: check for Harness outages and issues

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Harness Prod 0

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Harness Prod 1

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Continuous Delivery (CD) - FirstGen - EOS

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Slowness in Prod1 and Prod2 environment

Started 8 Sep 2026 21:52:48 (6 days ago), resolved 9 Sep 2026 04:30:49 (5 days ago)

Minor Incident

Postmortem

Continuous Delivery (CD) - FirstGen - EOS

Continuous Delivery - Next Generation (CDNG)

Cloud Cost Management (CCM)

More...

We are currently investigating this issue.

Postmortem: ### Summary

On September 8, 2026, customers in Prod 1 and Prod 2 experienced elevated platform latency and pipeline failures. The issue was caused by a regression in a newly released capability that triggered cascading failures under high load. Because the capability was behind a feature flag, it was quickly disabled, and service was restored after a brief monitoring period.

Customer Impact

Customers encountered slowness and failures during pipeline execution and UI operations. Some API calls returned errors or timed out.
No data loss or corruption occurred.

Root Cause

The new capability introduced a regression that created contention on a shared backend resource used by multiple Harness components. This saturated the shared platform infrastructure and caused the cascading failures.

Mitigation

Disabled the capability across all environments
Temporarily increased platform capacity to restore stability

Next Steps

To prevent recurrence, Harness will:

Permanently fix the capability by profiling and eliminating the sub-optimal code path and query
Improve detection by enhancing alerting for resource-intensive queries on high-frequency platform paths

9 Sep 2026 23:23:46 (4 days ago)

Resolved: This incident has been resolved.

9 Sep 2026 04:30:49 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:39:18 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:36:40 (5 days ago)

Identified: We are continuing to work on a fix for this issue.

9 Sep 2026 00:29:20 (5 days ago)

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

8 Sep 2026 23:52:12 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 23:31:44 (5 days ago)

Investigating: We are continuing to investigate the issue.

8 Sep 2026 22:53:35 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 22:53:04 (5 days ago)

Investigating: We are currently investigating this issue.

8 Sep 2026 21:52:48 (6 days ago)

See all updates

Continuous Delivery - Next Generation (CDNG)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Slowness in Prod1 and Prod2 environment

Started 8 Sep 2026 21:52:48 (6 days ago), resolved 9 Sep 2026 04:30:49 (5 days ago)

Minor Incident

Postmortem

Continuous Delivery (CD) - FirstGen - EOS

Continuous Delivery - Next Generation (CDNG)

Cloud Cost Management (CCM)

More...

We are currently investigating this issue.

Postmortem: ### Summary

On September 8, 2026, customers in Prod 1 and Prod 2 experienced elevated platform latency and pipeline failures. The issue was caused by a regression in a newly released capability that triggered cascading failures under high load. Because the capability was behind a feature flag, it was quickly disabled, and service was restored after a brief monitoring period.

Customer Impact

Customers encountered slowness and failures during pipeline execution and UI operations. Some API calls returned errors or timed out.
No data loss or corruption occurred.

Root Cause

The new capability introduced a regression that created contention on a shared backend resource used by multiple Harness components. This saturated the shared platform infrastructure and caused the cascading failures.

Mitigation

Disabled the capability across all environments
Temporarily increased platform capacity to restore stability

Next Steps

To prevent recurrence, Harness will:

Permanently fix the capability by profiling and eliminating the sub-optimal code path and query
Improve detection by enhancing alerting for resource-intensive queries on high-frequency platform paths

9 Sep 2026 23:23:46 (4 days ago)

Resolved: This incident has been resolved.

9 Sep 2026 04:30:49 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:39:18 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:36:40 (5 days ago)

Identified: We are continuing to work on a fix for this issue.

9 Sep 2026 00:29:20 (5 days ago)

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

8 Sep 2026 23:52:12 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 23:31:44 (5 days ago)

Investigating: We are continuing to investigate the issue.

8 Sep 2026 22:53:35 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 22:53:04 (5 days ago)

Investigating: We are currently investigating this issue.

8 Sep 2026 21:52:48 (6 days ago)

See all updates

Cloud Cost Management (CCM)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Slowness in Prod1 and Prod2 environment

Started 8 Sep 2026 21:52:48 (6 days ago), resolved 9 Sep 2026 04:30:49 (5 days ago)

Minor Incident

Postmortem

Continuous Delivery (CD) - FirstGen - EOS

Continuous Delivery - Next Generation (CDNG)

Cloud Cost Management (CCM)

More...

We are currently investigating this issue.

Postmortem: ### Summary

On September 8, 2026, customers in Prod 1 and Prod 2 experienced elevated platform latency and pipeline failures. The issue was caused by a regression in a newly released capability that triggered cascading failures under high load. Because the capability was behind a feature flag, it was quickly disabled, and service was restored after a brief monitoring period.

Customer Impact

Customers encountered slowness and failures during pipeline execution and UI operations. Some API calls returned errors or timed out.
No data loss or corruption occurred.

Root Cause

The new capability introduced a regression that created contention on a shared backend resource used by multiple Harness components. This saturated the shared platform infrastructure and caused the cascading failures.

Mitigation

Disabled the capability across all environments
Temporarily increased platform capacity to restore stability

Next Steps

To prevent recurrence, Harness will:

Permanently fix the capability by profiling and eliminating the sub-optimal code path and query
Improve detection by enhancing alerting for resource-intensive queries on high-frequency platform paths

9 Sep 2026 23:23:46 (4 days ago)

Resolved: This incident has been resolved.

9 Sep 2026 04:30:49 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:39:18 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:36:40 (5 days ago)

Identified: We are continuing to work on a fix for this issue.

9 Sep 2026 00:29:20 (5 days ago)

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

8 Sep 2026 23:52:12 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 23:31:44 (5 days ago)

Investigating: We are continuing to investigate the issue.

8 Sep 2026 22:53:35 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 22:53:04 (5 days ago)

Investigating: We are currently investigating this issue.

8 Sep 2026 21:52:48 (6 days ago)

See all updates

Continuous Error Tracking (CET)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Slowness in Prod1 and Prod2 environment

Started 8 Sep 2026 21:52:48 (6 days ago), resolved 9 Sep 2026 04:30:49 (5 days ago)

Minor Incident

Postmortem

Continuous Delivery (CD) - FirstGen - EOS

Continuous Delivery - Next Generation (CDNG)

Cloud Cost Management (CCM)

More...

We are currently investigating this issue.

Postmortem: ### Summary

On September 8, 2026, customers in Prod 1 and Prod 2 experienced elevated platform latency and pipeline failures. The issue was caused by a regression in a newly released capability that triggered cascading failures under high load. Because the capability was behind a feature flag, it was quickly disabled, and service was restored after a brief monitoring period.

Customer Impact

Customers encountered slowness and failures during pipeline execution and UI operations. Some API calls returned errors or timed out.
No data loss or corruption occurred.

Root Cause

The new capability introduced a regression that created contention on a shared backend resource used by multiple Harness components. This saturated the shared platform infrastructure and caused the cascading failures.

Mitigation

Disabled the capability across all environments
Temporarily increased platform capacity to restore stability

Next Steps

To prevent recurrence, Harness will:

Permanently fix the capability by profiling and eliminating the sub-optimal code path and query
Improve detection by enhancing alerting for resource-intensive queries on high-frequency platform paths

9 Sep 2026 23:23:46 (4 days ago)

Resolved: This incident has been resolved.

9 Sep 2026 04:30:49 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:39:18 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:36:40 (5 days ago)

Identified: We are continuing to work on a fix for this issue.

9 Sep 2026 00:29:20 (5 days ago)

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

8 Sep 2026 23:52:12 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 23:31:44 (5 days ago)

Investigating: We are continuing to investigate the issue.

8 Sep 2026 22:53:35 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 22:53:04 (5 days ago)

Investigating: We are currently investigating this issue.

8 Sep 2026 21:52:48 (6 days ago)

See all updates

Chaos Engineering

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Slowness in Prod1 and Prod2 environment

Started 8 Sep 2026 21:52:48 (6 days ago), resolved 9 Sep 2026 04:30:49 (5 days ago)

Minor Incident

Postmortem

Continuous Delivery (CD) - FirstGen - EOS

Continuous Delivery - Next Generation (CDNG)

Cloud Cost Management (CCM)

More...

We are currently investigating this issue.

Postmortem: ### Summary

On September 8, 2026, customers in Prod 1 and Prod 2 experienced elevated platform latency and pipeline failures. The issue was caused by a regression in a newly released capability that triggered cascading failures under high load. Because the capability was behind a feature flag, it was quickly disabled, and service was restored after a brief monitoring period.

Customer Impact

Customers encountered slowness and failures during pipeline execution and UI operations. Some API calls returned errors or timed out.
No data loss or corruption occurred.

Root Cause

The new capability introduced a regression that created contention on a shared backend resource used by multiple Harness components. This saturated the shared platform infrastructure and caused the cascading failures.

Mitigation

Disabled the capability across all environments
Temporarily increased platform capacity to restore stability

Next Steps

To prevent recurrence, Harness will:

Permanently fix the capability by profiling and eliminating the sub-optimal code path and query
Improve detection by enhancing alerting for resource-intensive queries on high-frequency platform paths

9 Sep 2026 23:23:46 (4 days ago)

Resolved: This incident has been resolved.

9 Sep 2026 04:30:49 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:39:18 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:36:40 (5 days ago)

Identified: We are continuing to work on a fix for this issue.

9 Sep 2026 00:29:20 (5 days ago)

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

8 Sep 2026 23:52:12 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 23:31:44 (5 days ago)

Investigating: We are continuing to investigate the issue.

8 Sep 2026 22:53:35 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 22:53:04 (5 days ago)

Investigating: We are currently investigating this issue.

8 Sep 2026 21:52:48 (6 days ago)

See all updates

Continuous Integration Enterprise(CIE) - Self Hosted Runners

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Continuous Integration Enterprise(CIE) - Mac Cloud Builds

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Continuous Integration Enterprise(CIE) - Windows Cloud Builds

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Continuous Integration Enterprise(CIE) - Linux Cloud Builds

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Custom Dashboards

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Feature Flags (FF)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Slowness in Prod1 and Prod2 environment

Started 8 Sep 2026 21:52:48 (6 days ago), resolved 9 Sep 2026 04:30:49 (5 days ago)

Minor Incident

Postmortem

Continuous Delivery (CD) - FirstGen - EOS

Continuous Delivery - Next Generation (CDNG)

Cloud Cost Management (CCM)

More...

We are currently investigating this issue.

Postmortem: ### Summary

On September 8, 2026, customers in Prod 1 and Prod 2 experienced elevated platform latency and pipeline failures. The issue was caused by a regression in a newly released capability that triggered cascading failures under high load. Because the capability was behind a feature flag, it was quickly disabled, and service was restored after a brief monitoring period.

Customer Impact

Customers encountered slowness and failures during pipeline execution and UI operations. Some API calls returned errors or timed out.
No data loss or corruption occurred.

Root Cause

The new capability introduced a regression that created contention on a shared backend resource used by multiple Harness components. This saturated the shared platform infrastructure and caused the cascading failures.

Mitigation

Disabled the capability across all environments
Temporarily increased platform capacity to restore stability

Next Steps

To prevent recurrence, Harness will:

Permanently fix the capability by profiling and eliminating the sub-optimal code path and query
Improve detection by enhancing alerting for resource-intensive queries on high-frequency platform paths

9 Sep 2026 23:23:46 (4 days ago)

Resolved: This incident has been resolved.

9 Sep 2026 04:30:49 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:39:18 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:36:40 (5 days ago)

Identified: We are continuing to work on a fix for this issue.

9 Sep 2026 00:29:20 (5 days ago)

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

8 Sep 2026 23:52:12 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 23:31:44 (5 days ago)

Investigating: We are continuing to investigate the issue.

8 Sep 2026 22:53:35 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 22:53:04 (5 days ago)

Investigating: We are currently investigating this issue.

8 Sep 2026 21:52:48 (6 days ago)

See all updates

Security Testing Orchestration (STO)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Service Reliability Management (SRM)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Internal Developer Portal (IDP)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Infrastructure as Code Management (IaCM)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Software Supply Chain Assurance (SSCA)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Software Engineering Insights (SEI) /AI DLC Insights

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Code Repository

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Artifact Registry

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Platform

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

AI Test Automation

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

FME

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Slowness in Prod1 and Prod2 environment

Started 8 Sep 2026 21:52:48 (6 days ago), resolved 9 Sep 2026 04:30:49 (5 days ago)

Minor Incident

Postmortem

Continuous Delivery (CD) - FirstGen - EOS

Continuous Delivery - Next Generation (CDNG)

Cloud Cost Management (CCM)

More...

We are currently investigating this issue.

Postmortem: ### Summary

On September 8, 2026, customers in Prod 1 and Prod 2 experienced elevated platform latency and pipeline failures. The issue was caused by a regression in a newly released capability that triggered cascading failures under high load. Because the capability was behind a feature flag, it was quickly disabled, and service was restored after a brief monitoring period.

Customer Impact

Customers encountered slowness and failures during pipeline execution and UI operations. Some API calls returned errors or timed out.
No data loss or corruption occurred.

Root Cause

The new capability introduced a regression that created contention on a shared backend resource used by multiple Harness components. This saturated the shared platform infrastructure and caused the cascading failures.

Mitigation

Disabled the capability across all environments
Temporarily increased platform capacity to restore stability

Next Steps

To prevent recurrence, Harness will:

Permanently fix the capability by profiling and eliminating the sub-optimal code path and query
Improve detection by enhancing alerting for resource-intensive queries on high-frequency platform paths

9 Sep 2026 23:23:46 (4 days ago)

Resolved: This incident has been resolved.

9 Sep 2026 04:30:49 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:39:18 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:36:40 (5 days ago)

Identified: We are continuing to work on a fix for this issue.

9 Sep 2026 00:29:20 (5 days ago)

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

8 Sep 2026 23:52:12 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 23:31:44 (5 days ago)

Investigating: We are continuing to investigate the issue.

8 Sep 2026 22:53:35 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 22:53:04 (5 days ago)

Investigating: We are currently investigating this issue.

8 Sep 2026 21:52:48 (6 days ago)

See all updates

Release Management

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Harness Prod 2

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Continuous Delivery (CD) - FirstGen - EOS

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Slowness in Prod1 and Prod2 environment

Started 8 Sep 2026 21:52:48 (6 days ago), resolved 9 Sep 2026 04:30:49 (5 days ago)

Minor Incident

Postmortem

Continuous Delivery (CD) - FirstGen - EOS

Continuous Delivery - Next Generation (CDNG)

Cloud Cost Management (CCM)

More...

We are currently investigating this issue.

Postmortem: ### Summary

On September 8, 2026, customers in Prod 1 and Prod 2 experienced elevated platform latency and pipeline failures. The issue was caused by a regression in a newly released capability that triggered cascading failures under high load. Because the capability was behind a feature flag, it was quickly disabled, and service was restored after a brief monitoring period.

Customer Impact

Customers encountered slowness and failures during pipeline execution and UI operations. Some API calls returned errors or timed out.
No data loss or corruption occurred.

Root Cause

The new capability introduced a regression that created contention on a shared backend resource used by multiple Harness components. This saturated the shared platform infrastructure and caused the cascading failures.

Mitigation

Disabled the capability across all environments
Temporarily increased platform capacity to restore stability

Next Steps

To prevent recurrence, Harness will:

Permanently fix the capability by profiling and eliminating the sub-optimal code path and query
Improve detection by enhancing alerting for resource-intensive queries on high-frequency platform paths

9 Sep 2026 23:23:46 (4 days ago)

Resolved: This incident has been resolved.

9 Sep 2026 04:30:49 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:39:18 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:36:40 (5 days ago)

Identified: We are continuing to work on a fix for this issue.

9 Sep 2026 00:29:20 (5 days ago)

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

8 Sep 2026 23:52:12 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 23:31:44 (5 days ago)

Investigating: We are continuing to investigate the issue.

8 Sep 2026 22:53:35 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 22:53:04 (5 days ago)

Investigating: We are currently investigating this issue.

8 Sep 2026 21:52:48 (6 days ago)

See all updates

Continuous Delivery - Next Generation (CDNG)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Slowness in Prod1 and Prod2 environment

Started 8 Sep 2026 21:52:48 (6 days ago), resolved 9 Sep 2026 04:30:49 (5 days ago)

Minor Incident

Postmortem

Continuous Delivery (CD) - FirstGen - EOS

Continuous Delivery - Next Generation (CDNG)

Cloud Cost Management (CCM)

More...

We are currently investigating this issue.

Postmortem: ### Summary

On September 8, 2026, customers in Prod 1 and Prod 2 experienced elevated platform latency and pipeline failures. The issue was caused by a regression in a newly released capability that triggered cascading failures under high load. Because the capability was behind a feature flag, it was quickly disabled, and service was restored after a brief monitoring period.

Customer Impact

Customers encountered slowness and failures during pipeline execution and UI operations. Some API calls returned errors or timed out.
No data loss or corruption occurred.

Root Cause

The new capability introduced a regression that created contention on a shared backend resource used by multiple Harness components. This saturated the shared platform infrastructure and caused the cascading failures.

Mitigation

Disabled the capability across all environments
Temporarily increased platform capacity to restore stability

Next Steps

To prevent recurrence, Harness will:

Permanently fix the capability by profiling and eliminating the sub-optimal code path and query
Improve detection by enhancing alerting for resource-intensive queries on high-frequency platform paths

9 Sep 2026 23:23:46 (4 days ago)

Resolved: This incident has been resolved.

9 Sep 2026 04:30:49 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:39:18 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:36:40 (5 days ago)

Identified: We are continuing to work on a fix for this issue.

9 Sep 2026 00:29:20 (5 days ago)

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

8 Sep 2026 23:52:12 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 23:31:44 (5 days ago)

Investigating: We are continuing to investigate the issue.

8 Sep 2026 22:53:35 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 22:53:04 (5 days ago)

Investigating: We are currently investigating this issue.

8 Sep 2026 21:52:48 (6 days ago)

See all updates

Cloud Cost Management (CCM)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Slowness in Prod1 and Prod2 environment

Started 8 Sep 2026 21:52:48 (6 days ago), resolved 9 Sep 2026 04:30:49 (5 days ago)

Minor Incident

Postmortem

Continuous Delivery (CD) - FirstGen - EOS

Continuous Delivery - Next Generation (CDNG)

Cloud Cost Management (CCM)

More...

We are currently investigating this issue.

Postmortem: ### Summary

On September 8, 2026, customers in Prod 1 and Prod 2 experienced elevated platform latency and pipeline failures. The issue was caused by a regression in a newly released capability that triggered cascading failures under high load. Because the capability was behind a feature flag, it was quickly disabled, and service was restored after a brief monitoring period.

Customer Impact

Customers encountered slowness and failures during pipeline execution and UI operations. Some API calls returned errors or timed out.
No data loss or corruption occurred.

Root Cause

The new capability introduced a regression that created contention on a shared backend resource used by multiple Harness components. This saturated the shared platform infrastructure and caused the cascading failures.

Mitigation

Disabled the capability across all environments
Temporarily increased platform capacity to restore stability

Next Steps

To prevent recurrence, Harness will:

Permanently fix the capability by profiling and eliminating the sub-optimal code path and query
Improve detection by enhancing alerting for resource-intensive queries on high-frequency platform paths

9 Sep 2026 23:23:46 (4 days ago)

Resolved: This incident has been resolved.

9 Sep 2026 04:30:49 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:39:18 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:36:40 (5 days ago)

Identified: We are continuing to work on a fix for this issue.

9 Sep 2026 00:29:20 (5 days ago)

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

8 Sep 2026 23:52:12 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 23:31:44 (5 days ago)

Investigating: We are continuing to investigate the issue.

8 Sep 2026 22:53:35 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 22:53:04 (5 days ago)

Investigating: We are currently investigating this issue.

8 Sep 2026 21:52:48 (6 days ago)

See all updates

Continuous Error Tracking (CET)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Slowness in Prod1 and Prod2 environment

Started 8 Sep 2026 21:52:48 (6 days ago), resolved 9 Sep 2026 04:30:49 (5 days ago)

Minor Incident

Postmortem

Continuous Delivery (CD) - FirstGen - EOS

Continuous Delivery - Next Generation (CDNG)

Cloud Cost Management (CCM)

More...

We are currently investigating this issue.

Postmortem: ### Summary

On September 8, 2026, customers in Prod 1 and Prod 2 experienced elevated platform latency and pipeline failures. The issue was caused by a regression in a newly released capability that triggered cascading failures under high load. Because the capability was behind a feature flag, it was quickly disabled, and service was restored after a brief monitoring period.

Customer Impact

Customers encountered slowness and failures during pipeline execution and UI operations. Some API calls returned errors or timed out.
No data loss or corruption occurred.

Root Cause

The new capability introduced a regression that created contention on a shared backend resource used by multiple Harness components. This saturated the shared platform infrastructure and caused the cascading failures.

Mitigation

Disabled the capability across all environments
Temporarily increased platform capacity to restore stability

Next Steps

To prevent recurrence, Harness will:

Permanently fix the capability by profiling and eliminating the sub-optimal code path and query
Improve detection by enhancing alerting for resource-intensive queries on high-frequency platform paths

9 Sep 2026 23:23:46 (4 days ago)

Resolved: This incident has been resolved.

9 Sep 2026 04:30:49 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:39:18 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:36:40 (5 days ago)

Identified: We are continuing to work on a fix for this issue.

9 Sep 2026 00:29:20 (5 days ago)

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

8 Sep 2026 23:52:12 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 23:31:44 (5 days ago)

Investigating: We are continuing to investigate the issue.

8 Sep 2026 22:53:35 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 22:53:04 (5 days ago)

Investigating: We are currently investigating this issue.

8 Sep 2026 21:52:48 (6 days ago)

See all updates

Chaos Engineering

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Slowness in Prod1 and Prod2 environment

Started 8 Sep 2026 21:52:48 (6 days ago), resolved 9 Sep 2026 04:30:49 (5 days ago)

Minor Incident

Postmortem

Continuous Delivery (CD) - FirstGen - EOS

Continuous Delivery - Next Generation (CDNG)

Cloud Cost Management (CCM)

More...

We are currently investigating this issue.

Postmortem: ### Summary

On September 8, 2026, customers in Prod 1 and Prod 2 experienced elevated platform latency and pipeline failures. The issue was caused by a regression in a newly released capability that triggered cascading failures under high load. Because the capability was behind a feature flag, it was quickly disabled, and service was restored after a brief monitoring period.

Customer Impact

Customers encountered slowness and failures during pipeline execution and UI operations. Some API calls returned errors or timed out.
No data loss or corruption occurred.

Root Cause

The new capability introduced a regression that created contention on a shared backend resource used by multiple Harness components. This saturated the shared platform infrastructure and caused the cascading failures.

Mitigation

Disabled the capability across all environments
Temporarily increased platform capacity to restore stability

Next Steps

To prevent recurrence, Harness will:

Permanently fix the capability by profiling and eliminating the sub-optimal code path and query
Improve detection by enhancing alerting for resource-intensive queries on high-frequency platform paths

9 Sep 2026 23:23:46 (4 days ago)

Resolved: This incident has been resolved.

9 Sep 2026 04:30:49 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:39:18 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:36:40 (5 days ago)

Identified: We are continuing to work on a fix for this issue.

9 Sep 2026 00:29:20 (5 days ago)

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

8 Sep 2026 23:52:12 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 23:31:44 (5 days ago)

Investigating: We are continuing to investigate the issue.

8 Sep 2026 22:53:35 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 22:53:04 (5 days ago)

Investigating: We are currently investigating this issue.

8 Sep 2026 21:52:48 (6 days ago)

See all updates

Continuous Integration Enterprise(CIE) - Self Hosted Runners

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Slowness in Prod1 and Prod2 environment

Started 8 Sep 2026 21:52:48 (6 days ago), resolved 9 Sep 2026 04:30:49 (5 days ago)

Minor Incident

Postmortem

Continuous Delivery (CD) - FirstGen - EOS

Continuous Delivery - Next Generation (CDNG)

Cloud Cost Management (CCM)

More...

We are currently investigating this issue.

Postmortem: ### Summary

On September 8, 2026, customers in Prod 1 and Prod 2 experienced elevated platform latency and pipeline failures. The issue was caused by a regression in a newly released capability that triggered cascading failures under high load. Because the capability was behind a feature flag, it was quickly disabled, and service was restored after a brief monitoring period.

Customer Impact

Customers encountered slowness and failures during pipeline execution and UI operations. Some API calls returned errors or timed out.
No data loss or corruption occurred.

Root Cause

The new capability introduced a regression that created contention on a shared backend resource used by multiple Harness components. This saturated the shared platform infrastructure and caused the cascading failures.

Mitigation

Disabled the capability across all environments
Temporarily increased platform capacity to restore stability

Next Steps

To prevent recurrence, Harness will:

Permanently fix the capability by profiling and eliminating the sub-optimal code path and query
Improve detection by enhancing alerting for resource-intensive queries on high-frequency platform paths

9 Sep 2026 23:23:46 (4 days ago)

Resolved: This incident has been resolved.

9 Sep 2026 04:30:49 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:39:18 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:36:40 (5 days ago)

Identified: We are continuing to work on a fix for this issue.

9 Sep 2026 00:29:20 (5 days ago)

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

8 Sep 2026 23:52:12 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 23:31:44 (5 days ago)

Investigating: We are continuing to investigate the issue.

8 Sep 2026 22:53:35 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 22:53:04 (5 days ago)

Investigating: We are currently investigating this issue.

8 Sep 2026 21:52:48 (6 days ago)

See all updates

Continuous Integration Enterprise(CIE) - Mac Cloud Builds

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Slowness in Prod1 and Prod2 environment

Started 8 Sep 2026 21:52:48 (6 days ago), resolved 9 Sep 2026 04:30:49 (5 days ago)

Minor Incident

Postmortem

Continuous Delivery (CD) - FirstGen - EOS

Continuous Delivery - Next Generation (CDNG)

Cloud Cost Management (CCM)

More...

We are currently investigating this issue.

Postmortem: ### Summary

On September 8, 2026, customers in Prod 1 and Prod 2 experienced elevated platform latency and pipeline failures. The issue was caused by a regression in a newly released capability that triggered cascading failures under high load. Because the capability was behind a feature flag, it was quickly disabled, and service was restored after a brief monitoring period.

Customer Impact

Customers encountered slowness and failures during pipeline execution and UI operations. Some API calls returned errors or timed out.
No data loss or corruption occurred.

Root Cause

The new capability introduced a regression that created contention on a shared backend resource used by multiple Harness components. This saturated the shared platform infrastructure and caused the cascading failures.

Mitigation

Disabled the capability across all environments
Temporarily increased platform capacity to restore stability

Next Steps

To prevent recurrence, Harness will:

Permanently fix the capability by profiling and eliminating the sub-optimal code path and query
Improve detection by enhancing alerting for resource-intensive queries on high-frequency platform paths

9 Sep 2026 23:23:46 (4 days ago)

Resolved: This incident has been resolved.

9 Sep 2026 04:30:49 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:39:18 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:36:40 (5 days ago)

Identified: We are continuing to work on a fix for this issue.

9 Sep 2026 00:29:20 (5 days ago)

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

8 Sep 2026 23:52:12 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 23:31:44 (5 days ago)

Investigating: We are continuing to investigate the issue.

8 Sep 2026 22:53:35 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 22:53:04 (5 days ago)

Investigating: We are currently investigating this issue.

8 Sep 2026 21:52:48 (6 days ago)

See all updates

Continuous Integration Enterprise(CIE) - Windows Cloud Builds

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Slowness in Prod1 and Prod2 environment

Started 8 Sep 2026 21:52:48 (6 days ago), resolved 9 Sep 2026 04:30:49 (5 days ago)

Minor Incident

Postmortem

Continuous Delivery (CD) - FirstGen - EOS

Continuous Delivery - Next Generation (CDNG)

Cloud Cost Management (CCM)

More...

We are currently investigating this issue.

Postmortem: ### Summary

On September 8, 2026, customers in Prod 1 and Prod 2 experienced elevated platform latency and pipeline failures. The issue was caused by a regression in a newly released capability that triggered cascading failures under high load. Because the capability was behind a feature flag, it was quickly disabled, and service was restored after a brief monitoring period.

Customer Impact

Customers encountered slowness and failures during pipeline execution and UI operations. Some API calls returned errors or timed out.
No data loss or corruption occurred.

Root Cause

The new capability introduced a regression that created contention on a shared backend resource used by multiple Harness components. This saturated the shared platform infrastructure and caused the cascading failures.

Mitigation

Disabled the capability across all environments
Temporarily increased platform capacity to restore stability

Next Steps

To prevent recurrence, Harness will:

Permanently fix the capability by profiling and eliminating the sub-optimal code path and query
Improve detection by enhancing alerting for resource-intensive queries on high-frequency platform paths

9 Sep 2026 23:23:46 (4 days ago)

Resolved: This incident has been resolved.

9 Sep 2026 04:30:49 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:39:18 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:36:40 (5 days ago)

Identified: We are continuing to work on a fix for this issue.

9 Sep 2026 00:29:20 (5 days ago)

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

8 Sep 2026 23:52:12 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 23:31:44 (5 days ago)

Investigating: We are continuing to investigate the issue.

8 Sep 2026 22:53:35 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 22:53:04 (5 days ago)

Investigating: We are currently investigating this issue.

8 Sep 2026 21:52:48 (6 days ago)

See all updates

Continuous Integration Enterprise(CIE) - Linux Cloud Builds

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Slowness in Prod1 and Prod2 environment

Started 8 Sep 2026 21:52:48 (6 days ago), resolved 9 Sep 2026 04:30:49 (5 days ago)

Minor Incident

Postmortem

Continuous Delivery (CD) - FirstGen - EOS

Continuous Delivery - Next Generation (CDNG)

Cloud Cost Management (CCM)

More...

We are currently investigating this issue.

Postmortem: ### Summary

On September 8, 2026, customers in Prod 1 and Prod 2 experienced elevated platform latency and pipeline failures. The issue was caused by a regression in a newly released capability that triggered cascading failures under high load. Because the capability was behind a feature flag, it was quickly disabled, and service was restored after a brief monitoring period.

Customer Impact

Customers encountered slowness and failures during pipeline execution and UI operations. Some API calls returned errors or timed out.
No data loss or corruption occurred.

Root Cause

The new capability introduced a regression that created contention on a shared backend resource used by multiple Harness components. This saturated the shared platform infrastructure and caused the cascading failures.

Mitigation

Disabled the capability across all environments
Temporarily increased platform capacity to restore stability

Next Steps

To prevent recurrence, Harness will:

Permanently fix the capability by profiling and eliminating the sub-optimal code path and query
Improve detection by enhancing alerting for resource-intensive queries on high-frequency platform paths

9 Sep 2026 23:23:46 (4 days ago)

Resolved: This incident has been resolved.

9 Sep 2026 04:30:49 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:39:18 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:36:40 (5 days ago)

Identified: We are continuing to work on a fix for this issue.

9 Sep 2026 00:29:20 (5 days ago)

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

8 Sep 2026 23:52:12 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 23:31:44 (5 days ago)

Investigating: We are continuing to investigate the issue.

8 Sep 2026 22:53:35 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 22:53:04 (5 days ago)

Investigating: We are currently investigating this issue.

8 Sep 2026 21:52:48 (6 days ago)

See all updates

Custom Dashboards

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Slowness in Prod1 and Prod2 environment

Started 8 Sep 2026 21:52:48 (6 days ago), resolved 9 Sep 2026 04:30:49 (5 days ago)

Minor Incident

Postmortem

Continuous Delivery (CD) - FirstGen - EOS

Continuous Delivery - Next Generation (CDNG)

Cloud Cost Management (CCM)

More...

We are currently investigating this issue.

Postmortem: ### Summary

On September 8, 2026, customers in Prod 1 and Prod 2 experienced elevated platform latency and pipeline failures. The issue was caused by a regression in a newly released capability that triggered cascading failures under high load. Because the capability was behind a feature flag, it was quickly disabled, and service was restored after a brief monitoring period.

Customer Impact

Customers encountered slowness and failures during pipeline execution and UI operations. Some API calls returned errors or timed out.
No data loss or corruption occurred.

Root Cause

The new capability introduced a regression that created contention on a shared backend resource used by multiple Harness components. This saturated the shared platform infrastructure and caused the cascading failures.

Mitigation

Disabled the capability across all environments
Temporarily increased platform capacity to restore stability

Next Steps

To prevent recurrence, Harness will:

Permanently fix the capability by profiling and eliminating the sub-optimal code path and query
Improve detection by enhancing alerting for resource-intensive queries on high-frequency platform paths

9 Sep 2026 23:23:46 (4 days ago)

Resolved: This incident has been resolved.

9 Sep 2026 04:30:49 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:39:18 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:36:40 (5 days ago)

Identified: We are continuing to work on a fix for this issue.

9 Sep 2026 00:29:20 (5 days ago)

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

8 Sep 2026 23:52:12 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 23:31:44 (5 days ago)

Investigating: We are continuing to investigate the issue.

8 Sep 2026 22:53:35 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 22:53:04 (5 days ago)

Investigating: We are currently investigating this issue.

8 Sep 2026 21:52:48 (6 days ago)

See all updates

Feature Flags (FF)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Slowness in Prod1 and Prod2 environment

Started 8 Sep 2026 21:52:48 (6 days ago), resolved 9 Sep 2026 04:30:49 (5 days ago)

Minor Incident

Postmortem

Continuous Delivery (CD) - FirstGen - EOS

Continuous Delivery - Next Generation (CDNG)

Cloud Cost Management (CCM)

More...

We are currently investigating this issue.

Postmortem: ### Summary

On September 8, 2026, customers in Prod 1 and Prod 2 experienced elevated platform latency and pipeline failures. The issue was caused by a regression in a newly released capability that triggered cascading failures under high load. Because the capability was behind a feature flag, it was quickly disabled, and service was restored after a brief monitoring period.

Customer Impact

Customers encountered slowness and failures during pipeline execution and UI operations. Some API calls returned errors or timed out.
No data loss or corruption occurred.

Root Cause

The new capability introduced a regression that created contention on a shared backend resource used by multiple Harness components. This saturated the shared platform infrastructure and caused the cascading failures.

Mitigation

Disabled the capability across all environments
Temporarily increased platform capacity to restore stability

Next Steps

To prevent recurrence, Harness will:

Permanently fix the capability by profiling and eliminating the sub-optimal code path and query
Improve detection by enhancing alerting for resource-intensive queries on high-frequency platform paths

9 Sep 2026 23:23:46 (4 days ago)

Resolved: This incident has been resolved.

9 Sep 2026 04:30:49 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:39:18 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:36:40 (5 days ago)

Identified: We are continuing to work on a fix for this issue.

9 Sep 2026 00:29:20 (5 days ago)

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

8 Sep 2026 23:52:12 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 23:31:44 (5 days ago)

Investigating: We are continuing to investigate the issue.

8 Sep 2026 22:53:35 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 22:53:04 (5 days ago)

Investigating: We are currently investigating this issue.

8 Sep 2026 21:52:48 (6 days ago)

See all updates

Security Testing Orchestration (STO)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Slowness in Prod1 and Prod2 environment

Started 8 Sep 2026 21:52:48 (6 days ago), resolved 9 Sep 2026 04:30:49 (5 days ago)

Minor Incident

Postmortem

Continuous Delivery (CD) - FirstGen - EOS

Continuous Delivery - Next Generation (CDNG)

Cloud Cost Management (CCM)

More...

We are currently investigating this issue.

Postmortem: ### Summary

On September 8, 2026, customers in Prod 1 and Prod 2 experienced elevated platform latency and pipeline failures. The issue was caused by a regression in a newly released capability that triggered cascading failures under high load. Because the capability was behind a feature flag, it was quickly disabled, and service was restored after a brief monitoring period.

Customer Impact

Customers encountered slowness and failures during pipeline execution and UI operations. Some API calls returned errors or timed out.
No data loss or corruption occurred.

Root Cause

The new capability introduced a regression that created contention on a shared backend resource used by multiple Harness components. This saturated the shared platform infrastructure and caused the cascading failures.

Mitigation

Disabled the capability across all environments
Temporarily increased platform capacity to restore stability

Next Steps

To prevent recurrence, Harness will:

Permanently fix the capability by profiling and eliminating the sub-optimal code path and query
Improve detection by enhancing alerting for resource-intensive queries on high-frequency platform paths

9 Sep 2026 23:23:46 (4 days ago)

Resolved: This incident has been resolved.

9 Sep 2026 04:30:49 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:39:18 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:36:40 (5 days ago)

Identified: We are continuing to work on a fix for this issue.

9 Sep 2026 00:29:20 (5 days ago)

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

8 Sep 2026 23:52:12 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 23:31:44 (5 days ago)

Investigating: We are continuing to investigate the issue.

8 Sep 2026 22:53:35 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 22:53:04 (5 days ago)

Investigating: We are currently investigating this issue.

8 Sep 2026 21:52:48 (6 days ago)

See all updates

Service Reliability Management (SRM)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Slowness in Prod1 and Prod2 environment

Started 8 Sep 2026 21:52:48 (6 days ago), resolved 9 Sep 2026 04:30:49 (5 days ago)

Minor Incident

Postmortem

Continuous Delivery (CD) - FirstGen - EOS

Continuous Delivery - Next Generation (CDNG)

Cloud Cost Management (CCM)

More...

We are currently investigating this issue.

Postmortem: ### Summary

On September 8, 2026, customers in Prod 1 and Prod 2 experienced elevated platform latency and pipeline failures. The issue was caused by a regression in a newly released capability that triggered cascading failures under high load. Because the capability was behind a feature flag, it was quickly disabled, and service was restored after a brief monitoring period.

Customer Impact

Customers encountered slowness and failures during pipeline execution and UI operations. Some API calls returned errors or timed out.
No data loss or corruption occurred.

Root Cause

The new capability introduced a regression that created contention on a shared backend resource used by multiple Harness components. This saturated the shared platform infrastructure and caused the cascading failures.

Mitigation

Disabled the capability across all environments
Temporarily increased platform capacity to restore stability

Next Steps

To prevent recurrence, Harness will:

Permanently fix the capability by profiling and eliminating the sub-optimal code path and query
Improve detection by enhancing alerting for resource-intensive queries on high-frequency platform paths

9 Sep 2026 23:23:46 (4 days ago)

Resolved: This incident has been resolved.

9 Sep 2026 04:30:49 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:39:18 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:36:40 (5 days ago)

Identified: We are continuing to work on a fix for this issue.

9 Sep 2026 00:29:20 (5 days ago)

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

8 Sep 2026 23:52:12 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 23:31:44 (5 days ago)

Investigating: We are continuing to investigate the issue.

8 Sep 2026 22:53:35 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 22:53:04 (5 days ago)

Investigating: We are currently investigating this issue.

8 Sep 2026 21:52:48 (6 days ago)

See all updates

Internal Developer Portal (IDP)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Slowness in Prod1 and Prod2 environment

Started 8 Sep 2026 21:52:48 (6 days ago), resolved 9 Sep 2026 04:30:49 (5 days ago)

Minor Incident

Postmortem

Continuous Delivery (CD) - FirstGen - EOS

Continuous Delivery - Next Generation (CDNG)

Cloud Cost Management (CCM)

More...

We are currently investigating this issue.

Postmortem: ### Summary

On September 8, 2026, customers in Prod 1 and Prod 2 experienced elevated platform latency and pipeline failures. The issue was caused by a regression in a newly released capability that triggered cascading failures under high load. Because the capability was behind a feature flag, it was quickly disabled, and service was restored after a brief monitoring period.

Customer Impact

Customers encountered slowness and failures during pipeline execution and UI operations. Some API calls returned errors or timed out.
No data loss or corruption occurred.

Root Cause

The new capability introduced a regression that created contention on a shared backend resource used by multiple Harness components. This saturated the shared platform infrastructure and caused the cascading failures.

Mitigation

Disabled the capability across all environments
Temporarily increased platform capacity to restore stability

Next Steps

To prevent recurrence, Harness will:

Permanently fix the capability by profiling and eliminating the sub-optimal code path and query
Improve detection by enhancing alerting for resource-intensive queries on high-frequency platform paths

9 Sep 2026 23:23:46 (4 days ago)

Resolved: This incident has been resolved.

9 Sep 2026 04:30:49 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:39:18 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:36:40 (5 days ago)

Identified: We are continuing to work on a fix for this issue.

9 Sep 2026 00:29:20 (5 days ago)

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

8 Sep 2026 23:52:12 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 23:31:44 (5 days ago)

Investigating: We are continuing to investigate the issue.

8 Sep 2026 22:53:35 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 22:53:04 (5 days ago)

Investigating: We are currently investigating this issue.

8 Sep 2026 21:52:48 (6 days ago)

See all updates

Infrastructure as Code Management (IaCM)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Slowness in Prod1 and Prod2 environment

Started 8 Sep 2026 21:52:48 (6 days ago), resolved 9 Sep 2026 04:30:49 (5 days ago)

Minor Incident

Postmortem

Continuous Delivery (CD) - FirstGen - EOS

Continuous Delivery - Next Generation (CDNG)

Cloud Cost Management (CCM)

More...

We are currently investigating this issue.

Postmortem: ### Summary

On September 8, 2026, customers in Prod 1 and Prod 2 experienced elevated platform latency and pipeline failures. The issue was caused by a regression in a newly released capability that triggered cascading failures under high load. Because the capability was behind a feature flag, it was quickly disabled, and service was restored after a brief monitoring period.

Customer Impact

Customers encountered slowness and failures during pipeline execution and UI operations. Some API calls returned errors or timed out.
No data loss or corruption occurred.

Root Cause

The new capability introduced a regression that created contention on a shared backend resource used by multiple Harness components. This saturated the shared platform infrastructure and caused the cascading failures.

Mitigation

Disabled the capability across all environments
Temporarily increased platform capacity to restore stability

Next Steps

To prevent recurrence, Harness will:

Permanently fix the capability by profiling and eliminating the sub-optimal code path and query
Improve detection by enhancing alerting for resource-intensive queries on high-frequency platform paths

9 Sep 2026 23:23:46 (4 days ago)

Resolved: This incident has been resolved.

9 Sep 2026 04:30:49 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:39:18 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:36:40 (5 days ago)

Identified: We are continuing to work on a fix for this issue.

9 Sep 2026 00:29:20 (5 days ago)

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

8 Sep 2026 23:52:12 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 23:31:44 (5 days ago)

Investigating: We are continuing to investigate the issue.

8 Sep 2026 22:53:35 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 22:53:04 (5 days ago)

Investigating: We are currently investigating this issue.

8 Sep 2026 21:52:48 (6 days ago)

See all updates

Software Supply Chain Assurance (SSCA)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Slowness in Prod1 and Prod2 environment

Started 8 Sep 2026 21:52:48 (6 days ago), resolved 9 Sep 2026 04:30:49 (5 days ago)

Minor Incident

Postmortem

Continuous Delivery (CD) - FirstGen - EOS

Continuous Delivery - Next Generation (CDNG)

Cloud Cost Management (CCM)

More...

We are currently investigating this issue.

Postmortem: ### Summary

On September 8, 2026, customers in Prod 1 and Prod 2 experienced elevated platform latency and pipeline failures. The issue was caused by a regression in a newly released capability that triggered cascading failures under high load. Because the capability was behind a feature flag, it was quickly disabled, and service was restored after a brief monitoring period.

Customer Impact

Customers encountered slowness and failures during pipeline execution and UI operations. Some API calls returned errors or timed out.
No data loss or corruption occurred.

Root Cause

The new capability introduced a regression that created contention on a shared backend resource used by multiple Harness components. This saturated the shared platform infrastructure and caused the cascading failures.

Mitigation

Disabled the capability across all environments
Temporarily increased platform capacity to restore stability

Next Steps

To prevent recurrence, Harness will:

Permanently fix the capability by profiling and eliminating the sub-optimal code path and query
Improve detection by enhancing alerting for resource-intensive queries on high-frequency platform paths

9 Sep 2026 23:23:46 (4 days ago)

Resolved: This incident has been resolved.

9 Sep 2026 04:30:49 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:39:18 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:36:40 (5 days ago)

Identified: We are continuing to work on a fix for this issue.

9 Sep 2026 00:29:20 (5 days ago)

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

8 Sep 2026 23:52:12 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 23:31:44 (5 days ago)

Investigating: We are continuing to investigate the issue.

8 Sep 2026 22:53:35 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 22:53:04 (5 days ago)

Investigating: We are currently investigating this issue.

8 Sep 2026 21:52:48 (6 days ago)

See all updates

Software Engineering Insights (SEI) / AI DLC Insights

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Slowness in Prod1 and Prod2 environment

Started 8 Sep 2026 21:52:48 (6 days ago), resolved 9 Sep 2026 04:30:49 (5 days ago)

Minor Incident

Postmortem

Continuous Delivery (CD) - FirstGen - EOS

Continuous Delivery - Next Generation (CDNG)

Cloud Cost Management (CCM)

More...

We are currently investigating this issue.

Postmortem: ### Summary

On September 8, 2026, customers in Prod 1 and Prod 2 experienced elevated platform latency and pipeline failures. The issue was caused by a regression in a newly released capability that triggered cascading failures under high load. Because the capability was behind a feature flag, it was quickly disabled, and service was restored after a brief monitoring period.

Customer Impact

Customers encountered slowness and failures during pipeline execution and UI operations. Some API calls returned errors or timed out.
No data loss or corruption occurred.

Root Cause

The new capability introduced a regression that created contention on a shared backend resource used by multiple Harness components. This saturated the shared platform infrastructure and caused the cascading failures.

Mitigation

Disabled the capability across all environments
Temporarily increased platform capacity to restore stability

Next Steps

To prevent recurrence, Harness will:

Permanently fix the capability by profiling and eliminating the sub-optimal code path and query
Improve detection by enhancing alerting for resource-intensive queries on high-frequency platform paths

9 Sep 2026 23:23:46 (4 days ago)

Resolved: This incident has been resolved.

9 Sep 2026 04:30:49 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:39:18 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:36:40 (5 days ago)

Identified: We are continuing to work on a fix for this issue.

9 Sep 2026 00:29:20 (5 days ago)

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

8 Sep 2026 23:52:12 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 23:31:44 (5 days ago)

Investigating: We are continuing to investigate the issue.

8 Sep 2026 22:53:35 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 22:53:04 (5 days ago)

Investigating: We are currently investigating this issue.

8 Sep 2026 21:52:48 (6 days ago)

See all updates

Code Repository

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Slowness in Prod1 and Prod2 environment

Started 8 Sep 2026 21:52:48 (6 days ago), resolved 9 Sep 2026 04:30:49 (5 days ago)

Minor Incident

Postmortem

Continuous Delivery (CD) - FirstGen - EOS

Continuous Delivery - Next Generation (CDNG)

Cloud Cost Management (CCM)

More...

We are currently investigating this issue.

Postmortem: ### Summary

On September 8, 2026, customers in Prod 1 and Prod 2 experienced elevated platform latency and pipeline failures. The issue was caused by a regression in a newly released capability that triggered cascading failures under high load. Because the capability was behind a feature flag, it was quickly disabled, and service was restored after a brief monitoring period.

Customer Impact

Customers encountered slowness and failures during pipeline execution and UI operations. Some API calls returned errors or timed out.
No data loss or corruption occurred.

Root Cause

The new capability introduced a regression that created contention on a shared backend resource used by multiple Harness components. This saturated the shared platform infrastructure and caused the cascading failures.

Mitigation

Disabled the capability across all environments
Temporarily increased platform capacity to restore stability

Next Steps

To prevent recurrence, Harness will:

Permanently fix the capability by profiling and eliminating the sub-optimal code path and query
Improve detection by enhancing alerting for resource-intensive queries on high-frequency platform paths

9 Sep 2026 23:23:46 (4 days ago)

Resolved: This incident has been resolved.

9 Sep 2026 04:30:49 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:39:18 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:36:40 (5 days ago)

Identified: We are continuing to work on a fix for this issue.

9 Sep 2026 00:29:20 (5 days ago)

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

8 Sep 2026 23:52:12 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 23:31:44 (5 days ago)

Investigating: We are continuing to investigate the issue.

8 Sep 2026 22:53:35 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 22:53:04 (5 days ago)

Investigating: We are currently investigating this issue.

8 Sep 2026 21:52:48 (6 days ago)

See all updates

Artifact Registry

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Slowness in Prod1 and Prod2 environment

Started 8 Sep 2026 21:52:48 (6 days ago), resolved 9 Sep 2026 04:30:49 (5 days ago)

Minor Incident

Postmortem

Continuous Delivery (CD) - FirstGen - EOS

Continuous Delivery - Next Generation (CDNG)

Cloud Cost Management (CCM)

More...

We are currently investigating this issue.

Postmortem: ### Summary

On September 8, 2026, customers in Prod 1 and Prod 2 experienced elevated platform latency and pipeline failures. The issue was caused by a regression in a newly released capability that triggered cascading failures under high load. Because the capability was behind a feature flag, it was quickly disabled, and service was restored after a brief monitoring period.

Customer Impact

Customers encountered slowness and failures during pipeline execution and UI operations. Some API calls returned errors or timed out.
No data loss or corruption occurred.

Root Cause

The new capability introduced a regression that created contention on a shared backend resource used by multiple Harness components. This saturated the shared platform infrastructure and caused the cascading failures.

Mitigation

Disabled the capability across all environments
Temporarily increased platform capacity to restore stability

Next Steps

To prevent recurrence, Harness will:

Permanently fix the capability by profiling and eliminating the sub-optimal code path and query
Improve detection by enhancing alerting for resource-intensive queries on high-frequency platform paths

9 Sep 2026 23:23:46 (4 days ago)

Resolved: This incident has been resolved.

9 Sep 2026 04:30:49 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:39:18 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:36:40 (5 days ago)

Identified: We are continuing to work on a fix for this issue.

9 Sep 2026 00:29:20 (5 days ago)

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

8 Sep 2026 23:52:12 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 23:31:44 (5 days ago)

Investigating: We are continuing to investigate the issue.

8 Sep 2026 22:53:35 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 22:53:04 (5 days ago)

Investigating: We are currently investigating this issue.

8 Sep 2026 21:52:48 (6 days ago)

See all updates

Platform

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Slowness in Prod1 and Prod2 environment

Started 8 Sep 2026 21:52:48 (6 days ago), resolved 9 Sep 2026 04:30:49 (5 days ago)

Minor Incident

Postmortem

Continuous Delivery (CD) - FirstGen - EOS

Continuous Delivery - Next Generation (CDNG)

Cloud Cost Management (CCM)

More...

We are currently investigating this issue.

Postmortem: ### Summary

On September 8, 2026, customers in Prod 1 and Prod 2 experienced elevated platform latency and pipeline failures. The issue was caused by a regression in a newly released capability that triggered cascading failures under high load. Because the capability was behind a feature flag, it was quickly disabled, and service was restored after a brief monitoring period.

Customer Impact

Customers encountered slowness and failures during pipeline execution and UI operations. Some API calls returned errors or timed out.
No data loss or corruption occurred.

Root Cause

The new capability introduced a regression that created contention on a shared backend resource used by multiple Harness components. This saturated the shared platform infrastructure and caused the cascading failures.

Mitigation

Disabled the capability across all environments
Temporarily increased platform capacity to restore stability

Next Steps

To prevent recurrence, Harness will:

Permanently fix the capability by profiling and eliminating the sub-optimal code path and query
Improve detection by enhancing alerting for resource-intensive queries on high-frequency platform paths

9 Sep 2026 23:23:46 (4 days ago)

Resolved: This incident has been resolved.

9 Sep 2026 04:30:49 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:39:18 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:36:40 (5 days ago)

Identified: We are continuing to work on a fix for this issue.

9 Sep 2026 00:29:20 (5 days ago)

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

8 Sep 2026 23:52:12 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 23:31:44 (5 days ago)

Investigating: We are continuing to investigate the issue.

8 Sep 2026 22:53:35 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 22:53:04 (5 days ago)

Investigating: We are currently investigating this issue.

8 Sep 2026 21:52:48 (6 days ago)

See all updates

AI Test Automation

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Slowness in Prod1 and Prod2 environment

Started 8 Sep 2026 21:52:48 (6 days ago), resolved 9 Sep 2026 04:30:49 (5 days ago)

Minor Incident

Postmortem

Continuous Delivery (CD) - FirstGen - EOS

Continuous Delivery - Next Generation (CDNG)

Cloud Cost Management (CCM)

More...

We are currently investigating this issue.

Postmortem: ### Summary

On September 8, 2026, customers in Prod 1 and Prod 2 experienced elevated platform latency and pipeline failures. The issue was caused by a regression in a newly released capability that triggered cascading failures under high load. Because the capability was behind a feature flag, it was quickly disabled, and service was restored after a brief monitoring period.

Customer Impact

Customers encountered slowness and failures during pipeline execution and UI operations. Some API calls returned errors or timed out.
No data loss or corruption occurred.

Root Cause

The new capability introduced a regression that created contention on a shared backend resource used by multiple Harness components. This saturated the shared platform infrastructure and caused the cascading failures.

Mitigation

Disabled the capability across all environments
Temporarily increased platform capacity to restore stability

Next Steps

To prevent recurrence, Harness will:

Permanently fix the capability by profiling and eliminating the sub-optimal code path and query
Improve detection by enhancing alerting for resource-intensive queries on high-frequency platform paths

9 Sep 2026 23:23:46 (4 days ago)

Resolved: This incident has been resolved.

9 Sep 2026 04:30:49 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:39:18 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:36:40 (5 days ago)

Identified: We are continuing to work on a fix for this issue.

9 Sep 2026 00:29:20 (5 days ago)

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

8 Sep 2026 23:52:12 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 23:31:44 (5 days ago)

Investigating: We are continuing to investigate the issue.

8 Sep 2026 22:53:35 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 22:53:04 (5 days ago)

Investigating: We are currently investigating this issue.

8 Sep 2026 21:52:48 (6 days ago)

See all updates

FME

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Slowness in Prod1 and Prod2 environment

Started 8 Sep 2026 21:52:48 (6 days ago), resolved 9 Sep 2026 04:30:49 (5 days ago)

Minor Incident

Postmortem

Continuous Delivery (CD) - FirstGen - EOS

Continuous Delivery - Next Generation (CDNG)

Cloud Cost Management (CCM)

More...

We are currently investigating this issue.

Postmortem: ### Summary

On September 8, 2026, customers in Prod 1 and Prod 2 experienced elevated platform latency and pipeline failures. The issue was caused by a regression in a newly released capability that triggered cascading failures under high load. Because the capability was behind a feature flag, it was quickly disabled, and service was restored after a brief monitoring period.

Customer Impact

Customers encountered slowness and failures during pipeline execution and UI operations. Some API calls returned errors or timed out.
No data loss or corruption occurred.

Root Cause

The new capability introduced a regression that created contention on a shared backend resource used by multiple Harness components. This saturated the shared platform infrastructure and caused the cascading failures.

Mitigation

Disabled the capability across all environments
Temporarily increased platform capacity to restore stability

Next Steps

To prevent recurrence, Harness will:

Permanently fix the capability by profiling and eliminating the sub-optimal code path and query
Improve detection by enhancing alerting for resource-intensive queries on high-frequency platform paths

9 Sep 2026 23:23:46 (4 days ago)

Resolved: This incident has been resolved.

9 Sep 2026 04:30:49 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:39:18 (5 days ago)

Monitoring: A fix has been implemented and we are monitoring the results.

9 Sep 2026 00:36:40 (5 days ago)

Identified: We are continuing to work on a fix for this issue.

9 Sep 2026 00:29:20 (5 days ago)

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

8 Sep 2026 23:52:12 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 23:31:44 (5 days ago)

Investigating: We are continuing to investigate the issue.

8 Sep 2026 22:53:35 (5 days ago)

Investigating: We are continuing to investigate this issue.

8 Sep 2026 22:53:04 (5 days ago)

Investigating: We are currently investigating this issue.

8 Sep 2026 21:52:48 (6 days ago)

See all updates

Harness Prod 3

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Continuous Delivery (CD) - FirstGen - EOS

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Continuous Delivery - Next Generation (CDNG)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Cloud Cost Management (CCM)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Continuous Error Tracking (CET)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Continuous Integration Enterprise(CIE) - Self Hosted Runners

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Continuous Integration Enterprise(CIE) - Mac Cloud Builds

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Continuous Integration Enterprise(CIE) - Windows Cloud Builds

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Continuous Integration Enterprise(CIE) - Linux Cloud Builds

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Custom Dashboards

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Feature Flags (FF)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Security Testing Orchestration (STO)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Service Reliability Management (SRM)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Chaos Engineering

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Internal Developer Portal (IDP)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Infrastructure as Code Management (IaCM)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Software Supply Chain Assurance (SSCA)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Software Engineering Insights (SEI) / AI DLC Insights

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Code Repository

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Artifact Registry

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Platform

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

FME

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Harness Prod 4

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Continuous Delivery - Next Generation (CDNG)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Cloud Cost Management (CCM)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Continuous Error Tracking (CET)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Continuous Integration Enterprise(CIE) - Self Hosted Runners

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Harness Continuous Delivery - Next Generation (CDNG)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Harness Cloud Cost Management (CCM)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Continuous Integration Enterprise(CIE) - Mac Cloud Builds

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Continuous Integration Enterprise(CIE) - Windows Cloud Builds

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Harness Continuous Integration Enterprise(CIE) - Cloud Builds

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Continuous Integration Enterprise(CIE) - Linux Cloud Builds

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Harness Continuous Integration Enterprise(CIE) - Self Hosted Runners

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Custom Dashboards

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Harness Custom Dashboards

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Feature Flags (FF)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Harness Feature Flags (FF)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Security Testing Orchestration (STO)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Harness Security Testing Orchestration (STO)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Harness Service Reliability Management (SRM)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Service Reliability Management (SRM)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Chaos Engineering

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Harness Chaos Engineering

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Harness Internal Developer Portal (IDP)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Internal Developer Portal (IDP)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Harness Infrastructure as Code Management (IaCM)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Infrastructure as Code Management (IaCM)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Code Repository

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Artifact Registry

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Platform

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Harness Prod Eu 1

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Continuous Delivery - Next Generation (CDNG)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Chaos Engineering

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Cloud Cost Management (CCM)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Continuous Error Tracking (CET)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Continuous Integration Enterprise(CIE) - Self Hosted Runners

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Continuous Integration Enterprise(CIE) - Mac Cloud Builds

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Continuous Integration Enterprise(CIE) - Windows Cloud Builds

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Continuous Integration Enterprise(CIE) - Linux Cloud Builds

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Custom Dashboards

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Feature Flags (FF)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Security Testing Orchestration (STO)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Service Reliability Management (SRM)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Internal Developer Portal (IDP)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Infrastructure as Code Management (IaCM)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Software Engineering Insights (SEI) / AI DLC Insights

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Artifact Registry

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Platform

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Code Repository

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Harness Service Reliability Management - Error Tracking FirstGen (fka OverOps)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Harness Software Engineering Insights FirstGen (fka Propelo)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Software Engineering Insights FirstGen (fka Propelo) - EU

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Software Engineering Insights FirstGen (fka Propelo) - US

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Harness Traceable

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

US - app.traceable.ai / api.traceable.ai

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

EU - app.eu.traceable.ai / api.eu.traceable.ai

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

APAC - app.apac.traceable.ai / api.apac.traceable.ai

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

APAC2 - app.apac2.traceable.ai / api.apac2.traceable.ai

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

US1 - app.us1.traceable.ai / api.us1.traceable.ai / api2.us1.traceable.ai

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Canada - app.ca.traceable.ai / api.ca.traceable.ai

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Harness Feature Management & Experimentation (FME)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

SDK API

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Admin API

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Streaming service

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Management Console

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Data processing

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Integrations

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

CDN

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

API docs

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Harness Prod 7

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Continuous Delivery - Next Generation (CDNG)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Custom Dashboards

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Feature Flags (FF)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Platform

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Service Reliability Management (SRM)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Harness Prod 8

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Continuous Delivery - Next Generation (CDNG)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Platform

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Security Testing Orchestration (STO)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Custom Dashboards

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Software Supply Chain Assurance (SSCA)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Feature Flags (FF)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Harness Dev

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Continuous Delivery (CD) - FirstGen - EOS

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Testing Dev Status Page

Started 11 Sep 2026 14:22:14 (3 days ago), resolved 11 Sep 2026 14:22:14 (3 days ago)

Minor Incident

Resolved

Continuous Delivery (CD) - FirstGen - EOS

We are currently investigating this issue.

Continuous Delivery - Next Generation (CDNG)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Cloud Cost Management (CCM)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Continuous Error Tracking (CET)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Chaos Engineering

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Continuous Integration Enterprise(CIE) - Self Hosted Runners

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Continuous Integration Enterprise(CIE) - Mac Cloud Builds

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Continuous Integration Enterprise(CIE) - Windows Cloud Builds

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Continuous Integration Enterprise(CIE) - Linux Cloud Builds

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Custom Dashboards

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Feature Flags (FF)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Security Testing Orchestration (STO)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Service Reliability Management (SRM)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Internal Developer Portal (IDP)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Infrastructure as Code Management (IaCM)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Software Supply Chain Assurance (SSCA)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Software Engineering Insights (SEI)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Code Repository

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Artifact Registry

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Platform

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

AI Test Automation

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

FME

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Release Management

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Harness Prod 5

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Continuous Delivery - Next Generation (CDNG)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Custom Dashboards

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Feature Flags (FF)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Platform

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Harness Continuous Integration Enterprise(CIE) - Mac Cloud Builds

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Harness Prod 6

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Continuous Delivery (CD) - FirstGen - EOS

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Continuous Delivery - Next Generation (CDNG)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Cloud Cost Management (CCM)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Continuous Error Tracking (CET)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Chaos Engineering

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Continuous Integration Enterprise(CIE) - Self Hosted Runners

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Continuous Integration Enterprise(CIE) - Mac Cloud Builds

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Continuous Integration Enterprise(CIE) - Windows Cloud Builds

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Continuous Integration Enterprise(CIE) - Linux Cloud Builds

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Custom Dashboards

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Feature Flags (FF)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Security Testing Orchestration (STO)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Service Reliability Management (SRM)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Internal Developer Portal (IDP)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Infrastructure as Code Management (IaCM)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Software Supply Chain Assurance (SSCA)

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Software Engineering Insights (SEI) /AI DLC Insights

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Code Repository

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Artifact Registry

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Platform

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

AI Test Automation

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

FME

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Release Management

Mon 7

Tue 8

Wed 9

Thu 10

Fri 11

Sat 12

Sun 13

now

Harness Status

Real-time updates of Harness issues and outages

Harness status is Operational

Continuous Delivery (CD) - FirstGen - EOS

Continuous Delivery - Next Generation (CDNG)

Cloud Cost Management (CCM)

Continuous Error Tracking (CET)

Chaos Engineering

Feature Flags (FF)

FME

You're checking on Harness - but is your own site converting?

Active Incidents

Customer Impact

Root Cause

Mitigation

Next Steps

Recently Resolved Incidents

Harness Outage Survival Guide

Harness Components

Harness

Harness Prod 0

Harness Prod 1

Continuous Delivery (CD) - FirstGen - EOS

Customer Impact

Root Cause

Mitigation

Next Steps

Continuous Delivery - Next Generation (CDNG)

Customer Impact

Root Cause

Mitigation

Next Steps

Cloud Cost Management (CCM)

Customer Impact

Root Cause

Mitigation

Next Steps

Continuous Error Tracking (CET)

Customer Impact

Root Cause

Mitigation

Next Steps

Chaos Engineering

Customer Impact

Root Cause

Mitigation

Next Steps

Continuous Integration Enterprise(CIE) - Self Hosted Runners

Continuous Integration Enterprise(CIE) - Mac Cloud Builds

Continuous Integration Enterprise(CIE) - Windows Cloud Builds

Continuous Integration Enterprise(CIE) - Linux Cloud Builds

Custom Dashboards

Feature Flags (FF)

Customer Impact

Root Cause

Mitigation

Next Steps

Security Testing Orchestration (STO)

Service Reliability Management (SRM)

Internal Developer Portal (IDP)

Infrastructure as Code Management (IaCM)

Software Supply Chain Assurance (SSCA)

Software Engineering Insights (SEI) /AI DLC Insights

Code Repository

Artifact Registry

Platform

AI Test Automation

FME

Customer Impact

Root Cause

Mitigation

Next Steps

Release Management

Harness Prod 2

Continuous Delivery (CD) - FirstGen - EOS

Customer Impact

Root Cause

Mitigation

Next Steps

Continuous Delivery - Next Generation (CDNG)