UCSO Bot

Discord

Operational

Uptime

Every day the record holds, one column each. Hover a column for that day.

Operational Degraded Down 98.92% over 63 days

Jul 10Jul 25Aug 9Aug 24Sep 8Sep 23

How long each check took, averaged into buckets the range can hold.

24h7d30d

63ms

66ms

68ms

Mean response time by hour, across the last seven days.

00:0006:0012:0018:0023:59

SMTWTFS

The numbers above, said out loud.

Uptime is 98.92% across the record — 9.7h of it not fully operational.
The process behind this service restarted 15 times in the last 30 days. A restart completes far inside the agent's 30-second sampling interval, so it leaves no mark on the percentage above — it is counted here instead, because "nothing was ever recorded against it" and "it never went away" are not the same claim.
2 of the last 30 days were only partly recorded, the thinnest at 33% of the day. Those percentages are true of the hours the record was watching, not of the whole day, and their columns are hatched to say so.
5 status changes in the last 30 days, the most recent 6d ago.
Slowest around 15:00 at 69 ms, against 62 ms at 03:00 — steady across the day.

Probe results recorded per day, with the number of services reporting one.

Probes Services Not operational 454 probes · 1 service / day

Sep 8Sep 13Sep 18Sep 23Sep 28Oct 3

Every status change in the last 90 days. Stretches with nothing in them are collapsed to a marker.

5 changes in 90 days

6 quiet days
Oct 1
- 00:48 UCSO Bot unknown → operational
- 00:48 UCSO Bot down → unknown host is serving, but the monitoring agent has stopped reporting
- 00:35 UCSO Bot operational → down host offline — every site on it has stopped answering
3 quiet days
Sep 27
- 13:10 UCSO Bot down → operational
- 13:08 UCSO Bot operational → down host offline — every site on it has stopped answering
79 quiet days

Updated s ago Times in America/New York (UTC-04:00) Full record →