I've just looked at a pair of what I would call "busy" MX400's.  They currently show as having 238 VPNs, and the "Organisation/Summary Report" pages shows the load as being 67%.  They are running 13.27 (you would use 13.28 now if you were going to upgrade).   The output you are seeing from support appears to be from the Linux "uptime" command (or the output from 'cat /proc/loadavg'). Easy explanation: https://www.itworld.com/article/2833435/hardware/how-to-interpret-cpu-load-on-linux.html More complex explanation: http://www.brendangregg.com/blog/2017-08-08/linux-load-averages.html   You would really need to see these stats at the time you are getting your VRRP events - but it would have to be pretty bad to cause a VRRP failover.  I find it difficult to believe the CPU load would cause a VRRP failover.  The Meraki hello timer is 300ms, and it needs three hellos to be missed - so the MX CPU would have to be so busy that it could not service the VRRP traffic for 900ms (that is almost a second!).     It is hard to talk about the linux load values without knowing more about the internals of the MX OS.  For example, if there was a single threaded process doing most of the work then having 4 CPU cores would not help, and a load average of 1 would not be so good.  But assuming there are lots of processes running splitting the load across the CPU cores then a load average of 1 is not that bad, ... View more