User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Money
doit.com · Money
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 764 ms · 6 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 03:30 | 0 | 0.0 | 475 ms | 0 |
| 03:45 | 0 | 0.0 | 1074 ms | 0 |
| 04:00 | 0 | 0.0 | 1166 ms | 0 |
| 04:15 | 0 | 0.0 | 720 ms | 0 |
| 04:30 | 0 | 0.0 | 1974 ms | 0 |
| 04:45 | 0 | 0.0 | 800 ms | 0 |
| 05:00 | 0 | 0.0 | 1066 ms | 0 |
| 05:15 | 0 | 0.0 | 1185 ms | 0 |
| 05:30 | 0 | 0.0 | 1856 ms | 0 |
| 05:45 | 0 | 0.0 | 489 ms | 0 |
| 06:00 | 0 | 0.0 | 1403 ms | 0 |
| 06:15 | 0 | 0.0 | 904 ms | 0 |
| 06:30 | 0 | 0.0 | 490 ms | 0 |
| 06:45 | 0 | 0.0 | 1049 ms | 0 |
| 07:00 | 0 | 0.0 | 938 ms | 0 |
| 07:15 | 0 | 0.0 | 903 ms | 0 |
| 07:30 | 0 | 0.0 | 1075 ms | 0 |
| 07:45 | 0 | 0.0 | 707 ms | 0 |
| 08:00 | 0 | 0.0 | 884 ms | 0 |
| 08:15 | 0 | 0.0 | 1004 ms | 0 |
| 08:30 | 0 | 0.0 | 1270 ms | 0 |
| 08:45 | 0 | 0.0 | 2160 ms | 0 |
| 09:00 | 0 | 0.0 | 802 ms | 0 |
| 09:15 | 0 | 0.0 | 1012 ms | 0 |
| 09:30 | 0 | 0.0 | 883 ms | 0 |
| 09:45 | 0 | 0.0 | 994 ms | 0 |
| 10:00 | 0 | 0.0 | 921 ms | 0 |
| 10:15 | 0 | 0.0 | 420 ms | 0 |
| 10:30 | 0 | 0.0 | 887 ms | 0 |
| 10:45 | 0 | 0.0 | 963 ms | 0 |
| 11:00 | 0 | 0.0 | 1492 ms | 0 |
| 11:15 | 0 | 0.0 | 708 ms | 0 |
| 11:30 | 0 | 0.0 | 1186 ms | 0 |
| 11:45 | 0 | 0.0 | 3704 ms | 0 |
| 12:00 | 0 | 0.0 | 3896 ms | 0 |
| 12:15 | 0 | 0.0 | 1432 ms | 0 |
| 12:30 | 0 | 0.0 | 2455 ms | 0 |
| 12:45 | 0 | 0.0 | 488 ms | 0 |
| 13:00 | 0 | 0.0 | 1730 ms | 0 |
| 13:15 | 0 | 0.0 | 961 ms | 0 |
| 13:30 | 0 | 0.0 | 980 ms | 0 |
| 13:45 | 0 | 0.0 | 1487 ms | 0 |
| 14:00 | 0 | 0.0 | 1492 ms | 0 |
| 14:15 | 0 | 0.0 | 974 ms | 0 |
| 14:30 | 0 | 0.0 | 819 ms | 0 |
| 14:45 | 0 | 0.0 | 2316 ms | 0 |
| 15:00 | 0 | 0.0 | 820 ms | 0 |
| 15:15 | 0 | 0.0 | 764 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 Doit 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 Doit goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Doit 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 Doit 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 Doit'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.