Split Help > Performance > What happens to my app if there's a Split service interruption?

What happens to my app if there's a Split service interruption?

Split was architected with a focus on performance, even in adverse conditions. Split's local SDKs mean it keeps serving features with no latency even when the connection breaks.

From the perspective of your users, our uptime is your uptime. Because Split SDKs are installed locally in your app, they continue to work as you'd expect. When your app becomes disconnected from the Split web console, it continues to serve features based on the last set of rollout plan instructions it received. 

Of course, if you aren't able to log into the Split web console, or if the connection is broken between the web console and your app, you'll be temporarily unable to make changes to your rollout plan until the connection is resolved, but your app will continue to behave as-normal in the meantime. 

Split's rollout plan instructions have three redundancies for the SDK: local cache, Fastly (our global CDN), and finally Split's AWS servers.

You can always check the status of Split's service at http://status.split.io.

Published June 1, 2017