Company Logo

Is there an Split outage?

Split status: Systems Active

Last checked: 3 minutes ago

Get notified about any outages, downtime or incidents for Split and 1800+ other cloud vendors. Monitor 10 companies, for free.

Subscribe for updates

Split outages and incidents

Outage and incident data over the last 30 days for Split.

There have been 0 outages or incidents for Split in the last 30 days.

Severity Breakdown:

Tired of searching for status updates?

Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!

Sign Up Now

Components and Services Monitored for Split

Outlogger tracks the status of these components for Xero:

API Active
CDN Active
Corporate Site Active
Data Processing Active
Documentation Active
Integrations Active
SDK API Active
Streaming Authentication Service Active
Web Console Active
Component Status
API Active
CDN Active
Corporate Site Active
Data Processing Active
Documentation Active
Integrations Active
SDK API Active
Streaming Authentication Service Active
Web Console Active

Latest Split outages and incidents.

View the latest incidents for Split and check for official updates:

Updates:

  • Time: April 9, 2024, 10:37 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: April 9, 2024, 6:21 p.m.
    Status: Identified
    Update: We have identified an issue causing the S3 data ingestion to be delayed and are working on a fix.

Updates:

  • Time: March 27, 2024, 1:38 p.m.
    Status: Resolved
    Update: This issue has been resolved and all our systems are healthy. We thank you for your patience while our team addressed this.
  • Time: March 25, 2024, 8:57 p.m.
    Status: Monitoring
    Update: Our team detected the root cause for this issue in a high amount of variants for cached resources being created in certain scenarios. A fix has been implemented to ensure a more efficient caching strategy by reducing unwanted revalidation and preventing excessive variants for objects in entries critical for SDK initialization. All indicators are currently healthy and validate that the fix has effectively mitigated the issue. We continue to monitor the results.
  • Time: March 25, 2024, 6:22 p.m.
    Status: Identified
    Update: We detected a spike in 503 responses from our SDK API today between 15:04 and 15:06 GMT. Our team continues to work on a fix for this issue.
  • Time: March 25, 2024, 6:17 p.m.
    Status: Identified
    Update: We are investigating some usage patterns affecting our CDN and sporadically causing slightly elevated error rates during short periods of time in certain regions. This can lead to initialization timeouts for SDKs initializing from an empty cache. Running SDK instances are unaffected, and synchronization will continue to work without issues. All of our SDKs have built-in retry mechanisms which means they will automatically recover once the event is resolved, typically within minutes of the onset of the issue. Client side SDKs with a populated cache from a previous session are unaffected. Our mobile SDKs have persistent caching always enabled, and for our browser-based SDKs this can be enabled by setting the storage type to 'localstorage' through the SDK factory configuration (see: https://help.split.io/hc/en-us/articles/360020448791-JavaScript-SDK#configuration). In order to minimize any potential impact to our customers' apps, we highly recommend following our best practices by handling SDK initialization timeouts and control treatments. More information on best practices to build a resilient integration with Split can be found here: https://help.split.io/hc/en-us/articles/25255992258701-How-to-build-a-resilient-integration. Our team is currently working on a fix for to remediate this issue as a top priority, and it is expected to be deployed shortly. We at Split sincerely apologize for the impact caused to any customers who were affected by this issue, and thank you for your patience this week as our engineering team investigated and addressed it.

Updates:

  • Time: March 22, 2024, 8:34 p.m.
    Status: Resolved
    Update: We are investigating some usage patterns affecting our CDN and sporadically causing slightly elevated error rates during short periods of time in certain regions. This can lead to initialization timeouts for SDKs initializing from an empty cache. Running SDK instances are unaffected, and synchronization will continue to work without issues. All of our SDKs have built-in retry mechanisms which means they will automatically recover once the event is resolved, typically within minutes of the onset of the issue. Client side SDKs with a populated cache from a previous session are unaffected. Our mobile SDKs have persistent caching always enabled, and for our browser-based SDKs this can be enabled by setting the storage type to 'localstorage' through the SDK factory configuration (see: https://help.split.io/hc/en-us/articles/360020448791-JavaScript-SDK#configuration). In order to minimize any potential impact to our customers' apps, we highly recommend following our best practices by handling SDK initialization timeouts and control treatments. More information on best practices to build a resilient integration with Split can be found here: https://help.split.io/hc/en-us/articles/25255992258701-How-to-build-a-resilient-integration. Our team is currently working on a fix for to remediate this issue as a top priority, and it is expected to be deployed shortly. We at Split sincerely apologize for the impact caused to any customers who were affected by this issue, and thank you for your patience this week as our engineering team investigated and addressed it.

Updates:

  • Time: March 19, 2024, 9:18 p.m.
    Status: Resolved
    Update: Today our SDK API experienced a slightly elevated error rate between 4:13PM and 4:26PM GMT. During this period, some customers may have observed isolated SDK initialization timeouts. Any running SDK instances were unaffected.

Updates:

  • Time: Feb. 14, 2024, 1:13 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: Feb. 13, 2024, 11:53 p.m.
    Status: Monitoring
    Update: A fix has been implemented and we are monitoring the results.
  • Time: Feb. 13, 2024, 7:57 p.m.
    Status: Investigating
    Update: We are currently investigating an issue with 500 Errors from streaming.split.io.

Check the status of similar companies and alternatives to Split

Hudl
Hudl

Systems Active

OutSystems
OutSystems

Systems Active

Postman
Postman

Systems Active

Mendix
Mendix

Systems Active

DigitalOcean
DigitalOcean

Issues Detected

Bandwidth
Bandwidth

Systems Active

DataRobot
DataRobot

Systems Active

Grafana Cloud
Grafana Cloud

Systems Active

SmartBear Software
SmartBear Software

Systems Active

Test IO
Test IO

Systems Active

Copado Solutions
Copado Solutions

Systems Active

CircleCI
CircleCI

Systems Active

Frequently Asked Questions - Split

Is there a Split outage?
The current status of Split is: Systems Active
Where can I find the official status page of Split?
The official status page for Split is here
How can I get notified if Split is down or experiencing an outage?
To get notified of any status changes to Split, simply sign up to OutLogger's free monitoring service. OutLogger checks the official status of Split every few minutes and will notify you of any changes. You can veiw the status of all your cloud vendors in one dashboard. Sign up here
What does Split do?
Split is a platform that enables feature flag management, software experimentation, and continuous delivery for businesses.

Start monitoring now!

Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.

Get Started for Free