Split had 106 outages in the last 2 years totaling 438h 18m of downtime — averaging 4.4 incidents per month.
There were 106 Split outages since April 8, 2026 totaling 438h 18m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating an issue in EU1 where users are having issues using IACM module.
We have implemented a fix on our side which has resolved this issue. We are continuing to monitor this issue.
This incident has been resolved.
We are currently investigating an issue in Prod3 cluster where pipeline components are loading slower than expected.
A fix has been implemented in one of our microservice responsible for dealing with pipeline templates which has resolved the issue. We are continuing to monitor the issue.
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We seeing the backlogged items worked through and continuing to monitor results.
We are continuing to monitor results while the backlog is worked through.
This incident has been resolved.
Dev Statuspage incident - Testing
We are currently investigating this issue.
Harness is investigating an issue affecting our Prod 4 environments. Our log-services are affected and harness is currently working on restoring function. This can affect our CI, Chaos, IACM modules.
We are continuing to work on a fix for this issue.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently experiencing intermittent login issues with the Traceable cluster due to an issue with our login provider. We are actively working with the provider to resolve the issue. This incident does not impact data ingestion, and all ingestion pipelines continue to function normally. We will provide updates as we have more information.
The issue has been identified and a fix is being implemented.
Issue has been fixed and we are closely monitoring
We are continuing to monitor for any further issues.
This incident has been resolved.
Harness login is failing. We are investigating the problem.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We have identified an issue affecting a small subset of accounts in the EU1 region. As a result, data ingestion for impacted integrations may have stopped.
Testing Dev in QA
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
IDP Systems' communication was interrupted due to an update. Harness is rolling back changes. Impacted environments - prod0, prod1, prod2
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are investigating an issue affecting artifact downloads from Maven Central following recent rate-limiting changes implemented by Sonatype. Sonatype has recently implemented rate limits and builds downloading artifacts from central sonatype https://central.sonatype.org/faq/429-contact-support/. Customers downloading artifacts would be impacted. We are actively engaging with Sonatype to mitigate the issue here.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
Maven Central is rate-limiting requests originating from our us-central1 NAT egress IP. Other regions (us-west1, us-east5) are not affected. The Maven/Sonatype team has been engaged and is actively working on lifting the rate limit for our IP range.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently investigating this issue.
We are continually monitoring this issue.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Instability in streaming connections could cause a delay in propagating updates. All SDKs are designed to poll against the CDN on streaming disconnects and instability scenarios. This could also cause some noise in the logs as SDKs try to reconnect to streaming. But updates are unaffected.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Please ignore this incident.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating an slowness issue in pipeline execution ui.
Our investigation has revealed that the pipeline execution are happening as expected in the backend, The slowness is limited to updates in pipeline UI only.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We have received reports of slowness in Harness pipelines in Prod3 cluster. We are actively investigating this issue. Please monitor this space for further updates.
A fix has been implemented which resolved the pipeline slowness , we are currently monitoring the results.
This incident has been resolved. The incident was identified as a slowness on the UI updates for execution graph visualization. Executions were not impacted outside of the UI execution graph visualization.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
We have identified a potential issue causing the service access problem and are working hard to address it. Please continue to monitor this page for updates.
We can confirm normal operation, Slowness issue is resolved. We will publish the RCA
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.