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 8 min ago. Last stored result reached it in 723 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Thu 22 | 0 | 0.0 | 126 ms | 0 |
| Fri 00 | 0 | 0.0 | 67 ms | 0 |
| Fri 02 | 0 | 0.0 | 1126 ms | 0 |
| Fri 04 | 0 | 0.0 | 169 ms | 0 |
| Fri 07 | 0 | 0.0 | 1490 ms | 0 |
| Fri 09 | 0 | 0.0 | 213 ms | 0 |
| Fri 10 | 0 | 0.0 | 452 ms | 0 |
| Fri 12 | 0 | 0.0 | 712 ms | 0 |
| Fri 14 | 0 | 0.0 | 70 ms | 0 |
| Fri 16 | 0 | 0.0 | 85 ms | 0 |
| Fri 18 | 0 | 0.0 | 765 ms | 0 |
| Fri 19 | 0 | 0.0 | 756 ms | 0 |
| Fri 21 | 0 | 0.0 | 70 ms | 0 |
| Fri 22 | 0 | 0.0 | 54 ms | 0 |
| Sat 00 | 0 | 0.0 | 426 ms | 0 |
| Sat 02 | 0 | 0.0 | 645 ms | 0 |
| Sat 04 | 0 | 0.0 | 811 ms | 0 |
| Sat 06 | 0 | 0.0 | 975 ms | 0 |
| Sat 08 | 0 | 0.0 | 971 ms | 0 |
| Sat 10 | 0 | 0.0 | 772 ms | 0 |
| Sat 12 | 0 | 0.0 | 738 ms | 0 |
| Sat 14 | 0 | 0.0 | 821 ms | 0 |
| Sat 16 | 0 | 0.0 | 168 ms | 0 |
| Sat 19 | 0 | 0.0 | 56 ms | 0 |
| Sat 21 | 0 | 0.0 | 157 ms | 0 |
| Sat 23 | 0 | 0.0 | 109 ms | 0 |
| Sun 02 | 0 | 0.0 | 868 ms | 0 |
| Sun 04 | 0 | 0.0 | 221 ms | 0 |
| Sun 06 | 0 | 0.0 | 40 ms | 0 |
| Sun 07 | 0 | 0.0 | 797 ms | 0 |
| Sun 09 | 0 | 0.0 | 68 ms | 0 |
| Sun 11 | 0 | 0.0 | 1005 ms | 0 |
| Sun 13 | 0 | 0.0 | 676 ms | 0 |
| Sun 16 | 0 | 0.0 | 825 ms | 0 |
| Sun 18 | 0 | 0.0 | 724 ms | 0 |
| Sun 19 | 0 | 0.0 | 89 ms | 0 |
| Sun 20 | 0 | 0.0 | 127 ms | 0 |
| Sun 21 | 0 | 0.0 | 117 ms | 0 |
| Sun 22 | 0 | 0.0 | 871 ms | 0 |
| Mon 00 | 0 | 0.0 | 873 ms | 0 |
| Mon 01 | 0 | 0.0 | 103 ms | 0 |
| Mon 02 | 0 | 0.0 | 730 ms | 0 |
| Mon 04 | 0 | 0.0 | 156 ms | 0 |
| Mon 05 | 0 | 0.0 | 189 ms | 0 |
| Mon 07 | 0 | 0.0 | 847 ms | 0 |
| Mon 09 | 0 | 0.0 | 1017 ms | 0 |
| Mon 11 | 0 | 0.0 | 723 ms | 0 |
| Mon 13 | 0 | 0.0 | 101 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 11 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Terms of Service; Didn't Read yet. Outages of 10 minutes or more get their own page here.
All Terms of Service; Didn't Read outages · Every recent outage
One report per service every 10 minutes from this network. No account.
Get an email when Terms of Service; Didn't Read goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send confirmed down and recovery alerts to Slack, Discord or a webhook — free. Early warnings are part of Owner Alerts.
Terms of Service; Didn't Read, at tosdr.org, is one of the Productivity services we monitor. 'I have read and agree to the Terms' is the biggest lie on the web. Together, we can fix that.
Terms of Service; Didn't Read publishes an official status page at status.tosdr.org; 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 11 days of checks. No public incidents logged since monitoring began 11 days ago.
Response time over the last 24 hours: 529 ms average, 89–1017 ms range across 17 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Terms of Service; Didn't Read incident since monitoring began 11 days ago.
From our own checks: 100% over 11 days of checks.
529 ms on average over the last 24 hours (89–1017 ms).
Yes, at https://status.tosdr.org.
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 Terms of Service; Didn't Read here at once, the problem is on Terms of Service; Didn't Read'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 Terms of Service; Didn't Read. 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.