Last day I was surprised watching the uptime of my AP. 
492 days !!! without reboots
WOW
And you? 
We where playing with this time ago. Nice uptime!
http://forum.mikrotik.com/t/v3-x-uptime-challenge/32448/1
497 days is limit on some older versions. when it starts from zero, upgrade it, and go for a new record 
Right! 
now uptime is 4 days! 
RouterOS Version is 5.5…
then I win..
when your uptime counter goes around to zero, you know it’s time to upgrade 
Don’t you guys use Dude? I surely never would leave a system for such a long time ‘unpatched’.. but maybe, I am just too long in Microsoft’s business…
swissiws, did you received a memorable hack in a mikrotik router? : ?
I have a 2003 server that was automatically updated on 14/02/2013 and now it reboots..
nope, but improvements in process handing, CPU utilization and speed.
Mikrotik wAP ac uptime 400day
7 years waiting : DDDD
nice update.
8 Years…
My device… RBV1AGARAxxx69
my one
The winner is voted most likely to get hacked…
do you like mine?
432 days
65 TB download
almost 18 TB uploaded
Is just a RB2011.
Many L2TP-IPsec VPN and big queues…
Current highest in my network is 465 days. Its in a site we are not allowed to get easy access to - but it is firewalled out the wazoo (running 6.45.5) - most of my others have been rebooted either due to upgrades or power issues I think the next highest is about 100d.
Not Mikrotik related, but uptime related
Went to a client in approx 1997/98, it was a bakery baking high volumes of breads for shops. The callout was for to setup / connect a new user to their network.
The Novell 3.x server used as a F&P server, dust, backing powder, etc all over the server, server uptime over 700 days
If we’re into (true) uptime stories: I’ve had a linux server (running early 2.6 kernel with fixed uptime counter) with uptime of more than 1700 days. The company I worked for at that time decided to move data centre and I came up with a plan to move the server while running off an UPS. That would not be entirely trivial as server had attached external disk enclosure which needed uninterrupted power and connectivity to server as well. The guys who helped moving gear almost agreed. At the end the company decided it’s time for a new server instead. Doh!
Oh man … 482d
Maybe i should stop Auto-Updating the Servers, to Win =)
