Last updated: November 10, 2026
Is Split down? User reports show no current problems with Split
Split is a feature flag and experimentation platform that now runs inside Harness as Feature Management and Experimentation. Teams use it to release features safely and measure each change.
Report a problem !
Select which issue applies
Split problems reported in the last 24 hours
Most reported problems
All quiet. No issues reported in the last 24 hours.
Your feedback
How would you rate Split over the past 3 months?
Most reported locations
Where Split reports are coming from in the last 24 hours.
No problem locations to show yet. Split looks fine right now. Locations appear here as soon as users submit reports.
Latest Split user reports
No reports yet — be the first to report a problem above.
Split outage history
Our latest check and the live report status for Split.
✓ Our latest check (8 November 2026, 4:00 AM PKT): split.io answered normally in 277 ms.
Good news. Split has no reported problems right now. If it is not working for you, report it above and your report will appear here.
Split uptime and reports
Live report counts and the day by day record for the last 30 days.
User reports received in each period.
Last 30 days, day by day: 11 October 2026 to 9 November 2026
Green: up. Red: outage. Amber: some checks failed. Grey: no record yet.
The daily record builds from today as our checks run. Grey days have no saved record yet. A red day marks a confirmed outage.
Get Split down alerts
Leave your email and we will tell you when Split is having problems, and when it is back up. No spam.
Split on social media
An early signal from outside our site, watched in rotation.
Posts on Bluesky saying Split is down. Checked 8 November 2026, 1:44 PM PKT.
A few mentions. Nothing wide is going on.
- @quindimarlena.bsky.social 7 Nov, 11:37 PM PKT
I wish you had posted it to me for our elections! It's split down the middle and looks like we will have to wait for weeks for one side or the other to form a multiple-party coalition. 🙄 - @holyhollopenos.bsky.social 7 Nov, 10:52 PM PKT
BYU vs Utah — the Holy War kicks off at 11:00 AM CT. The pepper stadium is split down the middle and the referee is holding both halves apart. Who takes it? 🏈🌶 #HolyHollopenos - @hullitude.bsky.social 7 Nov, 3:40 PM PKT
If these results are telling me anything, its that NZ is split down the middle and sick of both sides
Guides that can fix it
Step by step fixes for the problems people report most.
→ An App Is Not Working? Fixes for Android and iPhone
→ Login Problems That Are Not an Outage
→ How to Clear the Cache in Firefox, Safari and Edge
Is Split Down Right Now?
No. Split is not down right now, but it has changed homes. Harness bought Split in June 2024, and the product now runs inside Harness as Feature Management and Experimentation, often shortened to FME.
This page tracks the Split status for teams still running the SDKs and flags. Use it to tell whether a Split outage is under way, or whether your keys, login, or migration state are the real problem.
Is Split Down for Me or Everyone?
A platform incident slows flag delivery for everyone on the service. Your code then serves cached or default treatments. That looks very different from one app returning the wrong flag because of a bad key or a mistyped flag name.
Ask whether Split is down for me or for the whole team. If the console loads and other services answer, test your SDK key type and flag name before blaming an outage.
Why Did the Old Split Console Stop Working?
The standalone console at app.split.io was folded into the Harness platform. Accounts were migrated, and the old address now sends users into Harness. Split is no longer sold as a separate product.
Your flags, segments, and experiments live on as FME feature flags. The SDK packages still carry the Split name, so working code did not need a rewrite for the move.
Why Is My Feature Flag Returning ‘control’?
The SDK returns control when it cannot evaluate the flag. It may still be starting up. It may hold a wrong or expired API key. Or the flag name in code may not match the console exactly.
Key type matters too. Server-side and client-side keys are not interchangeable. A browser app with a server key, or the reverse, fails in ways that look like an outage.
Why Aren’t My Flag Changes Showing Up?
Flag changes travel to SDKs by streaming or polling. A blocked streaming connection makes an app poll slowly instead. Corporate proxies and strict firewalls cause many of these silent delays.
Also check the boring causes. The flag may be killed, the environment may differ, or a targeting rule may send your test user to the default treatment on purpose.
Why Are Impressions or Experiment Metrics Missing?
Metrics depend on impressions reaching the service. Ad blockers, network rules, and misconfigured impression modes can drop them quietly. The flag still works, but the reports stay empty.
Experiments also need real traffic on each treatment. A flag shown to a handful of users produces no readable result, no matter how long you wait.
Common Split Problems and Fixes
SDK returns control for every flag
Wait for the SDK ready callback before evaluating. Then verify the API key value and type, and check that the flag name matches the console character for character.
Flag updates arrive minutes late
Allow the streaming connection through your proxy or firewall. If streaming stays blocked, shorten the polling interval in the SDK config as a fallback.
Login sends you to Harness
That is the migration working. Sign in to Harness and open the FME module. Your old Split workspaces appear there as projects and environments.
API key errors in the SDK logs
Generate a fresh key of the correct type in the admin settings. Client-side keys belong in browsers and mobile apps. Server keys must stay on your servers.
Experiment shows no results
Confirm impressions are enabled and arriving. Check that both treatments receive traffic, and that the metrics you track are attached to the experiment.
Having a problem with Split?
Comments are public and help others understand the issue.
Frequently Asked Questions
Is Split.io now part of Harness?
Yes. Harness completed its purchase of Split in June 2024. The product now runs as Harness Feature Management and Experimentation inside the Harness platform.
Why does getTreatment return control?
The SDK could not evaluate the flag. Common causes are a wrong API key, a flag name mismatch, or evaluating before the SDK finished starting.
What is the difference between server-side and client-side API keys in Split?
Server keys evaluate flags on your backend and can see every flag. Client keys are safe to ship in browsers and apps, and only expose flags marked for them.
How fast do Split flag changes reach my app?
With streaming working, changes arrive within seconds. If streaming is blocked, the SDK falls back to polling, and updates can take minutes.
Can I still use the Split SDK after the Harness move?
Yes. The existing SDKs and packages still work and are maintained under Harness. New signups and console work happen inside Harness as FME.
Why are my Split impressions not showing in the console?
Impressions may be blocked by network rules or turned down by the SDK impression mode. Check the SDK config and test from a network without ad blocking.