Hi all,
I am fairly new to Mikrotiks and managed to setup a hap lite in multi-WAN mode. Dual-WAN to be exact. But it intermittently breaks.

The setup:
Running RouterOS v6.38.5. Two ports are configured for WANs (connected to two different ISPs' devices) and the other two are for LAN. Dedicated WAPs connect to one of the LAN ports and a computer to the other.

I used this guide to understand and configure, along with the official wiki. I tested the setup thoroughly when I set it up, it worked great and then I left the site.

The problem:
After a few days of operation (can be 5 to 25), all clients lose internet connectivity. Power cycling the setup fixes the issue, until it manifests again after a few days/weeks.
The device is remote so I can only troubleshoot it while it's responding remotely. While in the "stuck" mode, I can't access it. Reviewing logs after it boots back up doesn't help because they're stored in volatile memory.

What I've tried:
[*]Reviewing my settings trying to spot mistakes (found a minor one but the issue still happens after fixing it)
[*]Disabling one of the WAN interfaces, to force everything through the other WAN, didn't help
[*]Forwarding syslog to central server to help troubleshoot the problem (nothing interesting pops up when the connection goes down)

Ideas to troubleshoot this are appreciated! Please take a look at the config, maybe I've screwed up something. I'm a Mikrotik noob!

Thanks in advance!
The relevant (IMO) config parts are attached.

There are a couple of scenarios that would cause your issues, the first thing I would is try to get more visibility into the issue by setting up a syslog server to gather information.

By looking at your config file I did notice that you setup separate distances for the routes that use the tables your created for PCC:
This routes should both have the same distance; which if you don't specify it, will default to 1. That is unless you are looking for a failover scenario, in which case you won't need PCC.

Thanks for the reply. Good spotting of the distance setting! I fixed it. Hopefully it will help.

Regarding syslog, I tried forwarding it to a central server to help troubleshoot the problem but nothing interesting pops up when the connection goes down. I added the following topics: system, warning, critical, dhcp, error, firewall, info, interface. Should i have increased verbosity perhaps?