Can You Beat A 16-Year Device Uptime?

A few years back, a story went viral when a guy had to decommission his old server. The uptime was 16 years. 16 years, equivalent to 6014 days 5 hours and 21 minutes. Has one of your servers beaten this long-lived machine? Do you remember when long uptimes were a badge of honor? If you look at something like that now, imagine how horribly out of date and vulnerable it must be. Back in the day, uptime was a testament to how reliable the hardware and software were. Today, you’d rather have fully patched and up-to-date devices. For those who do still like to show off their uptime milestones from time to time, this subreddit might be a fun read. You can discover your devices’ uptime in seconds with this built-in Lansweeper report: Assets: Uptime since last reboot. You can find this report in our report library or in the reports tab of your Lansweeper web console by searching “Uptime”. Uptime info is scanned for Linux, Unix, Mac, Windows, VMware & SNMP devices. We also have our asset uptime calendar for devices. If you haven’t already, download a free trial of Lansweeper to run the report and check which devices in your network might need a reboot.

Get Your Hands on the Latest Network Reports for Free

"*" indicates required fields

Email*

Hidden

EmailType

Hidden

IM – Conv Page – Processing

Hidden

IM – UTM_Campaign FC – Processing

Hidden

IM – UTM_Campaign LC – Processing

Hidden

IM – UTM_Content FC – Processing

Hidden

IM – UTM_Content LC – Processing

Hidden

IM – UTM_Medium FC – Processing

Hidden

IM – UTM_Medium LC – Processing

Hidden

IM – UTM_Source FC – Processing

Hidden

IM – UTM_Source LC – Processing

Hidden

IM – UTM_Term FC – Processing

Hidden

IM – UTM_Term LC – Processing

Hidden

gclid

Hidden

msclkid

Phone

This field is for validation purposes and should be left unchanged.

Count Me In Submit