: Exact same points hop 8 would be: 104.160.153.78 and hop 9 would be: ae-30.br02.ams02.riotdirect.net [104.160.159.54] Those 2 seem to timeout the most, though hops 11 and 12 often have some non-responses and rarely hop 8. Riot believes the issue is at 10.189.30.10 (Hop 7) when Telkom hands over it's traffic to wherever it's landing in/near Europe. If it is Telkom, then we're kinda stuck with this for a while, as we know how fast they work
1 3 ms 2 ms 2 ms 10.0.0.2 2 * * * Request timed out. 3 27 ms 25 ms 26 ms 105-187-235-29.telkomsa.net [105.187.235.29] 4 26 ms 25 ms 25 ms 105-187-235-30.telkomsa.net [105.187.235.30] 5 26 ms 25 ms 24 ms ipc-aggr-1.south.dsl.telkomsa.net [105.226.0.13] 6 28 ms 26 ms 25 ms wblv-os-cer-1-wan.osnet.co.za [196.25.49.189] 7 193 ms 184 ms 185 ms 10.189.30.10 8 224 ms 197 ms * pr02.fra02.riotdirect.net [80.81.193.162] 9 * * * Request timed out. 10 * * 199 ms ae-30.br02.ams02.riotdirect.net [104.160.159.54] 11 200 ms 202 ms 197 ms 104.160.141.103 12 201 ms 200 ms 199 ms 104.160.141.107 13 196 ms 200 ms 204 ms 185.40.64.65
: Telkom has to change the route that it's being sent over, I'm going to try and use their live chat service in the morning, as otherwise it will probably sit in an inbox for a week
any word from them?
Rioter Comments

Kelloks1299

Level 95 (EUW)
Lifetime Upvotes
Create a Discussion