Split Outage History

Split is up right now

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

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

Source: https://status.split.io

Minor April 16, 2026

We are noticing CI hosted build failures

Detected by Pingoru
Apr 16, 2026, 07:15 AM UTC
Resolved
Apr 16, 2026, 12:02 PM UTC
Duration
4h 46m
Timeline · 5 updates
  1. investigating Apr 16, 2026, 10:06 AM UTC

    We are currently investigating this issue.

  2. identified Apr 16, 2026, 10:14 AM UTC

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

  3. identified Apr 16, 2026, 11:08 AM UTC

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

  4. monitoring Apr 16, 2026, 11:41 AM UTC

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

  5. resolved Apr 16, 2026, 12:02 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 15, 2026

Feature Flags unable to update

Detected by Pingoru
Apr 15, 2026, 11:55 PM UTC
Resolved
Apr 16, 2026, 04:15 AM UTC
Duration
4h 20m
Timeline · 4 updates
  1. investigating Apr 15, 2026, 11:55 PM UTC

    We are currently investigating this issue.

  2. investigating Apr 16, 2026, 12:01 AM UTC

    We are continuing to investigate this issue.

  3. monitoring Apr 16, 2026, 04:04 AM UTC

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

  4. resolved Apr 16, 2026, 06:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 13, 2026

FME metrics impact calculations are not updating

Detected by Pingoru
Apr 13, 2026, 04:47 PM UTC
Resolved
Apr 13, 2026, 05:31 PM UTC
Duration
43m
Timeline · 2 updates
  1. monitoring Apr 13, 2026, 04:47 PM UTC

    Feature flag metrics impact calculations were not updating. This issue does not impact experiment calculation. Fix is being rolled out. There is no data loss.

  2. resolved Apr 13, 2026, 05:31 PM UTC

    After monitoring post fixing the issue, all systems are back to normal and processing metrics impact calculations regularly. We will provide an RCA soon.

Read the full incident report →

Minor April 9, 2026

Legacy Run Test step is failing intermittently for all customers in Prod2

Detected by Pingoru
Apr 09, 2026, 05:30 AM UTC
Resolved
Apr 09, 2026, 10:48 AM UTC
Duration
5h 18m
Timeline · 4 updates
  1. investigating Apr 09, 2026, 08:34 AM UTC

    Some of the legacy run test step connectivity to test intel service is failing intermittently. We are currently investigating the issue here.

  2. identified Apr 09, 2026, 09:38 AM UTC

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

  3. monitoring Apr 09, 2026, 10:38 AM UTC

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

  4. resolved Apr 09, 2026, 10:48 AM UTC

    This incident has been resolved.

Read the full incident report →

Major April 9, 2026

Prod1 and Prod2 is facing login issues

Detected by Pingoru
Apr 09, 2026, 01:05 AM UTC
Resolved
Apr 09, 2026, 02:42 AM UTC
Duration
1h 36m
Timeline · 4 updates
  1. investigating Apr 09, 2026, 01:43 AM UTC

    We are currently investigating this issue.

  2. identified Apr 09, 2026, 02:02 AM UTC

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

  3. monitoring Apr 09, 2026, 02:33 AM UTC

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

  4. resolved Apr 09, 2026, 02:42 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 8, 2026

Experiencing issues impacting pipeline executions in Prod1

Detected by Pingoru
Apr 08, 2026, 01:09 PM UTC
Resolved
Apr 08, 2026, 03:00 PM UTC
Duration
1h 51m
Timeline · 3 updates
  1. investigating Apr 08, 2026, 01:09 PM UTC

    We are currently investigating this issue.

  2. monitoring Apr 08, 2026, 01:54 PM UTC

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

  3. resolved Apr 08, 2026, 07:44 PM UTC

    This incident has been resolved.

Read the full incident report →