uptime is often the very first command run when checking on an unfamiliar or recently-alerted server. In one line it answers three questions: how long has this machine been running, how many people are on it, and how busy has it been recently.

Basic Usage

uptime

Typical output:

 14:32:07 up 23 days,  4:12,  3 users,  load average: 0.42, 0.58, 0.61

Reading left to right: the current time (14:32:07), how long since boot (up 23 days, 4:12), the number of logged-in users (3 users), and the load average over the last 1, 5, and 15 minutes (0.42, 0.58, 0.61).

Why Check Uptime First

Uptime is cheap to run and answers questions that matter before diving into deeper diagnostics:

• Confirming a reboot happened: after applying a kernel update or major patch, uptime confirms whether the system actually restarted, since a short uptime after a scheduled reboot confirms the change took effect.
• Spotting unexpected reboots: an unexpectedly short uptime on a server you didn’t intentionally restart is a signal to check logs for a crash, power event, or out-of-memory kill.
• A first read on load: the load average gives an immediate sense of whether the system has been busy, without needing to open top or htop.

Simplified Output Modes

uptime -p

up 23 days, 4 hours, 12 minutes

Plain-language duration, useful for humans reading terminal output or scripts generating status messages.

uptime -s

2026-06-11 10:20:03

Just the exact boot timestamp, useful for scripting or logging when you need a machine-parseable value rather than a relative duration.

The Load Average Numbers

The three numbers after load average: represent system load averaged over the last 1, 5, and 15 minutes. On Linux, “load” counts processes that are either using the CPU, waiting for CPU time, or blocked in uninterruptible I/O (typically disk wait). This is broader than a pure CPU-only metric, which is why Linux load averages can be misleading if you assume they measure CPU usage alone.

Reading the three numbers together tells a story:

• Rising (1-min higher than 15-min): load has increased recently, might still be climbing
• Falling (1-min lower than 15-min): load has recently eased off from a busier period
• Steady: load has been roughly consistent across all three windows

A deeper explanation of what counts as “load,” how to interpret the numbers against your CPU core count, and common misreadings is covered in a dedicated article on load average.

Checking Who Else Is Logged In

The 3 users figure in the default output is a count, not a list. To see who’s actually logged in:

who

alice    pts/0        2026-07-04 09:12 (10.0.1.4)
bob      pts/1        2026-07-04 13:45 (10.0.1.9)

uptime vs. Session Duration

A common confusion: uptime reports how long the machine has been running, not how long you have been logged into your current session. If you SSH into a server that’s been up for 40 days, uptime will show 40 days regardless of when you connected. To check your own session length, use who filtered to your username, or review last for login history.

Frequently Asked Questions

What information does the uptime command show?

uptime shows the current time, how long the system has been running since its last boot, the number of users currently logged in, and the load average over the last 1, 5, and 15 minutes. It is one of the fastest commands available for a quick system health check, since it reads a small amount of data from the kernel and prints a single line.

Why would I check uptime before doing maintenance?

Checking uptime before a reboot or update tells you how long it has actually been since the system last restarted, which matters for confirming a previous patch or kernel update was applied correctly, planning maintenance windows around long-running processes, and spotting unexpected reboots that might indicate a crash or power event you were not aware of.

How is uptime different from checking system logs for boot time?

uptime gives you the duration directly with no calculation needed, while checking logs (via journalctl -b or the who -b command) tells you the exact boot timestamp. Both derive from the same kernel-tracked boot time, but uptime is faster for a quick check and log-based tools are better when you need the precise date and time or a history of previous boots.

What do the three load average numbers in uptime mean?

The three numbers are the average number of processes wanting to run (either using the CPU or waiting for it, and on Linux also processes waiting on uninterruptible I/O) averaged over the last 1, 5, and 15 minutes respectively. Reading all three together shows whether load is currently rising, falling, or steady compared to recent history.

How do I check just how long a system has been running without the extra details?

Use uptime -p for a plain-language duration like “up 3 days, 2 hours, 14 minutes” without the current time, user count, or load average. Use uptime -s to print just the exact date and time the system booted, which is useful for scripting or logging purposes.

Does uptime measure how long the current login session has lasted?

No. uptime measures how long the machine itself has been running since boot, not how long you personally have been logged in. To see how long your current session has lasted or when you logged in, use the who command with your username or check the output of the last command.