Thought I would share this for you all, from one of our CCR’s..
1year_ccr.jpg
x86-uptime.jpg
This is my uptime, but on X86 platform
Would you mind telling us what functions this router is fulfilling? BGP, OSPF, Queue Trees, NTP server …?
I had 270+ days on my BGP(1 peer, partial routes)/OSPF/50 firewall rules/20 vlans/occasional L2TP/IPsec server/500Mbps CCR1036 on 6.12 before it had a kernel panic and rebooted itself at 9 am local one week ago.
Can you post your “Health” section?
This is not a big deal I think. Mikrotik is very stable and can run years but what advantage does it have?
I have learned it is bad to have such a long uptime. It means your router is not updated and running old software. So vulnarabilities are not solved.
Long uptime is to me… an impressive achievment in its own right!
- This means stable power infrastructure and very good backup.
- This means stable software, which is not easy to achieve. Even with the big Vendors, there are nasty and devastating bugs that just crash the system.
- This means stablility and quality of the hardware, not only as a design, but also as production and quality assurance.
I do agree though, that it also depends on what the device does… if it is seating in a basement, just powered on, doing basically nothing - than it’s not impressive. But if it’s a real production device - that’s an impressive feat.
Regarding the updates - it depends. Many vulnerabilities might just not concern your device, because it does not have the configuration or the configuration options that are required; you might not even have the packages that are affected in your system enabled. So… it depends 
Regards,
Boyan
The CCRs need some reports of good uptimes under load to counter the bad “press” they deservedly received when first released. I see some people who wrote off the CCR line entirely back in the pre-6.7 days. These people haven’t noticed that most issues appear to be fixed, for many, not all and maybe not most, of the recent RouterOS releases since 6.7.
If MikroTik could resist some of the feature creep, we would not have to guess if the next revision will break long working sub-systems.
So, while unpatched uptime on Internet connected devices is not really something to brag about, we could use some anecdotes in the case of the CCR hardware line.
This is an edge router running ebgp, ibgp, ospf, ospfv3 in production, average traffic is quite low but has bursts of up to gigabit. Here’s a screen grab of the counters and BGP, one of the remote BGP peers has 291 days uptime, I think this shows that the CCR platform is pretty solid, this router has also survived at least 1 DDoS attack.
ccr_uptime.jpg