Show System Uptime and Load Average
The uptime command shows how long your Linux system has been running without a reboot, along with the current load average. It's one of the simplest yet most telling commands for system health.
Think of uptime as your system's report card. In one line, it tells you: current time, how long the server has been up (days, hours, minutes), how many users are logged in, and the load average (1-minute, 5-minute, and 15-minute averages). The load average is crucial—it shows how busy your CPU is. A load of 1.00 means one CPU core is fully utilized. On a 4-core system, a load of 4.00 is fully utilized, while 8.00 means it's overloaded with processes waiting. Admins check uptime daily to verify stability—a server with 300+ days uptime is rock solid (or hasn't been patched!). It's also the first command you run when troubleshooting performance issues: if load is sky-high, you know the system is struggling.
Advertisement
[ Insert Google AdSense Banner Code Here ]
Check if the server has been running reliably without crashes.
Check CPU load averages to spot performance issues.
Confirm when the system was last restarted.
Quick check if high load is causing slowdowns.
uptime Display system uptime, users, and load average.
uptime -p Show uptime in pretty, human-readable format (e.g., "up 6 weeks, 2 days").
uptime -s Show the exact date and time when the system booted.
w Show who is logged in plus uptime information.
cat /proc/uptime View raw uptime in seconds (uptime and idle time).
cat /proc/loadavg View load averages directly from the kernel.
Load average shows three numbers: 1-minute, 5-minute, and 15-minute averages. These indicate how many processes are waiting for CPU time.
Single-core system: Load of 1.00 = fully utilized, 2.00 = overloaded (processes waiting)
Multi-core system: Multiply by core count. 4-core system can handle load of 4.00 comfortably
What's healthy? Load below 70% of core count is good. If load exceeds cores for 15+ minutes, investigate with top or htop.
Long uptime isn't always good: While impressive, very long uptimes (1+ year) mean the system hasn't been patched with security updates. Reboot after kernel updates!
Watch the trends: Rising load from 1-min → 5-min → 15-min means growing problem. Falling load means issue is resolving.
Load vs CPU%: Load includes processes waiting for I/O (disk/network), not just CPU. High load with low CPU% often means disk bottleneck.
Practice uptime commands in the interactive terminal below: