Packet loss. Where to apply?

Question

Computer networks

Hello.
Tell me what to do in a similar situation:
My provider has Megafon as a backbone. Recently, constant packet loss began when accessing some resources. The trace looks like this:
Everything works

spoiler

C:\Users\Redfox>tracert 54.37.169.39
Трассировка маршрута к 54.37.169.39 с максимальным числом прыжков 30
1 1 ms 1 ms <1 мс 10.1.2.20
2 1 ms <1 мс 1 ms 194.58.188.97
3 1 ms 1 ms 1 ms du-112-41.sv-en.ru [134.19.150.41]
4 1 ms 1 ms 11 ms du-208-93.sv-en.ru [109.236.208.93]
5 3 ms 2 ms 3 ms 188.170.161.29
6 53 ms 52 ms 94 ms 10.222.44.125
7 53 ms 53 ms 53 ms 10.222.44.5
8 52 ms 53 ms 53 ms 10.222.37.14
9 53 ms 53 ms 53 ms 10.222.77.70
10 52 ms 52 ms 52 ms 10.222.36.134
11 62 ms 52 ms 52 ms 83.169.204.50
12 * * * Превышен интервал ожидания для запроса.
13 * * * Превышен интервал ожидания для запроса.
14 * * * Превышен интервал ожидания для запроса.
15 * * * Превышен интервал ожидания для запроса.
16 61 ms 61 ms 61 ms be105.gra-g1-nc5.fr.eu [213.186.32.212]
17 * * * Превышен интервал ожидания для запроса.
18 61 ms 60 ms 61 ms be50-5.gra-3a-a9.fr.eu [37.187.231.86]
19 60 ms 60 ms 60 ms 54.37.169.39

And like this when the resource is unavailable:

spoiler

C:\Users\Redfox>tracert 54.37.169.39
Трассировка маршрута к 54.37.169.39 с максимальным числом прыжков 30
1 1 ms 1 ms 1 ms 10.1.2.20
2 1 ms 1 ms 1 ms 194.58.188.97
3 1 ms 1 ms 1 ms du-112-41.sv-en.ru [134.19.150.41]
4 1 ms 1 ms 1 ms du-208-93.sv-en.ru [109.236.208.93]
5 3 ms 3 ms 5 ms 188.170.161.29
6 53 ms 53 ms 53 ms 10.222.44.125
7 55 ms 53 ms 59 ms 10.222.44.5
8 53 ms 53 ms 52 ms 10.222.37.14
9 53 ms 52 ms 52 ms 10.222.77.70
10 53 ms 53 ms 52 ms 10.222.36.134
11 * * * Превышен интервал ожидания для запроса.
12 * * * Превышен интервал ожидания для запроса.
13 * * * Превышен интервал ожидания для запроса.
14 * * * Превышен интервал ожидания для запроса.
15 * * * Превышен интервал ожидания для запроса.
16 * * * Превышен интервал ожидания для запроса.
17 * * * Превышен интервал ожидания для запроса.
18 * * * Превышен интервал ожидания для запроса.
19 * * * Превышен интервал ожидания для запроса.
20 * * * Превышен интервал ожидания для запроса.

This is what the Zabbix chart looks like:

spoiler

WinMTR log

spoiler

------------------------------------------------------------------------------------------|

| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 10.1.2.20 - 0 | 1669 | 1669 | 0 | 0 | 351 | 0 |
| 194.58.188.97 - 0 | 1666 | 1666 | 0 | 1 | 129 | 1 |
| du-112-41.sv-en.ru - 0 | 1667 | 1667 | 1 | 1 | 30 | 1 |
| du-208-93.sv-en.ru - 0 | 1666 | 1666 | 1 | 6 | 391 | 2 |
| 188.170.161.29 - 0 | 1666 | 1666 | 2 | 3 | 235 | 3 |
| 10.222.44.117 - 0 | 1668 | 1668 | 41 | 41 | 68 | 42 |
| 10.222.44.1 - 0 | 1669 | 1669 | 41 | 41 | 72 | 41 |
| 10.222.37.1 - 0 | 1669 | 1669 | 41 | 41 | 55 | 48 |
| 10.222.77.66 - 0 | 1668 | 1668 | 40 | 41 | 74 | 41 |
| 83.169.204.124 - 29 | 799 | 572 | 0 | 41 | 84 | 40 |
| No response from host - 100 | 342 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 342 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 342 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 342 | 0 | 0 | 0 | 0 | 0 |
| be105.gra-g1-nc5.fr.eu - 29 | 799 | 572 | 0 | 51 | 115 | 49 |
| No response from host - 100 | 342 | 0 | 0 | 0 | 0 | 0 |
| be50-5.gra-3a-a9.fr.eu - 29 | 799 | 572 | 0 | 70 | 227 | 51 |
| 54.37.169.39 - 29 | 796 | 569 | 0 | 48 | 58 | 48 |
|________________________________________________|______|______|______|______|______|______|

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Node 188.170.161.29 belongs to MegaFon, as I understand it, VPN goes on, node 83.169.204.124 belongs to Volga Branch of OJSC MegaFon NOC.
At the same time, through another provider (Beeline, Rostelecom, KGTS), everything works without failures.
tracing through KGTS:

spoiler

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.2.1 - 0 | 11 | 11 | 2 | 2 | 6 | 2 |
| access-46-42-0-6.kmtn.ru - 0 | 11 | 11 | 4 | 12 | 54 | 4 |
| access-46-42-0-5.kmtn.ru - 0 | 11 | 11 | 3 | 6 | 12 | 11 |
| m9-r5.inet2.ru - 0 | 11 | 11 | 8 | 9 | 16 | 9 |
| msk-ix.as16276.ovh.ru.eu - 0 | 11 | 11 | 29 | 32 | 55 | 29 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| be100-1166.ams-1-a9.nl.eu - 0 | 11 | 11 | 50 | 53 | 71 | 50 |
| be104.gra-g1-nc5.fr.eu - 0 | 11 | 11 | 58 | 61 | 70 | 60 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| be50-5.gra-3a-a9.fr.eu - 0 | 11 | 11 | 58 | 71 | 161 | 58 |
| 54.37.169.39 - 0 | 11 | 11 | 58 | 59 | 66 | 58 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

My ISP's tech support said there was no problem on their site.
Megafon support said that they could not help.
Tell me what to do and where to turn in such a situation?
Thank you.

UPD: The provider started up traffic on a different route, the losses are gone. No Megaphone, no problem.

Answer 1

Well, it is immediately obvious that the problem, judging by the WINMTR log on the be105.gra-g1-nc5.fr.eu side, is the backbone provider.
Here option 2. Personally addresses the specified provider.
Option 2 to press through the provider, because you are a client. The provider either writes to the trunk operator himself (although he is not particularly obliged (see the contract)), or changes the routing if possible.