User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Productivity
Is Terms of Service; Didn't Read down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → tosdr.org—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 1 hr ago. Last stored result reached it in 1005 ms.
Official status
All clear
No active incidents in the official feed Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 12:45 | 0 | 0.0 | 738 ms | 0 |
| 14:30 | 0 | 0.0 | 821 ms | 0 |
| 16:45 | 0 | 0.0 | 168 ms | 0 |
| 19:00 | 0 | 0.0 | 56 ms | 0 |
| 21:30 | 0 | 0.0 | 157 ms | 0 |
| 23:45 | 0 | 0.0 | 109 ms | 0 |
| 02:00 | 0 | 0.0 | 868 ms | 0 |
| 04:30 | 0 | 0.0 | 221 ms | 0 |
| 06:45 | 0 | 0.0 | 40 ms | 0 |
| 07:15 | 0 | 0.0 | 797 ms | 0 |
| 09:15 | 0 | 0.0 | 68 ms | 0 |
| 11:15 | 0 | 0.0 | 1005 ms | 0 |
Reliability
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 10 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Terms of Service; Didn't Read badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
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
Having trouble with Terms of Service; Didn't Read?
One report per service every 10 minutes from this network. No account.
Follow Terms of Service; Didn't Read
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.
About Terms of Service; Didn't Read
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 10 days of checks. No public incidents logged since monitoring began 10 days ago.
Response time over the last 24 hours: 421 ms average, 40–1005 ms range across 12 successful checks.
Questions
Is Terms of Service; Didn't Read down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Terms of Service; Didn't Read last down?
We have not recorded a public Terms of Service; Didn't Read incident since monitoring began 10 days ago.
What is Terms of Service; Didn't Read's uptime?
From our own checks: 100% over 10 days of checks.
How fast does Terms of Service; Didn't Read respond?
421 ms on average over the last 24 hours (40–1005 ms).
Does Terms of Service; Didn't Read have an official status page?
Yes, at https://status.tosdr.org.
Terms of Service; Didn't Read not working for me but the status is fine. What now?
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.