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 3 min ago. Last stored result reached it in 187 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 |
|---|---|---|---|---|
| Mon 07 | 0 | 0.0 | 353 ms | 0 |
| Mon 09 | 0 | 0.0 | 192 ms | 0 |
| Mon 11 | 0 | 0.0 | 322 ms | 0 |
| Mon 13 | 0 | 0.0 | 234 ms | 0 |
| Mon 15 | 0 | 0.0 | 109 ms | 0 |
| Mon 17 | 0 | 0.0 | 229 ms | 0 |
| Mon 19 | 0 | 0.0 | 256 ms | 0 |
| Mon 21 | 0 | 0.0 | 125 ms | 0 |
| Mon 23 | 0 | 0.0 | 335 ms | 0 |
| Tue 02 | 0 | 0.0 | 323 ms | 0 |
| Tue 04 | 0 | 0.0 | 258 ms | 0 |
| Tue 06 | 0 | 0.0 | 139 ms | 0 |
| Tue 08 | 0 | 0.0 | 336 ms | 0 |
| Tue 10 | 0 | 0.0 | 310 ms | 0 |
| Tue 12 | 0 | 0.0 | 138 ms | 0 |
| Tue 14 | 0 | 0.0 | 382 ms | 0 |
| Tue 17 | 0 | 0.0 | 126 ms | 0 |
| Tue 19 | 0 | 0.0 | 180 ms | 0 |
| Tue 21 | 0 | 0.0 | 193 ms | 0 |
| Tue 23 | 0 | 0.0 | 397 ms | 0 |
| Wed 02 | 0 | 0.0 | 178 ms | 0 |
| Wed 04 | 0 | 0.0 | 200 ms | 0 |
| Wed 06 | 0 | 0.0 | 322 ms | 0 |
| Wed 08 | 0 | 0.0 | 213 ms | 0 |
| Wed 11 | 0 | 0.0 | 369 ms | 0 |
| Wed 13 | 0 | 0.0 | 223 ms | 0 |
| Wed 15 | 0 | 0.0 | 308 ms | 0 |
| Wed 17 | 0 | 0.0 | 412 ms | 0 |
| Wed 19 | 0 | 0.0 | 152 ms | 0 |
| Wed 21 | 0 | 0.0 | 149 ms | 0 |
| Thu 00 | 0 | 0.0 | 105 ms | 0 |
| Thu 02 | 0 | 0.0 | 425 ms | 0 |
| Thu 04 | 0 | 0.0 | 295 ms | 0 |
| Thu 06 | 0 | 0.0 | 220 ms | 0 |
| Thu 08 | 0 | 0.0 | 360 ms | 0 |
| Thu 10 | 0 | 0.0 | 168 ms | 0 |
| Thu 12 | 0 | 0.0 | 111 ms | 0 |
| Thu 14 | 0 | 0.0 | 117 ms | 0 |
| Thu 16 | 0 | 0.0 | 245 ms | 0 |
| Thu 18 | 0 | 0.0 | 298 ms | 0 |
| Thu 20 | 0 | 0.0 | 214 ms | 0 |
| Thu 22 | 0 | 0.0 | 336 ms | 0 |
| Fri 00 | 0 | 0.0 | 148 ms | 0 |
| Fri 03 | 0 | 0.0 | 457 ms | 0 |
| Fri 05 | 0 | 0.0 | 157 ms | 0 |
| Fri 07 | 0 | 0.0 | 339 ms | 0 |
| Fri 09 | 0 | 0.0 | 187 ms | 0 |
| Fri 10 | 0 | 0.0 | 233 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: 237 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?
237 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.