Split Outage History

Split is up right now

Split had 106 outages in the last 2 years totaling 50h 53m of downtime — averaging 4.4 incidents per month.

There were 106 Split outages since April 8, 2026 totaling 50h 53m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.split.io

Major May 12, 2026

Platform access issues in Prod1/Prod2/Prod3

Detected by Pingoru
May 12, 2026, 05:33 PM UTC
Resolved
May 12, 2026, 05:55 PM UTC
Duration
21m
Timeline · 5 updates
  1. investigating May 12, 2026, 05:33 PM UTC

    We are currently investigating this issue.

  2. investigating May 12, 2026, 05:37 PM UTC

    We are continuing to investigate this issue.

  3. identified May 12, 2026, 05:46 PM UTC

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

  4. monitoring May 12, 2026, 05:52 PM UTC

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

  5. resolved May 12, 2026, 05:55 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 12, 2026

Testing Dev Status Page incident

Detected by Pingoru
May 12, 2026, 09:19 AM UTC
Resolved
May 12, 2026, 02:04 PM UTC
Duration
4h 44m
Timeline · 2 updates
  1. investigating May 12, 2026, 09:19 AM UTC

    incident testing

  2. resolved May 12, 2026, 02:04 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 11, 2026

AI Summary Feature is not available across all Insights

Detected by Pingoru
May 11, 2026, 09:50 AM UTC
Resolved
May 11, 2026, 04:59 PM UTC
Duration
7h 8m
Timeline · 4 updates
  1. investigating May 11, 2026, 09:50 AM UTC

    We are currently investigating this issue.

  2. identified May 11, 2026, 09:51 AM UTC

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

  3. monitoring May 11, 2026, 04:58 PM UTC

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

  4. resolved May 11, 2026, 04:59 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 11, 2026

Delegate Upgrades are failing for some customers

Detected by Pingoru
May 11, 2026, 06:48 AM UTC
Resolved
May 11, 2026, 07:16 AM UTC
Duration
28m
Timeline · 4 updates
  1. investigating May 11, 2026, 06:48 AM UTC

    We are currently investigating this issue.

  2. identified May 11, 2026, 06:57 AM UTC

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

  3. monitoring May 11, 2026, 07:12 AM UTC

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

  4. resolved May 11, 2026, 07:16 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical May 7, 2026

Deployment Degradation - Slowness in Prod3

Detected by Pingoru
May 07, 2026, 08:00 AM UTC
Resolved
May 07, 2026, 12:54 PM UTC
Duration
4h 54m
Timeline · 8 updates
  1. investigating May 07, 2026, 09:08 AM UTC

    We are currently investigating this issue.

  2. investigating May 07, 2026, 10:19 AM UTC

    We are continuing to investigate this issue.

  3. identified May 07, 2026, 11:20 AM UTC

    We have identified the root cause as elevated queue depth and throughput saturation on the MongoDB layer, leading to processing latency. A fix is being implemented to optimize handling and restore database stability

  4. identified May 07, 2026, 12:06 PM UTC

    Executions are running fine now. However, there is still some slowness in the execution graph generation so we might see some delay in the execution updates to show up in UI. But executions would work without any delay/slowness.

  5. monitoring May 07, 2026, 12:09 PM UTC

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

  6. monitoring May 07, 2026, 12:12 PM UTC

    A fix has been implemented and we are monitoring the system.

  7. monitoring May 07, 2026, 12:12 PM UTC

    We are continuing to monitor for any further issues.

  8. resolved May 07, 2026, 12:54 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 7, 2026

Deployment Degradation – Failures in Prod1,2,3

Detected by Pingoru
May 07, 2026, 07:54 AM UTC
Resolved
May 07, 2026, 11:23 AM UTC
Duration
3h 29m
Timeline · 5 updates
  1. investigating May 07, 2026, 07:54 AM UTC

    CDS Deployment Failing in looping startegy

  2. investigating May 07, 2026, 08:17 AM UTC

    We are continuing to investigate this issue.

  3. investigating May 07, 2026, 08:43 AM UTC

    We are continuing to investigate this issue.

  4. monitoring May 07, 2026, 09:05 AM UTC

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

  5. resolved May 07, 2026, 11:23 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 6, 2026

AI Summary Feature Unavailable in SEI Insights

Detected by Pingoru
May 06, 2026, 04:12 PM UTC
Resolved
May 06, 2026, 04:25 PM UTC
Duration
13m
Timeline · 2 updates
  1. investigating May 06, 2026, 04:12 PM UTC

    We are currently investigating an issue where the AI Summary feature in the Harness SEI module is not available across all Insights. Our engineering team is actively working to restore the functionality as quickly as possible. We will share further updates as more information becomes available.

  2. resolved May 06, 2026, 04:25 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 5, 2026

K8s Customer Billing Data will be outdated

Detected by Pingoru
May 05, 2026, 07:57 AM UTC
Resolved
May 05, 2026, 08:17 AM UTC
Duration
19m
Timeline · 2 updates
  1. investigating May 05, 2026, 07:57 AM UTC

    We are currently experiencing an issue, K8s customer billing data will be stale.

  2. resolved May 05, 2026, 08:17 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 1, 2026

Prod3 experiences slowness in pipelines

Detected by Pingoru
May 01, 2026, 04:28 PM UTC
Resolved
May 01, 2026, 08:10 PM UTC
Duration
3h 41m
Timeline · 6 updates
  1. investigating May 01, 2026, 04:28 PM UTC

    We are currently investigating this issue.

  2. monitoring May 01, 2026, 04:56 PM UTC

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

  3. monitoring May 01, 2026, 05:14 PM UTC

    We are continuing to monitor for any further issues.

  4. monitoring May 01, 2026, 05:15 PM UTC

    We are continuing to monitor for any further issues.

  5. monitoring May 01, 2026, 07:58 PM UTC

    We are largely mitigated and most pipelines are running normally. We are monitoring all parameters to make sure there are no issues before closing it.

  6. resolved May 01, 2026, 08:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 1, 2026

Intermittent slowness during pipeline executions (Prod1, Prod2)

Detected by Pingoru
May 01, 2026, 03:02 PM UTC
Resolved
May 01, 2026, 08:10 PM UTC
Duration
5h 8m
Timeline · 4 updates
  1. investigating May 01, 2026, 03:02 PM UTC

    We are currently investigating this issue.

  2. monitoring May 01, 2026, 03:37 PM UTC

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

  3. monitoring May 01, 2026, 07:58 PM UTC

    We are largely mitigated and most pipelines are running normally. We are monitoring all parameters to make sure there are no issues before closing it.

  4. resolved May 01, 2026, 08:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 30, 2026

FF (Classic) some API's have elevated latencies in prod2

Detected by Pingoru
Apr 30, 2026, 11:09 PM UTC
Resolved
Apr 30, 2026, 11:43 PM UTC
Duration
33m
Timeline · 4 updates
  1. investigating Apr 30, 2026, 11:09 PM UTC

    We are currently investigating this issue.

  2. identified Apr 30, 2026, 11:19 PM UTC

    Issue has been identified and fix is underway

  3. monitoring Apr 30, 2026, 11:29 PM UTC

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

  4. resolved Apr 30, 2026, 11:43 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 28, 2026

Rule Base Segment supported SDKs timeout (FME Only)

Detected by Pingoru
Apr 28, 2026, 06:27 PM UTC
Resolved
Apr 28, 2026, 06:27 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Apr 28, 2026, 09:48 PM UTC

    Requests made by SDKs with Rule Based Segments support could have gotten a null instead of an empty for responses with no Rule Based Segments, leading to an null pointer exception. Impact observed: 18:27 until 19:05 UTC. The impact for SDKs would have been a failure to initialize or process an update. Any change made to feature flags or RBS in an affected environment would re-generate any specific caches remaining.

Read the full incident report →

Minor April 28, 2026

Scheduled change request delayed for a subset of flags

Detected by Pingoru
Apr 28, 2026, 05:21 PM UTC
Resolved
Apr 28, 2026, 05:21 PM UTC
Duration
—
Timeline · 1 update
  1. resolved May 02, 2026, 12:01 AM UTC

    Between April 28 and May 1, 2026, a subset of scheduled change requests failed to execute at their scheduled times. The issue was introduced by a production deployment on April 28 and fixed with a new deployment on May 1. All affected scheduled jobs that had not been manually withdrawn by customers have since been executed successfully.

Read the full incident report →

Minor April 24, 2026

Degraded Performance — Feature Flags in PROD2

Detected by Pingoru
Apr 24, 2026, 04:06 PM UTC
Resolved
Apr 24, 2026, 06:59 PM UTC
Duration
2h 52m
Timeline · 3 updates
  1. investigating Apr 24, 2026, 07:16 PM UTC

    We are currently investigating this issue.

  2. monitoring Apr 24, 2026, 07:29 PM UTC

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

  3. resolved Apr 24, 2026, 08:01 PM UTC

    This incident has been resolved.

Read the full incident report →

Major April 19, 2026

IACM infrastructure pipelines using terraform are currently experiencing an outage

Detected by Pingoru
Apr 19, 2026, 02:09 PM UTC
Resolved
Apr 19, 2026, 03:24 PM UTC
Duration
1h 15m
Timeline · 4 updates
  1. investigating Apr 19, 2026, 02:09 PM UTC

    We are currently investigating this issue.

  2. identified Apr 19, 2026, 02:20 PM UTC

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

  3. monitoring Apr 19, 2026, 03:17 PM UTC

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

  4. resolved Apr 19, 2026, 03:24 PM UTC

    This incident has been resolved. Customers using a pinned version older than plugins/harness_terraform:0.214.0 should update to the latest version by following the https://developer.harness.io/docs/continuous-integration/use-ci/set-up-build-infrastructure/harness-ci/#specify-the-harness-ci-images-used-in-your-pipelines. If you are not pinning a specific version, no action is required — your pipelines are already using the updated image.

Read the full incident report →