Why do you need to do a traceroute when the resource is not responding, what can this tell the admins?

Question

linux

The vk.com resource is unavailable, and only at my provider, technical support suggested doing a trace:

[email protected]:~$ traceroute vk.com
traceroute to vk.com (87.240.131.118), 30 hops max, 60 byte packets
 1  router.asus.com (192.168.1.1)  0.477 ms  1.042 ms  1.220 ms
 2  10.91.255.254 (10.91.255.254)  11.331 ms  11.530 ms  11.554 ms
 3  91.144.152.201 (91.144.152.201)  4.813 ms  4.999 ms  5.155 ms
 4  lag-6-435.bbr01.nn.ertelecom.ru (91.144.153.98)  14.348 ms  14.865 ms  14.517 ms
 5  net131.234.188-181.ertelecom.ru (188.234.131.181)  30.800 ms  31.435 ms  31.629 ms
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

Why is there no asterisk after 5 routes? What does it mean? Is everything that bad?

Answer 1

This means that the problems are on the part of R-telecom. Admins will know who to warm their heads for this. Or they will realize that they let your traffic go through the wrong backbone, or they will turn to the backbone directly.
Traceroute, as it were, is translated - we trace the path.
On the way from you to contact, the packet passes through many intermediate nodes. The trace helps determine where exactly the packet stops going further.