Is Split down?

Last checked 4m ago
Current status
Split is up

No incidents right now.

Get alerts when Split breaks →

Free · no credit card

Official status page: https://status.split.io · Polled every 5 minutes · 13 components tracked

Real-time Split status, recent outages, and incident history — pulled directly from Split's official status page at https://status.split.io every 5 minutes. Pingoru tracks 13 Split services and has captured 24 incidents in the last 90 days (98.76% uptime). Get email, Slack, Discord, or webhook alerts the moment Split reports a new incident — free for 5 monitors, no credit card.

Users who monitor Split also follow these Development services: Bitbucket OpenAI Datadog US1 Sentry NPM Travis CI Postman Pusher Pendo SonarCloud View all 6,000+ providers
Split uptime 98.76% uptime · past 90 days
Mon Wed Fri
JanFebMarApr
Less More

Recent outages & incidents

Past 7 days
  1. Rule Base Segment supported SDKs timeout (FME Only)
    Resolved —
    Started Apr 28, 2026, 09:48 PM UTC · Resolved Apr 28, 2026, 06:27 PM UTC
    1 update · show timeline
    • resolved · Apr 28, 2026, 09:48 PM UTC

      Requests made by SDKs with Rule Based Segments support could have gotten a null instead of an empty for responses with no Rule Based Segments, leading to an null pointer exception. Impact observed: 18:27 until 19:05 UTC. The impact for SDKs would have been a failure to initialize or process an update. Any change made to feature flags or RBS in an affected environment would re-generate any specific caches remaining.

    Latest: Requests made by SDKs with Rule Based Segments support could have gotten a null instead of an empty for responses with no Rule Based Segments, leading to an null pointer exception.…

  2. Testing Dev Status Page Degradation Testing
    Resolved 3h 30m
    Started Apr 28, 2026, 03:28 PM UTC · Resolved Apr 28, 2026, 06:58 PM UTC
    1 update · show timeline
    • investigating · Apr 28, 2026, 03:28 PM UTC

      We are currently investigating this issue.

    Latest: We are currently investigating this issue.

  3. Testing Dev Status Page Adjusting to test the Active incident length
    Resolved 2h 25m
    Started Apr 28, 2026, 11:51 AM UTC · Resolved Apr 28, 2026, 02:16 PM UTC
    2 updates · show timeline
    • investigating · Apr 28, 2026, 11:51 AM UTC

      We are currently investigating this issue.

    • monitoring · Apr 28, 2026, 12:14 PM UTC

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

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

  4. Intermittent slowness while running pipelines
    Resolved —
    Started Apr 27, 2026, 10:27 PM UTC · Resolved Apr 27, 2026, 08:00 PM UTC
    1 update · show timeline
    • resolved · Apr 27, 2026, 10:27 PM UTC

      We were seeing slowness while executing pipelines

    Latest: We were seeing slowness while executing pipelines

  5. CI pipelines using cache intelligence are seeing degraded performance.
    Resolved 19m
    Started Apr 27, 2026, 04:05 PM UTC · Resolved Apr 27, 2026, 04:24 PM UTC
    3 updates · show timeline
    • investigating · Apr 27, 2026, 04:05 PM UTC

      We are currently investigating this issue.

    • identified · Apr 27, 2026, 04:08 PM UTC

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

    • resolved · Apr 27, 2026, 04:24 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

See the full Split outage history

11 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Sign up free to unlock full history

10 free monitors · No credit card

Outage history

Past 30 days · 16 incidents
  • Rule Base Segment supported SDKs timeout (FME Only) Resolved
    Started Apr 28, 2026, 09:48 PM UTC · Resolved Apr 28, 2026, 06:27 PM UTC · —
  • Testing Dev Status Page Degradation Testing Resolved
    Started Apr 28, 2026, 03:28 PM UTC · Resolved Apr 28, 2026, 06:58 PM UTC · 3h 30m
  • Testing Dev Status Page Adjusting to test the Active incident length Resolved
    Started Apr 28, 2026, 11:51 AM UTC · Resolved Apr 28, 2026, 02:16 PM UTC · 2h 25m
  • Intermittent slowness while running pipelines Resolved
    Started Apr 27, 2026, 10:27 PM UTC · Resolved Apr 27, 2026, 08:00 PM UTC · —
  • CI pipelines using cache intelligence are seeing degraded performance. Resolved
    Started Apr 27, 2026, 04:05 PM UTC · Resolved Apr 27, 2026, 04:24 PM UTC · 19m
  • Degraded Performance — Feature Flags in PROD2 Resolved
    Started Apr 24, 2026, 04:06 PM UTC · Resolved Apr 24, 2026, 06:59 PM UTC · 2h 52m
  • Testing Dev Status Page Resolved
    Started Apr 24, 2026, 05:23 AM UTC · Resolved Apr 24, 2026, 05:43 AM UTC · 19m
  • Testing Dev Status Page Resolved
    Started Apr 21, 2026, 08:12 PM UTC · Resolved Apr 21, 2026, 09:02 PM UTC · 49m

See Split in your Pingoru dashboard

Monitor Split alongside every other service your stack depends on — same alerts, same timeline, same calendar — all in one place.

Every status page, one dashboard

Add Split to your Pingoru monitors and it sits next to AWS, Stripe, GitHub, and every other vendor in your stack — a single dashboard for the live status of every cloud and SaaS provider you depend on. One subscription, one inbox, every incident.

Incident timeline, this provider or all of them

Every Split incident — when it started, when it resolved, which services were affected, how bad it was, how long it lasted — laid out in one feed you can scan in 30 seconds. Filter to just Split or see every provider at once.

Maintenance calendar

Scheduled Split maintenance windows land in the same calendar as every other vendor you depend on — see what's running now, what's coming up, and a calendar view. Plan around your vendors instead of being caught out by them.

Every Split status change, one inbox

Pingoru watches Split's official status page every 5 minutes and delivers incident, resolution, and maintenance events to your email, Slack, Discord, Teams, or webhook.

Only alert on the services you use

Split reports on 13 services. Subscribe to the ones you actually use — everything else stays silent.

Email + Slack + Discord + Teams

Signed webhooks on every plan. Route Split alerts wherever your team already lives — no per-integration billing, no tier-gating the channels that matter.

Maintenance, not surprises

Upcoming Split maintenance windows appear in your maintenance calendar days in advance. Plan deploys and rollouts around them instead of finding out during an incident.

Fine-grained alert control

Per-monitor switches for opened, updated, resolved, and maintenance events. Silence the noisy Split services without silencing the monitor entirely.

Invite your team

Premium includes 10 team seats. Everyone watching Split from the same account, with per-user notification preferences for any monitor.

Get notified on Split status changes

Pingoru watches Split's official status page and sends your team instant alerts when incidents open, change severity, or resolve. Route notifications to email, Slack, Discord, or a webhook — wherever your team already lives.

Start monitoring Split free

Monitor Split along with everything else

Pingoru tracks 6,000+ cloud and SaaS status pages in one dashboard. Add Split and every other provider you depend on — AWS, Stripe, GitHub, Cloudflare, OpenAI — and get a single view of the health of every service your app depends on.

Browse the full service directory

Track Split uptime & incident history

See 90 days of Split uptime at a glance, with every past incident linked to its component and update timeline. Export the history as CSV or JSON for SLA reports, postmortems, or vendor evaluations — data your team actually needs, not marketing numbers.

See Split uptime history

Frequently asked questions

What is Split's uptime?
Over the last 90 days, Split reported 98.76% uptime on its official status page. That figure is calculated from the public incident timeline at https://status.split.io — each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see Split's uptime history rolling forward in real time.
Has Split had outages in 2026?
Yes — Split has had 24 incidents reported on its official status page so far in 2026. The full timeline (start times, durations, components affected) is shown above on this page. Pingoru re-checks the status page every 5 minutes so the count stays current.
When was the last Split outage?
The most recent Split incident was "Testing Dev Maintenance 1234", which started on April 29, 2026 and was resolved on April 28, 2026. Pingoru captured this directly from https://status.split.io. See the full incident card above for affected components and the update timeline.
How often does Split have outages?
Based on the last 90 days, Split averages 8.0 reported incidents per month on its official status page. Pingoru tracks each one with start time, duration, severity, and affected components — so you can see the pattern at a glance instead of digging through the vendor's archive.
Where is Split's status page?
Split's official status page is https://status.split.io. Pingoru polls it every 5 minutes and renders the same data here, alongside every other cloud or SaaS provider you depend on — so you can spot multi-vendor incidents (e.g. AWS + Stripe + Cloudflare degrading at the same minute) without flipping between tabs.
Is Split down right now?
Split is up. Pingoru checks the official status page every 5 minutes and flips this headline the moment Split reports a change. Current status is based on 13 tracked services.
How does Pingoru know if Split is down?
We read https://status.split.io directly, using Split's own status page. If the vendor reports an incident, you see it within one check cycle — not after someone manually marks the page as down.
Where can I get notified when Split has an outage?
Create a free Pingoru account and add Split as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.
Split's status page says the service is up, but I'm having issues — what's wrong?
Three common reasons: • A real Split incident that hasn't been acknowledged on their public status page yet — vendor status pages are updated manually and typically lag the first customer reports by 10–30 minutes. • A regional or account-scoped issue affecting a subset of customers — these rarely trigger a global status-page change. • A local problem: ISP / DNS / your own software. Try reproducing from a mobile data connection and from a different network to isolate. If you suspect a real Split issue that isn't reflected yet, contact their support to escalate. Subscribing here means you get the alert the moment they do post an update.
Where does Pingoru get the official Split status?
We use Split's own status page at https://status.split.io. Nothing is read in a way the vendor hasn't explicitly made public — we use the same data their own dashboard uses. So our data is as accurate as what you'd see loading the status page yourself, but rolled into one dashboard alongside every other service you depend on.
What does "Up" mean?
All tracked Split components are reporting operational. No incidents are currently affecting service.

Stop finding out from your users.

We watch Split's official status page every 5 minutes. The moment they report an incident, you get an email — often before the outage is widely noticed.

Monitor Split free →

10 monitors free · email alerts · no credit card

Want the full picture first? See everything Pingoru does →