uptime system
one line. four facts. zero effort.
The uptime man page is 50 lines long. The command itself outputs one line. This might be the shortest page on this site.
Someone asks “when was the server last rebooted?” You could check logs. You could run last reboot. You could look at monitoring dashboards. Or you could type six letters and get the answer instantly.
uptime tells you four things in one line: the current time, how long the system has been running, how many users are logged in, and the load average. That’s it. One command. One line of output. No scrolling, no parsing, no clicking through dashboards.
On Windows, you’d open Task Manager, click “Performance,” look at the bottom where it says “Up time” in a font size designed for ants, and do mental math to figure out what “4:02:15:33” means. Or you’d run systeminfo in PowerShell and scroll through 40 lines of output to find the “System Boot Time” field, then calculate the uptime yourself. For one number.
Unless you’re running Windows then wtf none of this applies to you. But hey, come to the dark side, go install WSL2 and you can follow along. We’ll wait. Impatiently.
If you’re lazy like me (all sysadmins are!) then click here for the uptime cheat sheet.
Just run it
uptime
16:30:01 up 47 days, 3:22, 2 users, load average: 0.52, 0.44, 0.38
Four facts in one line:
| Piece | Meaning |
|---|---|
16:30:01 |
Current system time. |
up 47 days, 3:22 |
System has been running for 47 days, 3 hours, 22 minutes. |
2 users |
Two users are currently logged in (see who). |
load average: 0.52, 0.44, 0.38 |
System load over the last 1, 5, and 15 minutes. |
That’s the whole command. There’s barely anything else to say.
Machine-readable uptime
uptime -s
2026-01-27 13:08:01
The exact date and time the system was booted. No mental math. When someone asks “when did this server come up,” this is the answer.
Just the duration
uptime -p
up 47 days, 3 hours, 22 minutes
Human-readable uptime without the load average and user count. Just the fact.
Understanding load average
The three numbers at the end are the most important — and most misunderstood — part of the output.
load average: 0.52, 0.44, 0.38
Load average represents the number of processes waiting for CPU time (plus processes currently using CPU). Think of it as a queue length.
The rule of thumb: compare load average to your number of CPU cores.
nproc
If you have 4 cores:
| Load average | Meaning |
|---|---|
0.50 |
System is 12.5% loaded. Mostly idle. |
1.00 |
One core is fully utilized. Three are free. Fine. |
4.00 |
All four cores are fully utilized. System is at capacity. |
8.00 |
Twice as many processes want CPU as you have cores. Things are waiting. Slow. |
The three numbers show the trend: 1-minute, 5-minute, 15-minute averages. If the 1-minute average is high but the 15-minute average is low, you just had a spike. If all three are high, the system has been busy for a while.
The flags that actually matter
| Flag | What it does |
|---|---|
-p |
Pretty — human-readable uptime duration. |
-s |
Since — exact boot time (YYYY-MM-DD HH:MM:SS). |
That’s all of them. There are two flags. This is the simplest command on this site.
“But—”
Really?
“I check uptime in my monitoring dashboard.” Your monitoring dashboard shows a graph. uptime shows a number. The graph is useful for trends. The number answers the question “how long has this been running” in one second. Use both. But when someone on a call asks “when was the last reboot,” you’re not going to share your screen and open Grafana.
“High uptime means the server is healthy.” No. High uptime means nobody has rebooted it. Maybe nobody has patched it either. “500 days uptime” is not a badge of honor — it’s 500 days of kernel security patches you haven’t applied. Reboot your servers. Apply your updates.
“Load average doesn’t tell me much.” Load average tells you whether the system is overloaded right now, at a glance, without opening htop or reading through ps output. It’s the vital sign check before the full diagnosis. High load? Now go investigate with htop. Low load? The problem isn’t CPU. Move on.
uptime cheat sheet
You made it. Or you skipped straight here. Either way, no judgment. Copy and paste these. Pin them. Tattoo them on your forearm. Whatever works.
| What you’re doing | Command |
|---|---|
| Full status (time, uptime, users, load) | uptime |
| Just the uptime duration | uptime -p |
| Exact boot time | uptime -s |
| Number of CPU cores (for load context) | nproc |
The one command:
uptime— one word, one line, four facts. The quickest system health check that exists.