Boards›Report a Bug

Ping high from riot servers

BINGBONGPANDA·2/1/2020, 2:59:12 AM·3 votes·3,035 views

I did a traceroute and found that the riot service endpoint is the high latency. Anyone else experiencing this recently? I am located in Northern California, USA, #NA

tracert 104.160.131.1

Tracing route to 104.160.131.1 over a maximum of 30 hops

1 <1 ms <1 ms 1 ms testwifi.here [192.168.86.1] 2 2 ms 2 ms 3 ms 1.116.24.136.in-addr.arpa [136.XX.XXX.X] 3 * * * Request timed out. 4 * * * Request timed out. 5 1 ms 2 ms 2 ms xe-2-2-0.mpr4.sfo7.us.above.net [64.125.69.65] 6 2 ms 2 ms 3 ms ae5.cr2.sjc2.us.zip.zayo.com [64.125.26.21] 7 4 ms 2 ms 3 ms ae16.mpr4.sjc7.us.zip.zayo.com [64.125.31.15] 8 6 ms 2 ms 2 ms ae19.mpr3.sjc7.us.zip.zayo.com [64.125.30.76] 9 4 ms 2 ms 3 ms 128.177.104.34.IPYX-089814-940-ZYO.zip.zayo.com [128.177.104.34] 10 3 ms 3 ms 3 ms 104.160.130.35 11 50 ms 50 ms 49 ms 104.160.159.102 12 154 ms 150 ms 153 ms ae34-br01.chi01.riotdirect.net [104.160.159.22] 13 52 ms 51 ms 50 ms 104.160.131.1

Trace complete.

and

tracert 104.160.131.3

Tracing route to 104.160.131.3 over a maximum of 30 hops

1 <1 ms 1 ms 1 ms testwifi.here [192.168.86.1] 2 2 ms 4 ms 3 ms 1.116.24.136.in-addr.arpa [136.XX.XXX.X] 3 * * * Request timed out. 4 * * * Request timed out. 5 2 ms <1 ms 1 ms xe-2-2-0.mpr4.sfo7.us.above.net [64.125.69.65] 6 3 ms 4 ms 4 ms ae5.cr2.sjc2.us.zip.zayo.com [64.125.26.21] 7 5 ms 5 ms 5 ms ae16.mpr4.sjc7.us.zip.zayo.com [64.125.31.15] 8 5 ms 2 ms 2 ms ae19.mpr3.sjc7.us.zip.zayo.com [64.125.30.76] 9 3 ms 3 ms 3 ms 128.177.104.34.IPYX-089814-940-ZYO.zip.zayo.com [128.177.104.34] 10 3 ms 3 ms 4 ms 104.160.130.35 11 50 ms 50 ms 50 ms 104.160.159.102 12 158 ms 157 ms 161 ms 104.160.131.3

Trace complete.

You see in both cases the ~150ms is at the last hop to the riot services.

2 Comments

xDogMeatx2/1/2020, 7:31:28 AM1 votes

我在哪里不高？也许是服务还是您的路由器？

U Honor I Carry2/2/2020, 1:59:10 AM1 votes

Tracing route to 104.160.131.3 over a maximum of 30 hops

1 : 1 ms | 1 ms | 1 ms RT-AC68U-7BF8 [192.168.1.1] 2 : 5 ms | 2 ms | 3 ms 142-0-108-0-vrrp.tidewater.net [0.0.0.0] 3 : 2 ms | 1 ms | 1 ms 0.0.0.0 4 : 1 ms | 1 ms | 1 ms lnbh-co-pe-01-xe-0-0-2.tidewater.net 0.0.0.0] 5 : 11 ms | 10 ms | 11 ms v110.core1.bos1.he.net [209.51.191.149] 6 : 15 ms | 16 ms | 16 ms e0-35.core2.nyc4.he.net [184.105.64.53] 7 : 16 ms | 16 ms | 16 ms 100ge8-2.core1.nyc4.he.net [184.104.192.241] 8 : 25 ms | 16 ms | 16 ms ve951.core2.nyc6.he.net [184.105.64.178] 9 : 142 ms | 138 ms | 135 ms nyiix.riotdirect.net [198.32.160.32] 10 : 115 ms | 115 ms | 110 ms 104.160.132.35 11 : 113 ms | 114 ms | 116 ms 104.160.131.3

No you are not alone and it's pissing me off because riot support says it's my ISP call my ISP call the ISP but i've called and called to check and they have ZERO problems, they said they only see problems AFTER the hand my packages over to Riot. And that's out of their control.