Survey: What's your uptime?

What's your uptime? List your devices' makes and models, OpenWrt versions and targets, along with their uptime. I'm curious to see which combinations have the best uptime records.

I'll start:

TP-Link TL-WDR3600, OpenWRT 18.06.7, ath71xx: Uptime 1 day, 18:28

  • Most recent reboot manual due to firmware downgrade after experiencing instability upon upgrade to ath79/19.07.1.

I've had 90 days :heavy_plus_sign: ...this is the easiest accessible right now.

Are you just making a fun thread?

Routers don't need to be rebooted.

Updated to 17.07.1 around the 1st of the month...

# uptime
 15:17:42 up 20 days, 21:52,  load average: 0.00, 0.00, 0.00

Usually uptime is months, no reason to restart unless applying an update.

1 Like

I like your idea in the larger sense, but this can be a bit misleading as short uptimes don't necessarily indicate stability issues. For example, I have a Ubiquiti RouterStation Pro (ar71xx) running 18.06.5 that has been up for 78 days and another one running 19.07.1 (on the ath79 target) that has been up for 21 days. Flashing new versions, installing certain packages (or performing extroot and other things), major configuration changes, and the like can all require restarts and thus resetting uptimes (not to mention power outages, ISP issues requiring power-cycling of the router, etc.).

In the case of the official stable release of 19.07.1 (Jan 31), it wouldn't be possible to have more than 23 days uptime, and that assumes you installed it immediately after release. It says nothing about stability.

So a better way to look at this might be to also ask "what was the reason you you most recently rebooted your device?" to understand if this was due to an OpenWrt issue or some other factors.

5 Likes

:+1:

[Mains] power outage.

That Snapshot was installed the day of release, so otherwise 100% up since flashing and after.

I agree that a short uptime doesn't necessarily indicate instability; however, I feel that a long uptime usually does indicate stability, and that's what I'm most curious to see. There should be no need to reboot your device (except for some of the reasons below).

If you feel that your uptime response may not reflect your typical number, and would like to qualify it with a caveat, please do so as this could also be informative for positive reasons such as:

  • installed critical security patch
  • powered down due to planned equipment move
  • purchased new device
  • rebooted due to elective firmware upgrade

as well as negative ones such as

  • spontaneous reboots due to hardware or software issues
  • unplanned power outages
  • manual reboots due to hard lockups
1 Like

What make and model is your device?

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------
 OpenWrt 19.07-SNAPSHOT, r10913+22-4668ae3bed
 -----------------------------------------------------
root@PC Engines APU2:~# uptime
 22:07:41 up 21 days, 18:06,  load average: 0.00, 0.00, 0.00

They only go down for updates. So last bump 21 days ago.

My Technicolor TG799vac used as AP has been up 111 days. I don't have any reasons to restart it since I can't update the software.
And my server and virtual routers have been up 70 days, but I really should restart soon since the kernel was updated some time ago.

Completely agree. My point was to suggest that readers use caution not to infer that shorter uptimes are necessarily related to issues, especially when running newer versions. One might even argue that an uptime of say 2 years, while clearly stable, might suggest that the user should seriously consider a new version (if supported) to improve security based on patched vulnerabilities in the more recent builds.

1 Like

Model
Linksys WRT3200ACM
Architecture
ARMv7 Processor rev 1 (v7l)
Firmware Version
OpenWrt SNAPSHOT r12288-1173719817 / LuCI Master git-20.052.85700-b0de632
Kernel Version
4.19.101
Local Time
2020-02-22 21:42:54
Uptime
0h 51m 49s
Restarted because I flashed a new snapshot.
Model
Linksys WRT1900ACv2
Architecture
ARMv7 Processor rev 1 (v7l)
Firmware Version
OpenWrt SNAPSHOT r12252-060b58fd6e / LuCI Master git-20.050.48515-eec30a2
Kernel Version
4.19.101
Local Time
2020-02-22 21:43:23
Uptime
2d 10h 17m 29sLast
rebooted because of snapshot upgrade. I don't think I have gon more than 10 days before flashing a new build. lol

Netgear/R7800

Hi

@**:~# uptime
21:00:36 up 80 days, 1:52, load average: 0.21, 0.14, 0.10
ASUS RT-AC51U
Last reboot: softwareupdate

I just reboot these two when I need it (for example, after an upgrade); otherwise the uptime would be infinite:

Linksys WRT3200ACM
TP-Link TL-WDR4300

Hey there!

Heres my current setup:

vendor model version uptime device used for
LeMaker Banana Pi 18.06.0 121d 13h 7m 40s network router behind another router I have to use due to ISP limitations
TP-Link TL-WDR4900 v1 17.01.1 56d 2h 51m 57s dumb AP 2nd floor
TP-Link TL-WR1043N/ND v1 17.01.1 56d 2h 51m 2s dumb AP 2nd floor
TP-Link TL-WDR4300 v1 17.01.1 56d 2h 48m 31s dumb AP basement
TP-Link TL-WDR4900 v1 17.01.1 85d 1h 54m 48s dumb AP 1st floor
TP-Link TL-WDR4900 v1 17.01.1 29d 9h 3m 36s dumb AP basement

It's obviously about time to raise some versions here.

Reasons for reboot:

The connection between the wdr4900 2nd floor and the wdr4300 basement has a sometimes faulty network cable that sometimes drops the link to 100MBit once or twice a year. Changing the cable isn't easy. So I just live with it and just remove the cable and plug it back in whenever this happens. The reboot 59 days ago was just me being too lazy to walk over to the cable. I started rebooting all my devices just "while I was on it", but realized there's no reason for it when I was only half way through :).

The reboot 85 days ago of another 4900 was because the wall it was mounted to was repainted.

I have no clue why the 4900 in the basement was rebootet 29 days ago.

The reboot of the Banana Pi was me investigating a network issue that turned out as a DNS problem with my ISP.

Conclusion: As you guys already said, there's literally no reason to reboot a router that is intrinsic to it being a router, except for updates. All other reasons are rather caused by the environment.

Regards,
Stephan.

Apologies for resurrecting old thread.

BT Home Hub 5A (Lantiq), wireless disabled, running LEDE 17.01.6 in VDSL modem-router mode.

1,000 days

2 Likes

Have you got a fantastic stable electric supply or a UPS?

No UPS. Last power outage perhaps occurred about 4 years ago affecting this part of the town.

For sharts and gargles, the highest uptime I currently see with my devices is this TP-Link TL-WA850RE that is used for its intended purpose: providing Wifi to a remote corner of my parents' house ... edit: oh, and it's the WireGuard peer to bridge my network to theirs. Come to think of it, I'm actually amazed that this little bugger is holding up as well as it is.

 OpenWrt 18.06.2, r7676-cddd7b4c77
 -----------------------------------------------------
root@TP-Link-Extender:~# uptime
 02:26:34 up 326 days,  9:53,  load average: 0.00, 0.00, 0.00

Everything else I run OpenWrt on gets rebooted occasionally, but never reboots on its own.

1 Like