Czy mógł by ktoś zrobić tracert do serwera PUBG (161.156.141.5) we Frankfurcie na światłowodzie? u mnie na neo wygląda to tak:
C:\Users\XX>tracert 161.156.141.5
Tracing route to 5.8d.9ca1.ip4.static.sl-reverse.com [161.156.141.5]
over a maximum of 30 hops:
1 5 ms 28 ms 11 ms www.routerlogin.com [192.168.0.1]
2 22 ms 25 ms 26 ms byd-bng2.neo.tpnet.pl [83.1.5.87]
3 21 ms 25 ms 36 ms byd-r1.tpnet.pl [80.50.158.185]
4 25 ms 35 ms 32 ms poz-r2.tpnet.pl [194.204.175.206]
5 50 ms 62 ms 54 ms ae16-10.ffttr7.-.opentransit.net [193.251.249.5]
6 64 ms * 65 ms hundredgige0-0-0-30.pastr4.-.opentransit.net [193.251.240.174]
7 66 ms 66 ms 65 ms hundredgige0-1-0-13.partr1.-.opentransit.net [193.251.131.18]
8 87 ms 90 ms 91 ms 100ge2-0-0.liscr1.-.opentransit.net [193.251.129.206]
9 96 ms 92 ms 101 ms cloudflare-11.gw.opentransit.net [193.251.150.116]
10 91 ms 87 ms 87 ms 172.68.101.26
11 101 ms 89 ms 88 ms 172.68.101.26
12 * * * Request timed out.
13 * 95 ms 93 ms ae5.cbs01.xn01.fra01.networklayer.com [169.45.18.166]
14 96 ms 94 ms 94 ms eb.13.2da9.ip4.static.sl-reverse.com [169.45.19.235]
15 93 ms 88 ms 95 ms 8f.76.9ca1.ip4.static.sl-reverse.com [161.156.118.143]
16 92 ms 93 ms 105 ms a3.76.9ca1.ip4.static.sl-reverse.com [161.156.118.163]
17 100 ms 93 ms 92 ms 5.8d.9ca1.ip4.static.sl-reverse.com [161.156.141.5]
Trace complete.
