Hi all, 

I just moved to another house, and the same ISP is providing me internet access here. My C2300 Router is a few years old now, and he moved together with us to the new house.

Here i added some extra AP's and switches all from ubiquity, all connected to my TP Link router and that one is connected via the WAN port to my modem from my ISP (telenet in Belgium) 

Now for a few months we notice that during our telework skype and teams is instable. Up to the point that it's not workable anymore. Even on my private laptop (without VPN) i have issues when we do a video call with friends via zoom. (as well as cable and wifi) 

So i started some investigation. 

1) I called my ISP and logged a case. Because in the beginning if i restart the modem, the fenomene disapeard and we could work again for a few days. So i thought there is something wrong with the signal or modem. They even sent an engineer over to check the signal here in house etc. All was good and my case was passed through to some technical department for further investigation. Also there they don't see anything wrong. His question was to pull all cables out and work directly on the modem to exclude my setup. 

If we work directly on the telenet modem and all other cables are out, things seem to work. But i wrote a quick script with some pings and timestamps, i start it from my laptop.
So i have a continious ping to 2 DNS servers 1.1.1.1 and 8.8.8.8.8

I also have a continious ping to the internal adres of my modem, the internal adres of my router and the 'internal' WAN adres of my router

What did i noticed after a few days, all internal pings (up to the modem) do not have any package loss. 

But my ping to the outside / Internet have some serious drops from time to time. 

For example this week we could work normal on our initial setup via wifi. But this morning we noticed very quick that skype etc was instable. 

So i put my output from my script that pings the external DNS in an excel and noticed the following amount for 'request timed out': 

So on the 19th i have suddenly a large amount of drops. If i zoom in on the 19th:

So each hour almost equal amount of dropped packages. From 9h09 i changed the setup by pulling out the cable in the WAN port and plugged it in on a switch and further to my work computer, since then it worked smoothly again. 
This evening i just replugged the cable in the WAN port and all works again. 

Do you have any idea what is going wrong here? 
Other things I can start to monitor? 
First my suspect was the Modem from my ISP but I'm not so sure of it anymore. It seems there goes something wrong with the routing of my router? 

Thanks in advance for your help to figure this out. I'm a bit stuck. 

P.S.: if i do a ping via the router itself (system tools - Diagnostics) i got the same behaviour. almost instant response from the internal IP of the ISP modem. And I just did the ping to the outside: 

PING 8.8.8.8 (8.8.8.8): 64 data bytes
Reply from 8.8.8.8:  bytes=64  ttl=118  seq=1  time=16.658 ms
Reply from 8.8.8.8:  bytes=64  ttl=118  seq=2  time=18.068 ms
Reply from 8.8.8.8:  bytes=64  ttl=118  seq=3  time=21.180 ms
Reply from 8.8.8.8:  bytes=64  ttl=118  seq=4  time=17.146 ms
Reply from 8.8.8.8:  bytes=64  ttl=118  seq=5  time=16.706 ms
Reply from 8.8.8.8:  bytes=64  ttl=118  seq=6  time=18.917 ms
Reply from 8.8.8.8:  bytes=64  ttl=118  seq=7  time=18.314 ms
Reply from 8.8.8.8:  bytes=64  ttl=118  seq=8  time=16.945 ms
Reply from 8.8.8.8:  bytes=64  ttl=118  seq=9  time=21.020 ms
Reply from 8.8.8.8:  bytes=64  ttl=118  seq=10  time=24.899 ms
Reply from 8.8.8.8:  bytes=64  ttl=118  seq=11  time=17.953 ms
Reply from 8.8.8.8:  bytes=64  ttl=118  seq=12  time=22.892 ms
Reply from 8.8.8.8:  bytes=64  ttl=118  seq=13  time=18.280 ms
Reply from 8.8.8.8:  bytes=64  ttl=118  seq=14  time=20.093 ms
Reply from 8.8.8.8:  bytes=64  ttl=118  seq=15  time=16.103 ms
Reply from 8.8.8.8:  bytes=64  ttl=118  seq=16  time=19.930 ms
Reply from 8.8.8.8:  bytes=64  ttl=118  seq=17  time=15.848 ms
Reply from 8.8.8.8:  bytes=64  ttl=118  seq=18  time=15.682 ms
Reply from 8.8.8.8:  bytes=64  ttl=118  seq=19  time=17.946 ms
Reply from 8.8.8.8:  bytes=64  ttl=118  seq=20  time=18.880 ms
Reply from 8.8.8.8:  bytes=64  ttl=118  seq=21  time=17.140 ms
Request timed out!
Reply from 8.8.8.8:  bytes=64  ttl=118  seq=23  time=18.114 ms
Reply from 8.8.8.8:  bytes=64  ttl=118  seq=24  time=16.266 ms
Reply from 8.8.8.8:  bytes=64  ttl=118  seq=25  time=15.797 ms
Reply from 8.8.8.8:  bytes=64  ttl=118  seq=26  time=16.192 ms
Reply from 8.8.8.8:  bytes=64  ttl=118  seq=27  time=17.523 ms
Reply from 8.8.8.8:  bytes=64  ttl=118  seq=28  time=21.306 ms
Reply from 8.8.8.8:  bytes=64  ttl=118  seq=29  time=16.992 ms
Reply from 8.8.8.8:  bytes=64  ttl=118  seq=30  time=16.156 ms
Reply from 8.8.8.8:  bytes=64  ttl=118  seq=31  time=16.235 ms
Reply from 8.8.8.8:  bytes=64  ttl=118  seq=32  time=16.499 ms
Reply from 8.8.8.8:  bytes=64  ttl=118  seq=33  time=17.109 ms
Reply from 8.8.8.8:  bytes=64  ttl=118  seq=34  time=17.348 ms
Reply from 8.8.8.8:  bytes=64  ttl=118  seq=35  time=15.936 ms
Reply from 8.8.8.8:  bytes=64  ttl=118  seq=36  time=18.315 ms
Reply from 8.8.8.8:  bytes=64  ttl=118  seq=37  time=21.338 ms
Reply from 8.8.8.8:  bytes=64  ttl=118  seq=38  time=17.732 ms
Reply from 8.8.8.8:  bytes=64  ttl=118  seq=39  time=15.851 ms

So one drop and it hangs at ping number 39.