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 17 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 |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 78 ms | 0 |
| Nov 7 | 0 | 0.0 | 674 ms | 0 |
| Nov 7 | 0 | 0.0 | 800 ms | 0 |
| Nov 7 | 0 | 0.0 | 861 ms | 0 |
| Nov 7 | 0 | 0.0 | 110 ms | 0 |
| Nov 8 | 0 | 0.0 | 214 ms | 0 |
| Nov 8 | 0 | 0.0 | 780 ms | 0 |
| Nov 8 | 0 | 0.0 | 738 ms | 0 |
| Nov 8 | 0 | 0.0 | 212 ms | 0 |
| Nov 9 | 0 | 0.0 | 696 ms | 0 |
| Nov 9 | 0 | 0.0 | 166 ms | 0 |
| Nov 9 | 0 | 0.0 | 833 ms | 0 |
| Nov 9 | 0 | 0.0 | 266 ms | 0 |
| Nov 10 | 0 | 0.0 | 223 ms | 0 |
| Nov 10 | 0 | 0.0 | 219 ms | 0 |
| Nov 10 | 0 | 0.0 | 776 ms | 0 |
| Nov 10 | 0 | 0.0 | 136 ms | 0 |
| Nov 11 | 0 | 0.0 | 345 ms | 0 |
| Nov 11 | 0 | 0.0 | 230 ms | 0 |
| Nov 11 | 0 | 0.0 | 693 ms | 0 |
| Nov 11 | 0 | 0.0 | 91 ms | 0 |
| Nov 12 | 0 | 0.0 | 137 ms | 0 |
| Nov 12 | 0 | 0.0 | 704 ms | 0 |
| Nov 12 | 0 | 0.0 | 312 ms | 0 |
| Nov 12 | 0 | 0.0 | 126 ms | 0 |
| Nov 13 | 0 | 0.0 | 169 ms | 0 |
| Nov 13 | 0 | 0.0 | 543 ms | 0 |
| Nov 13 | 0 | 0.0 | 85 ms | 0 |
| Nov 13 | 0 | 0.0 | 413 ms | 0 |
| Nov 14 | 0 | 0.0 | 696 ms | 0 |
| Nov 14 | 0 | 0.0 | 971 ms | 0 |
| Nov 14 | 0 | 0.0 | 738 ms | 0 |
| Nov 14 | 0 | 0.0 | 109 ms | 0 |
| Nov 15 | 0 | 0.0 | 545 ms | 0 |
| Nov 15 | 0 | 0.0 | 433 ms | 0 |
| Nov 15 | 0 | 0.0 | 754 ms | 0 |
| Nov 15 | 0 | 0.0 | 127 ms | 0 |
| Nov 16 | 0 | 0.0 | 189 ms | 0 |
| Nov 16 | 0 | 0.0 | 847 ms | 0 |
| Nov 16 | 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.