Case study1 min read
How to get a real 100% availability in Uptime Kuma without nightly false positives
Project period: Sep 2026Duration: 4 days

In short
Scheduled shutdowns of printers and displays drag down the availability reported by Uptime Kuma. Here is how to structure maintenance windows to keep corporate metrics clean.
Monitoring network printers and meeting-room displays is a headache for any systems administrator.
In an infrastructure with 33 monitors configured in Uptime Kuma, three belonged to two multifunction printers and a Smart TV in the meeting room. At the end of the workday, these devices go to sleep or are switched off.
At 7:05 p.m., Uptime Kuma would start firing downtime notifications. The next morning, the monthly availability report showed 91.2%. Presenting that figure meant unnecessary explanations: “No, the network did not go down; the printers were switched off overnight.”
The goal of monitoring is not to alert on the obvious, but to detect unwanted anomalies.
The solution: recurring maintenance windows
Instead of removing these peripherals from monitoring or disabling their alerts, two automated maintenance windows were scheduled:
- Daily night window (Monday to Friday): from 7:00 p.m. to 7:00 a.m. (12 hours of scheduled rest).
- Weekend window: from Friday 7:00 p.m. to Monday 7:00 a.m. (60 continuous hours).
During these periods, Uptime Kuma switches the monitor’s status to MAINTENANCE: it does not wait for a response from the device, it silences the notification webhooks and, most importantly, it excludes those hours from the availability formula.
The result
Of the network’s 33 monitors:
- 30 monitors stay active (200 OK / nominal ping).
- 3 monitors go into maintenance according to working hours.
- 0 outages recorded.
Overall availability now accurately reflects the real 100.0% uptime of the servers, links, switches and cameras.
Collaborations
Projects, research or ideas worth building together.