Why beeline does not like youtube so much?

Since the end of last year, I began to notice unpleasant brakes when watching videos from youtube via the wired Internet from Beeline in Nizhny Novgorod. At first, I thought that this was a temporary phenomenon, a channel clogged with torrents, windows glitches, problems with the router, viruses. In general, I thought for a long time, then I noticed that this is observed not only for me and not only for youtube. As a result, not so long ago I wrote the following letter to tech support.

Hello.

I am connected to the home internet.
Contract data:
*****************

For quite a long time, there has been a problem with speed to some sites. Including the youtube.com website almost all the time video download speed - 20 kbytes / c. At the same time from the Russian sites everything works as it should. I have already checked my software, viruses and other things that could occupy the Internet channel, besides, if with other sites I can assume that the site itself is slowing down then in the case of youtube this is absurd. This problem is observed not only for me but also for many in Nizhny Novgorod.
I did a route tracing to youtube servers in the case when it works fine and with brakes:
')
Works fine -
Tracing route to youtube.com [74.125.45.100]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 192.168.1.1
2 5 ms 3 ms 3 ms 195.98.58.254
3 4 ms 4 ms 7 ms bb-gi-2-22.kis.ru [92.242.65.1]
4 2 ms * 4 ms Amway1.NNovgorod.gldn.net [194.186.130.189]
5 53 ms 52 ms 52 ms cat01.Frankfurt.gldn.net [194.186.80.126]
6 50 ms 50 ms 51 ms de-cix10.net.google.com [80.81.192.108]
7 61 ms 63 ms 63 ms 209.85.255.172
8 64 ms 59 ms 59 ms 209.85.248.94
9 145 ms 142 ms 143 ms 72.14.239.94
10 165 ms 175 ms 159 ms 216.239.48.69
11 154 ms 153 ms 155 ms 72.14.232.213
12 156 ms * 168 ms 209.85.253.141
13 162 ms 158 ms 160 ms yx-in-f100.1e100.net [74.125.45.100]

Trace complete.

Brakes -
Tracing route to youtube.com [74.125.67.100]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 2 ms 2 ms 1 ms bras-ats77-7-lo-1.kis.ru [89.189.25.254]
3 2 ms 2 ms 3 ms bb-gi-2-13.kis.ru [89.189.25.237]
4 2 ms 1 ms 1 ms pe-l.NNovgorod.gldn.net [212.44.133.37]
5 48 ms 47 ms 47 ms cat01.Frankfurt.gldn.net [194.186.80.126]
6 51 ms 55 ms 51 ms de-cix10.net.google.com [80.81.192.108]
7 58 ms * 57 ms 209.85.255.172
8 59 ms 59 ms 58 ms 72.14.232.105
9 146 ms 139 ms 138 ms 216.239.43.90
10 153 ms 152 ms 153 ms 66.249.95.149
11 154 ms 156 ms 152 ms 209.85.254.247
12 154 ms 158 ms 161 ms 209.85.255.194
13 161 ms 157 ms 167 ms gw-in-f100.1e100.net [74.125.67.100]

Trace complete.

Checked twice in the case of a low speed route goes through the node pe-l.NNovgorod.gldn.net [212.44.133.37].
Perhaps this will help fix the problem faster.

I am not at all sure about my guess about the buggy node because I understand little of this, but still ... After about a day I received the answer:

Dear Customer!

Thank you for taking the time to write to us.

Answering your question, we would like to inform you that at the moment work is underway to remedy the situation, the application for work No. 105991879. The exact time frame for resolving the issue, unfortunately, has not been determined. We are well aware of your desire to have quality service, and on behalf of the Company we offer you our sincere apologies for the inconvenience caused. The information contained in your letter is very important to us: pointing out the shortcomings in our work, you help us find solutions and ensure high quality of service. Believe me, our Company takes all possible actions to ensure that all its services work without complaints from Clients.

We wish you all the best!

Your "Beeline".

And now, for a week, there has been no answer, according to former experience of communicating with technical support, it is unrealistic to get anything from them, they are constantly redirecting somewhere and they are afraid that they’ll do it right now.

PS It took me 20 meters of a twisted pair, perhaps I'll save a little and use a beeline cable for this purpose.