User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
splitwise.com · Cloud & developer
Is Splitwise down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → splitwise.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
Live outage map
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
What's broken
Recent reports
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
Our checks
Reaching it
Last checked 1 hr ago. Last stored result reached it in 339 ms.
Official status
All clear
All systems operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 341 ms | 0 |
| Nov 7 | 0 | 0.0 | 406 ms | 0 |
| Nov 7 | 0 | 0.0 | 113 ms | 0 |
| Nov 7 | 0 | 0.0 | 317 ms | 0 |
| Nov 7 | 0 | 0.0 | 222 ms | 0 |
| Nov 8 | 0 | 0.0 | 234 ms | 0 |
| Nov 8 | 0 | 0.0 | 325 ms | 0 |
| Nov 8 | 0 | 0.0 | 186 ms | 0 |
| Nov 8 | 0 | 0.0 | 137 ms | 0 |
| Nov 9 | 0 | 0.0 | 163 ms | 0 |
| Nov 9 | 0 | 0.0 | 322 ms | 0 |
| Nov 9 | 0 | 0.0 | 229 ms | 0 |
| Nov 9 | 0 | 0.0 | 253 ms | 0 |
| Nov 10 | 0 | 0.0 | 291 ms | 0 |
| Nov 10 | 0 | 0.0 | 245 ms | 0 |
| Nov 10 | 0 | 0.0 | 138 ms | 0 |
| Nov 10 | 0 | 0.0 | 203 ms | 0 |
| Nov 11 | 0 | 0.0 | 189 ms | 0 |
| Nov 11 | 0 | 0.0 | 322 ms | 0 |
| Nov 11 | 0 | 0.0 | 308 ms | 0 |
| Nov 11 | 0 | 0.0 | 151 ms | 0 |
| Nov 12 | 0 | 0.0 | 295 ms | 0 |
| Nov 12 | 0 | 0.0 | 220 ms | 0 |
| Nov 12 | 0 | 0.0 | 117 ms | 0 |
| Nov 12 | 0 | 0.0 | 298 ms | 0 |
| Nov 13 | 0 | 0.0 | 157 ms | 0 |
| Nov 13 | 0 | 0.0 | 339 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Splitwise badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Splitwise yet. Outages of 10 minutes or more get their own page here.
Having trouble with Splitwise?
One report per service every 10 minutes from this network. No account.
Follow Splitwise
Get an email when Splitwise goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Splitwise alerts to Slack, Discord or a webhook — free.
About Splitwise
We track Splitwise (splitwise.com) as part of the Cloud & developer group. Splitwise is a free tool for friends and roommates to track bills and other shared expenses, so that everyone gets paid back. On the web, iPhone, and Android!
Splitwise publishes an official status page at status.splitwise.com; when we can read it, its incident level is folded into the status shown here.
Common problems for cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 246 ms average, 111–457 ms range across 12 successful checks.
Questions
Is Splitwise down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Splitwise last down?
We have not recorded a public Splitwise incident since monitoring began 8 days ago.
What is Splitwise's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Splitwise respond?
246 ms on average over the last 24 hours (111–457 ms).
Does Splitwise have an official status page?
Yes, at https://status.splitwise.com.
Splitwise not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Splitwise here at once, the problem is on Splitwise's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Splitwise. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.