Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Skyrunner]

Recently, I have been having tons of dropped packets to the bay12 minecraft server occassionally, from 20 to 60% at times.

Spoiler: tracert (click to show/hide)

tracert baytwelve.playat.ch

최대 30홉 이상의
baytwelve.playat.ch [78.129.230.78](으)로 가는 경로 추적:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     9 ms    10 ms     9 ms  183.98.73.126
  3     9 ms     7 ms     7 ms  121.138.47.57
  4     6 ms     6 ms     6 ms  61.78.42.172
  5     6 ms     5 ms     6 ms  121.138.4.141
  6     7 ms     7 ms     7 ms  112.174.57.249
  7     6 ms     5 ms     5 ms  112.174.48.86
  8     9 ms     6 ms     6 ms  112.174.84.102
  9   142 ms   158 ms   142 ms  112.174.97.242
 10     *        *        *     요청 시간이 만료되었습니다.
 11     *      300 ms   300 ms  xe-10-0-3.lon10.ip4.gtt.net [141.136.107.157]
 12     *      330 ms     *     iomart-gw.ip4.gtt.net [46.33.94.6]
 13   301 ms   297 ms     *     202.core1.hex.as20860.net [62.233.127.1]
 14   300 ms   300 ms     *     610.net2.north.dc5.as20860.net [62.233.127.182]

 15   352 ms     *        *     87.117.212.38
 16   304 ms   303 ms   301 ms  82.145.61.5
 17   300 ms   305 ms   299 ms  78.129.230.78

추적을 완료했습니다.

Tracert seems to tell me that the 10th path it used to get to the server has a timeout (that's what the korean says, btw--request has timed out). Is it possible to figure out which path this is then blacklist it somehow? :/

[Thief^]

Tracert seems to tell me that the 10th path it used to get to the server has a timeout (that's what the korean says, btw--request has timed out). Is it possible to figure out which path this is then blacklist it somehow? :/

That's not quite what it's saying. If *every* ping to that hop times out, it tends to mean that it's configured not to respond to ping.

Given that the random timeouts happen after that hop, that does suggest that the problem is with one side of that hop (incoming from hop 9 or outgoing to hop 11) or even with one of those routers (hop 9, 10 or 11) itself. Unfortunately you can't find out whose it is, but it might be possible to ID hop 9 to give you a hint. Hop 11 is an international line (run by GTT), which is why the latency skyrockets.

FAKEEDIT: Hop 9 is most likely Korea Telecom. 8 is for sure, most likely all the 112.174.*.* hops are. So the problem seems to be on the border router between Korea Telecom and GTT.

[Skyrunner]

Interesting, so that's how you read tracert.