User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
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 9 min ago. Last stored result reached it in 821 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 15 | 0 | 0.0 | 832 ms | 0 |
| Mon 17 | 0 | 0.0 | 830 ms | 0 |
| Mon 19 | 0 | 0.0 | 1075 ms | 0 |
| Mon 21 | 0 | 0.0 | 735 ms | 0 |
| Mon 23 | 0 | 0.0 | 749 ms | 0 |
| Tue 01 | 0 | 0.0 | 943 ms | 0 |
| Tue 03 | 0 | 0.0 | 751 ms | 0 |
| Tue 05 | 0 | 0.0 | 812 ms | 0 |
| Tue 08 | 0 | 0.0 | 1496 ms | 0 |
| Tue 10 | 0 | 0.0 | 960 ms | 0 |
| Tue 12 | 0 | 0.0 | 892 ms | 0 |
| Tue 14 | 0 | 0.0 | 903 ms | 0 |
| Tue 16 | 0 | 0.0 | 873 ms | 0 |
| Tue 19 | 0 | 0.0 | 641 ms | 0 |
| Tue 21 | 0 | 0.0 | 986 ms | 0 |
| Tue 23 | 0 | 0.0 | 780 ms | 0 |
| Wed 01 | 0 | 0.0 | 805 ms | 0 |
| Wed 04 | 0 | 0.0 | 839 ms | 0 |
| Wed 06 | 0 | 0.0 | 807 ms | 0 |
| Wed 08 | 0 | 0.0 | 702 ms | 0 |
| Wed 10 | 0 | 0.0 | 781 ms | 0 |
| Wed 13 | 0 | 0.0 | 798 ms | 0 |
| Wed 15 | 0 | 0.0 | 928 ms | 0 |
| Wed 17 | 0 | 0.0 | 1226 ms | 0 |
| Wed 19 | 0 | 0.0 | 910 ms | 0 |
| Wed 21 | 0 | 0.0 | 865 ms | 0 |
| Wed 23 | 0 | 0.0 | 772 ms | 0 |
| Thu 02 | 0 | 0.0 | 721 ms | 0 |
| Thu 04 | 0 | 0.0 | 1408 ms | 0 |
| Thu 06 | 0 | 0.0 | 692 ms | 0 |
| Thu 08 | 0 | 0.0 | 839 ms | 0 |
| Thu 10 | 0 | 0.0 | 812 ms | 0 |
| Thu 12 | 0 | 0.0 | 726 ms | 0 |
| Thu 14 | 0 | 0.0 | 914 ms | 0 |
| Thu 16 | 0 | 0.0 | 1271 ms | 0 |
| Thu 18 | 0 | 0.0 | 986 ms | 0 |
| Thu 20 | 0 | 0.0 | 724 ms | 0 |
| Thu 22 | 0 | 0.0 | 794 ms | 0 |
| Fri 00 | 0 | 0.0 | 771 ms | 0 |
| Fri 02 | 0 | 0.0 | 862 ms | 0 |
| Fri 04 | 0 | 0.0 | 849 ms | 0 |
| Fri 06 | 0 | 0.0 | 845 ms | 0 |
| Fri 08 | 0 | 0.0 | 770 ms | 0 |
| Fri 11 | 0 | 0.0 | 731 ms | 0 |
| Fri 13 | 0 | 0.0 | 748 ms | 0 |
| Fri 15 | 0 | 0.0 | 979 ms | 0 |
| Fri 17 | 0 | 0.0 | 841 ms | 0 |
| Fri 18 | 0 | 0.0 | 768 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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Otus 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 Otus goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Otus alerts to Slack, Discord or a webhook — free.
Otus, at otus.com, is one of the Cloud & developer services we monitor. Otus combines data, assessment, progress monitoring, and grading to maximize student performance and save educators time.
Otus publishes an official status page at status.otus.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: 815 ms average, 713–1038 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 Otus incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
815 ms on average over the last 24 hours (713–1038 ms).
Yes, at https://status.otus.com.
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 Otus here at once, the problem is on Otus'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 Otus. 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.