User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
rescuetime.com · Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
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 1225 ms · 7 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 03:15 | 0 | 0.0 | 297 ms | 0 |
| 03:30 | 0 | 0.0 | 565 ms | 0 |
| 03:45 | 0 | 0.0 | 582 ms | 0 |
| 04:00 | 0 | 0.0 | 398 ms | 0 |
| 04:15 | 0 | 0.0 | 857 ms | 0 |
| 04:30 | 0 | 0.0 | 1522 ms | 0 |
| 04:45 | 0 | 0.0 | 237 ms | 0 |
| 05:00 | 0 | 0.0 | 181 ms | 0 |
| 05:15 | 0 | 0.0 | 893 ms | 0 |
| 05:30 | 0 | 0.0 | 486 ms | 0 |
| 05:45 | 0 | 0.0 | 607 ms | 0 |
| 06:00 | 0 | 0.0 | 185 ms | 0 |
| 06:15 | 0 | 0.0 | 443 ms | 0 |
| 06:30 | 0 | 0.0 | 915 ms | 0 |
| 06:45 | 0 | 0.0 | 656 ms | 0 |
| 07:00 | 0 | 0.0 | 3768 ms | 0 |
| 07:15 | 0 | 0.0 | 841 ms | 0 |
| 07:30 | 0 | 0.0 | 515 ms | 0 |
| 07:45 | 0 | 0.0 | 315 ms | 0 |
| 08:00 | 0 | 0.0 | 684 ms | 0 |
| 08:15 | 0 | 0.0 | 196 ms | 0 |
| 08:30 | 0 | 0.0 | 661 ms | 0 |
| 08:45 | 0 | 0.0 | 712 ms | 0 |
| 09:00 | 0 | 0.0 | 215 ms | 0 |
| 09:15 | 0 | 0.0 | 727 ms | 0 |
| 09:30 | 0 | 0.0 | 423 ms | 0 |
| 09:45 | 0 | 0.0 | 394 ms | 0 |
| 10:00 | 0 | 0.0 | 397 ms | 0 |
| 10:15 | 0 | 0.0 | 525 ms | 0 |
| 10:30 | 0 | 0.0 | 243 ms | 0 |
| 10:45 | 0 | 0.0 | 357 ms | 0 |
| 11:00 | 0 | 0.0 | 392 ms | 0 |
| 11:15 | 0 | 0.0 | 81 ms | 0 |
| 11:30 | 0 | 0.0 | 353 ms | 0 |
| 11:45 | 0 | 0.0 | 300 ms | 0 |
| 12:00 | 0 | 0.0 | 120 ms | 0 |
| 12:15 | 0 | 0.0 | 510 ms | 0 |
| 12:30 | 0 | 0.0 | 841 ms | 0 |
| 12:45 | 0 | 0.0 | 448 ms | 0 |
| 13:00 | 0 | 0.0 | 361 ms | 0 |
| 13:15 | 0 | 0.0 | 340 ms | 0 |
| 13:30 | 0 | 0.0 | 1225 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 RescueTime 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 RescueTime goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send RescueTime alerts to Slack, Discord or a webhook — free.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
If RescueTime is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on RescueTime's side.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.