User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Health
loseit.com · Health
Checks are succeeding and user reports are near the baseline.
Live diagnosis
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.
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.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 41 ms · 7 min ago.
No status feed
Lose It! does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 12:30 | 0 | 0.0 | 144 ms | 0 |
| 12:45 | 0 | 0.0 | 445 ms | 0 |
| 13:00 | 0 | 0.0 | 134 ms | 0 |
| 13:15 | 0 | 0.0 | 237 ms | 0 |
| 13:30 | 0 | 0.0 | 113 ms | 0 |
| 13:45 | 0 | 0.0 | 366 ms | 0 |
| 14:00 | 0 | 0.0 | 132 ms | 0 |
| 14:15 | 0 | 0.0 | 82 ms | 0 |
| 14:30 | 0 | 0.0 | 79 ms | 0 |
| 14:45 | 0 | 0.0 | 192 ms | 0 |
| 15:00 | 0 | 0.0 | 134 ms | 0 |
| 15:15 | 0 | 0.0 | 491 ms | 0 |
| 15:30 | 0 | 0.0 | 431 ms | 0 |
| 15:45 | 0 | 0.0 | 114 ms | 0 |
| 16:00 | 0 | 0.0 | 184 ms | 0 |
| 16:15 | 0 | 0.0 | 453 ms | 0 |
| 16:30 | 0 | 0.0 | 118 ms | 0 |
| 16:45 | 0 | 0.0 | 146 ms | 0 |
| 17:00 | 0 | 0.0 | 143 ms | 0 |
| 17:15 | 0 | 0.0 | 314 ms | 0 |
| 17:30 | 0 | 0.0 | 298 ms | 0 |
| 17:45 | 0 | 0.0 | 448 ms | 0 |
| 18:00 | 0 | 0.0 | 73 ms | 0 |
| 18:15 | 0 | 0.0 | 621 ms | 0 |
| 18:30 | 0 | 0.0 | 564 ms | 0 |
| 18:45 | 0 | 0.0 | 240 ms | 0 |
| 19:00 | 0 | 0.0 | 69 ms | 0 |
| 19:15 | 0 | 0.0 | 505 ms | 0 |
| 19:30 | 0 | 0.0 | 193 ms | 0 |
| 19:45 | 0 | 0.0 | 339 ms | 0 |
| 20:00 | 0 | 0.0 | 111 ms | 0 |
| 20:15 | 0 | 0.0 | 266 ms | 0 |
| 20:30 | 0 | 0.0 | 149 ms | 0 |
| 20:45 | 0 | 0.0 | 241 ms | 0 |
| 21:00 | 0 | 0.0 | 397 ms | 0 |
| 21:15 | 0 | 0.0 | 367 ms | 0 |
| 21:30 | 0 | 0.0 | 302 ms | 0 |
| 21:45 | 0 | 0.0 | 85 ms | 0 |
| 22:00 | 0 | 0.0 | 148 ms | 0 |
| 22:15 | 0 | 0.0 | 298 ms | 0 |
| 22:30 | 0 | 0.0 | 69 ms | 0 |
| 22:45 | 0 | 0.0 | 152 ms | 0 |
| 23:00 | 0 | 0.0 | 49 ms | 0 |
| 23:15 | 0 | 0.0 | 432 ms | 0 |
| 23:30 | 0 | 0.0 | 41 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Lose It! yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Lose It! goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Lose It! alerts to Slack, Discord or a webhook — free.
Lose It!, at loseit.com, is one of the Health services we monitor. Live checks and user reports.
Lose It! has no official status feed we can read, so this page relies on our own checks and user reports.
Typical issues with health services: patient portal and member sign-in failures, prescription refills or appointment booking not going through, and app errors.
Measured uptime from our checks: 100% over 1 day of checks. No public incidents logged since monitoring began 1 day ago.
Response time over the last 24 hours: 252 ms average, 41–1032 ms range across 82 successful checks.
Checks are succeeding and user reports are near the baseline.
We have not recorded a public Lose It! incident since monitoring began 1 day ago.
From our own checks: 100% over 1 day of checks.
252 ms on average over the last 24 hours (41–1032 ms).
Not one we can read. This page uses independent checks of loseit.com and user reports.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For health services, watch for patient portal and member sign-in failures, prescription refills or appointment booking not going through, and app errors. If many people report Lose It! here at once, the problem is on Lose It!'s side.