User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps 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. Every report with a known place can appear on the map. Updates every minute.
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.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 5 min ago. Last stored result reached it in 187 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 02 | 0 | 0.0 | 1374 ms | 0 |
| Tue 04 | 0 | 0.0 | 1260 ms | 0 |
| Tue 06 | 0 | 0.0 | 865 ms | 0 |
| Tue 08 | 0 | 0.0 | 763 ms | 0 |
| Tue 10 | 0 | 0.0 | 822 ms | 0 |
| Tue 12 | 0 | 0.0 | 1782 ms | 0 |
| Tue 15 | 0 | 0.0 | 1377 ms | 0 |
| Tue 17 | 0 | 0.0 | 1660 ms | 0 |
| Tue 19 | 0 | 0.0 | 588 ms | 0 |
| Tue 22 | 0 | 0.0 | 1315 ms | 0 |
| Wed 00 | 0 | 0.0 | 1795 ms | 0 |
| Wed 02 | 0 | 0.0 | 1206 ms | 0 |
| Wed 04 | 0 | 0.0 | 868 ms | 0 |
| Wed 06 | 0 | 0.0 | 928 ms | 0 |
| Wed 09 | 0 | 0.0 | 388 ms | 0 |
| Wed 11 | 0 | 0.0 | 886 ms | 0 |
| Wed 13 | 0 | 0.0 | 1057 ms | 0 |
| Wed 15 | 0 | 0.0 | 1423 ms | 0 |
| Wed 17 | 0 | 0.0 | 980 ms | 0 |
| Wed 20 | 0 | 0.0 | 1447 ms | 0 |
| Wed 22 | 0 | 0.0 | 896 ms | 0 |
| Thu 00 | 0 | 0.0 | 768 ms | 0 |
| Thu 02 | 0 | 0.0 | 1213 ms | 0 |
| Thu 04 | 0 | 0.0 | 1130 ms | 0 |
| Thu 06 | 0 | 0.0 | 734 ms | 0 |
| Thu 08 | 0 | 0.0 | 1421 ms | 0 |
| Thu 10 | 0 | 0.0 | 853 ms | 0 |
| Thu 12 | 0 | 0.0 | 1214 ms | 0 |
| Thu 14 | 0 | 0.0 | 1193 ms | 0 |
| Thu 17 | 0 | 0.0 | 1084 ms | 0 |
| Thu 18 | 0 | 0.0 | 796 ms | 0 |
| Thu 20 | 0 | 0.0 | 985 ms | 0 |
| Thu 22 | 0 | 0.0 | 503 ms | 0 |
| Fri 00 | 0 | 0.0 | 870 ms | 0 |
| Fri 02 | 0 | 0.0 | 1103 ms | 0 |
| Fri 04 | 0 | 0.0 | 551 ms | 0 |
| Fri 06 | 0 | 0.0 | 1065 ms | 0 |
| Fri 08 | 0 | 0.0 | 708 ms | 0 |
| Fri 11 | 0 | 0.0 | 518 ms | 0 |
| Fri 13 | 0 | 0.0 | 985 ms | 0 |
| Fri 15 | 0 | 0.0 | 342 ms | 0 |
| Fri 17 | 0 | 0.0 | 982 ms | 0 |
| Fri 18 | 0 | 0.0 | 1195 ms | 0 |
| Fri 20 | 0 | 0.0 | 809 ms | 0 |
| Fri 22 | 0 | 0.0 | 1081 ms | 0 |
| Sat 00 | 0 | 0.0 | 1140 ms | 0 |
| Sat 02 | 0 | 0.0 | 516 ms | 0 |
| Sat 03 | 0 | 0.0 | 1656 ms | 0 |
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 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Reditus 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 Reditus goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Reditus alerts to Slack, Discord or a webhook — free.
Reditus is listed in our Productivity category and checked at getreditus.com. Grow the MRR for your B2B SaaS by leveraging the audience of someone else. Setup, manage & recruit B2B SaaS affiliates via Reditus. 14-day free trial.
Reditus publishes an official status page at status.getreditus.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with productivity services: files not syncing, editors not loading, and sign-in problems.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 839 ms average, 143–1656 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Reditus incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
839 ms on average over the last 24 hours (143–1656 ms).
Yes, at https://status.getreditus.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For productivity services, watch for files not syncing, editors not loading, and sign-in problems. If many people report Reditus here at once, the problem is on Reditus'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 Reditus. 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.