Split Outage History

Split is up right now

Split had 48 outages in the last 2 years totaling 245h 15m of downtime — averaging 2 incidents per month.

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

Source: https://status.split.io

Minor June 17, 2026

IDP Workflows and Backend failures

Detected by Pingoru
Jun 17, 2026, 04:44 PM UTC
Resolved
Jun 17, 2026, 05:50 PM UTC
Duration
1h 6m
Timeline · 5 updates
  1. investigating Jun 17, 2026, 04:44 PM UTC

    We are currently investigating this issue.

  2. identified Jun 17, 2026, 04:45 PM UTC

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

  3. identified Jun 17, 2026, 04:45 PM UTC

    IDP Systems' communication was interrupted due to an update. Harness is rolling back changes. Impacted environments - prod0, prod1, prod2

  4. monitoring Jun 17, 2026, 04:47 PM UTC

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

  5. resolved Jun 17, 2026, 05:50 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 17, 2026

Cloud builds are failing with 429 Too Many Requests error while downloading artifacts from central sonatype registry.

Detected by Pingoru
Jun 17, 2026, 01:42 PM UTC
Resolved
Jun 17, 2026, 05:13 PM UTC
Duration
3h 30m
Timeline · 6 updates
  1. investigating Jun 17, 2026, 01:42 PM UTC

    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.

  2. identified Jun 17, 2026, 02:03 PM UTC

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

  3. monitoring Jun 17, 2026, 02:21 PM UTC

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

  4. monitoring Jun 17, 2026, 03:21 PM UTC

    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.

  5. monitoring Jun 17, 2026, 04:12 PM UTC

    We are continuing to monitor for any further issues.

  6. resolved Jun 17, 2026, 05:13 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 5, 2026

Intermittent 503s on IDP services

Detected by Pingoru
Jun 05, 2026, 10:56 PM UTC
Resolved
Jun 06, 2026, 12:30 AM UTC
Duration
1h 34m
Timeline · 3 updates
  1. investigating Jun 05, 2026, 10:56 PM UTC

    We are currently investigating this issue.

  2. monitoring Jun 06, 2026, 12:01 AM UTC

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

  3. resolved Jun 06, 2026, 12:30 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 4, 2026

FME SDKs - SDKs falling back to polling

Detected by Pingoru
Jun 04, 2026, 02:33 PM UTC
Resolved
Jun 04, 2026, 04:38 PM UTC
Duration
2h 4m
Timeline · 3 updates
  1. identified Jun 04, 2026, 02:33 PM UTC

    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.

  2. monitoring Jun 04, 2026, 03:13 PM UTC

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

  3. resolved Jun 04, 2026, 04:38 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 2, 2026

Testing Dev Status Page 3rd June

Detected by Pingoru
Jun 02, 2026, 06:58 PM UTC
Resolved
Jun 02, 2026, 08:08 PM UTC
Duration
1h 10m
Timeline · 3 updates
  1. investigating Jun 02, 2026, 06:58 PM UTC

    Please ignore this incident.

  2. identified Jun 02, 2026, 07:16 PM UTC

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

  3. resolved Jun 02, 2026, 08:08 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 1, 2026

Hosted CI Builds Failing Intermittently

Detected by Pingoru
Jun 01, 2026, 10:01 AM UTC
Resolved
Jun 01, 2026, 01:47 PM UTC
Duration
3h 45m
Timeline · 3 updates
  1. investigating Jun 01, 2026, 10:01 AM UTC

    We are currently investigating this issue.

  2. monitoring Jun 01, 2026, 11:05 AM UTC

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

  3. resolved Jun 01, 2026, 01:47 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 21, 2026

Prod3 pipeline execution UI slowness

Detected by Pingoru
May 21, 2026, 01:55 PM UTC
Resolved
May 21, 2026, 04:34 PM UTC
Duration
2h 38m
Timeline · 5 updates
  1. investigating May 21, 2026, 01:55 PM UTC

    We are currently investigating an slowness issue in pipeline execution ui.

  2. investigating May 21, 2026, 02:15 PM UTC

    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.

  3. identified May 21, 2026, 02:33 PM UTC

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

  4. monitoring May 21, 2026, 02:49 PM UTC

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

  5. resolved May 21, 2026, 04:34 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 20, 2026

Prod3 Pipeline UI Updates on execution graph slowness

Detected by Pingoru
May 20, 2026, 10:48 AM UTC
Resolved
May 20, 2026, 12:38 PM UTC
Duration
1h 49m
Timeline · 3 updates
  1. investigating May 20, 2026, 10:48 AM UTC

    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.

  2. monitoring May 20, 2026, 11:52 AM UTC

    A fix has been implemented which resolved the pipeline slowness , we are currently monitoring the results.

  3. resolved May 20, 2026, 12:38 PM UTC

    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.

Read the full incident report →

Minor May 15, 2026

Custom Dashboards are failing intermittently in prod3

Detected by Pingoru
May 15, 2026, 08:35 PM UTC
Resolved
May 17, 2026, 05:37 AM UTC
Duration
1d 9h
Timeline · 4 updates
  1. investigating May 15, 2026, 08:35 PM UTC

    We are currently investigating this issue.

  2. monitoring May 15, 2026, 08:59 PM UTC

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

  3. monitoring May 17, 2026, 05:36 AM UTC

    We are continuing to monitor for any further issues.

  4. resolved May 17, 2026, 05:37 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 15, 2026

IACM Pipeline Struck In Prod4

Detected by Pingoru
May 15, 2026, 04:54 AM UTC
Resolved
May 21, 2026, 04:34 PM UTC
Duration
6d 11h
Timeline · 4 updates
  1. investigating May 15, 2026, 04:54 AM UTC

    We are currently investigating this issue.

  2. monitoring May 15, 2026, 05:14 AM UTC

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

  3. monitoring May 15, 2026, 05:23 AM UTC

    We are continuing to monitor for any further issues.

  4. resolved May 21, 2026, 04:34 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 14, 2026

Pipeline Updates in Prod4 is taking time.

Detected by Pingoru
May 14, 2026, 01:36 PM UTC
Resolved
May 14, 2026, 02:10 PM UTC
Duration
34m
Timeline · 6 updates
  1. investigating May 14, 2026, 01:36 PM UTC

    We are currently investigating this issue.

  2. investigating May 14, 2026, 01:39 PM UTC

    We are continuing to investigate this issue.

  3. investigating May 14, 2026, 01:40 PM UTC

    We are continuing to investigate this issue.

  4. identified May 14, 2026, 02:03 PM UTC

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

  5. monitoring May 14, 2026, 02:08 PM UTC

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

  6. resolved May 14, 2026, 02:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 14, 2026

Traceable APAC Cluster Slowness

Detected by Pingoru
May 14, 2026, 10:57 AM UTC
Resolved
May 14, 2026, 11:13 AM UTC
Duration
15m
Timeline · 3 updates
  1. investigating May 14, 2026, 10:57 AM UTC

    We are currently investigating this issue.

  2. identified May 14, 2026, 11:00 AM UTC

    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.

  3. resolved May 14, 2026, 11:13 AM UTC

    We can confirm normal operation, Slowness issue is resolved. We will publish the RCA

Read the full incident report →

Minor May 12, 2026

Hosted CI customers using secure connect are facing connectivity issues

Detected by Pingoru
May 12, 2026, 09:38 PM UTC
Resolved
May 12, 2026, 11:10 PM UTC
Duration
1h 32m
Timeline · 4 updates
  1. investigating May 12, 2026, 09:38 PM UTC

    We are currently investigating this issue.

  2. identified May 12, 2026, 09:40 PM UTC

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

  3. monitoring May 12, 2026, 10:50 PM UTC

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

  4. resolved May 12, 2026, 11:10 PM UTC

    This incident has been resolved.

Read the full incident report →

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 →