MicroTik. Disruption of communication every couple of minutes?

Question

Computer networks

Hello!
The problem started this morning and I can't figure out how to solve it.

Every couple of minutes the L2TP tunnel falls off.
The provider says that everything is fine from their side, but from our point of view there is a very high upload traffic of more than 11 Mbps with a limit of 10 Mbps.

Client log:
11:48:49 system,info,account user support logged out from ***.***.**.* via winbox
11:49:43 l2tp,ppp,info MSK: terminating... - hungup
11:49:43 l2tp,ppp,info,account MSK logged out, 84 636554 75549 610 536
11:49:43 l2tp,ppp,info MSK: disconnected
11:50:43 l2tp,info first L2TP UDP packet received from ** *.***.**.**
11:50:43 l2tp,ppp,info,account MSK logged in, **.**.*.**
11:50:43 l2tp,ppp,info MSK: authenticated
11:50:43 l2tp,ppp,info MSK: connected
11:50:43 l2tp,ppp,info MSK: using encoding - MPPE128 stateless
11:52:07 l2tp, ppp,info MSK: terminating... - hungup
11:52:07 l2tp,ppp,info,account MSK logged out, 84 1457443 2639665 2607

Another line from the client log:
12:26:00 l2tp,ppp,info TRAKT-SERVER : terminating... - old tunnel is not closed yet

Client logs are also spammed from similar messages:
12:52:41 warning denied winbox/dude connect from ***.***.**.**

Server log:
11:48:49 system,info,account user support logged out from ***.***.**.** via winbox
11:49:43 l2tp,ppp,info MSK: terminating... - hungup
11:49:43 l2tp,ppp,info,account MSK logged out, 84 636554 75549 610 536
11:49:43 l2tp,ppp,info MSK: disconnected
11:50:43 l2tp,info first L2TP UDP packet received from ** *.***.**.**
11:50:43 l2tp,ppp,info,account MSK logged in, **.**.*.**
11:50:43 l2tp,ppp,info MSK: authenticated
11:50:43 l2tp,ppp,info MSK: connected
11:50:43 l2tp,ppp,info MSK: using encoding - MPPE128 stateless
11:52:07 l2tp,ppp,info MSK: terminating... - hungup
11: 52:07 l2tp,ppp,info,account MSK logged out, 84 1457443 2639665 2607

Answer 1

The info log level is not sufficient in this case, debug is needed.
But I will assume that the channel is overloaded because of this, the tunnel falls.
Do qos and see what applauds you so much, it is possible that someone in the office is either streaming or "torrenting".

Answer 2

As a result, the problem with the L2TP tunnel could not be solved.
Forwarded IPIP with IPSec and it all worked.
It was assumed that one of the providers on the way to the server was somehow blocking L2TP.

Answer 3

I would first of all translate to tcp, and watch.