OS End of Life
See in time when support for a device's operating system ends, based on endoflife.date.
The OS End of Life check tells you how long the operating system on a device is still supported. The octoja agent works out which operating system and release the device runs, looks that release up in the public endoflife.date catalog, and reports two lifecycle dates: when active/mainstream support ends and when extended support (security updates only) ends. Choose which phase drives alerting, whether to warn before it ends, and which status to report afterwards.
The check runs on Windows, macOS, and Linux every 12 hours; the interval is not user-configurable. Everything about the operating system is read on the device itself. The only outbound request is the lookup against endoflife.date, which the agent performs; the device needs no extra software and you enter nothing about which OS it runs. Because it only reads the OS version and makes one lookup, the check adds no meaningful load to the device.
Prerequisites
- The agent must reach endoflife.date over HTTPS. On a device with no outbound internet access the lookup fails and the check reports a failure rather than a status.
Settings
Both thresholds count backwards from the end date of the support phase you select. If you set the warning value lower than the critical value, the check swaps the two so the wider window always raises the warning first.
For information-only reporting, turn off Alert before support ends and set Support phase ended to OK, then save the check. Lifecycle dates remain visible; detection problems and failed API lookups still report warnings or failures. Turning off pre-expiry alerts alone leaves the status after support ends unchanged.
The check always reads both lifecycle phases; the alert basis only decides which one drives the check result. The other phase's date stays visible on the result card. Not every release has two distinct phases in the catalog. Where endoflife.date publishes a single lifecycle date — macOS, for example — both rows show that same date and the alert basis makes no practical difference.
Results
What the check reports
What the statuses mean
In every message, the phase is the one you picked as the alert basis — Active/mainstream support or Extended support (security updates only).
End-of-life dates come from endoflife.date and follow the vendor's published lifecycle. The only exception: if a commercial ESU license (Extended Security Updates, year 1 to 3) is activated on a device running Windows 10 22H2, the check uses the end of the licensed ESU year as the end of extended support.
When the check can't run
These outcomes are about the check itself, not a verdict on the device. The first three raise a warning so you notice a gap in coverage; the last two are check failures, usually a temporary network problem.
Platform support
Related articles
Was this helpful?
Still need help? Ask the team