Terms of Service; Didn't Read Uptime History
Measured by PulsAPI's own checks, not reported by Terms of Service; Didn't Read. Every figure below is computed over the 90 days in the last 365 that PulsAPI actually observed, from 2026-08-08 to 2026-11-05. Days nobody watched are left out rather than counted as perfect.
Terms of Service; Didn't Read Uptime at a Glance
- Measured uptime
- 95.94%
- Days with an issue
- 9
- Longest outage
- —
- Mean recovery
- —
across 90 observed days
days were not fully operational
no resolved incident recorded
no resolved incident recorded
Monthly Terms of Service; Didn't Read Uptime
Each month is the mean of its observed days. The strongest month was November 2026 at 100.00%, the weakest October 2026 at 91.63%. Months with few observed days are marked, because a short month is not evidence of a good one.
| Month | Uptime | Uptime bar | Days observed |
|---|---|---|---|
| November 2026 | 100.00% | 5partial | |
| October 2026 | 91.63% | 31 | |
| September 2026 | 99.11% | 30 | |
| August 2026 | 96.70% | 24 |
Get an email when Terms of Service; Didn't Read moves
Every figure on this page came from a check we ran. Those same checks can reach your inbox the moment Terms of Service; Didn't Read stops being operational, so the next dip arrives as a notification rather than a row you find later.
Free, no password, no card. Unsubscribe in one click.
How This Terms of Service; Didn't Read Uptime Figure Is Measured
PulsAPI checks Terms of Service; Didn't Read continuously (every 60 seconds) and records the result. A day's uptime is the share of that day's checks that came back fully operational, so a 20-minute outage shows up as a dip rather than being rounded away. The window figure is the mean of those daily values.
Two things this deliberately is not. It is not Terms of Service; Didn't Read's own published uptime, because vendors generally measure against their own SLA definitions, which usually exclude scheduled maintenance and often exclude partial degradation. And it is not a promise about the future: 90 days of history describes what happened, and the useful way to read it is alongside the incidents behind the dips.
Uptime measured this way is a mean of component uptimes where a vendor publishes components, so coverage matters as much as the percentage. That is why the observed-day count sits beside every figure on this page rather than in a footnote.
These measurements are published under CC BY 4.0. Quote or republish them freely, with attribution to PulsAPI.