这是我在 Stackexchange 上发表的第一篇文章，因此如果缺少任何必要的信息，我可以在发布后添加。
我的问题是我正在尝试访问防暴游戏的 api。我在 zap-hosting.com 上托管了一个 Debian-Rootserver。
它已经运行了好几个月，没有一次超时。然而，昨天它停止工作了，因为它无法连接到riotgames的euw api。
研究问题后，我发现连接无法正常工作并停止在韩国的某个地方。我什至不知道为什么会这样，这似乎有点矫枉过正——我也不知道我是否可以改变它。
我可以 ping 并到达除此特定服务器之外的任何 IP 地址 (euw1.api.riotgames.com)
您可以在下面找到有关我对地址进行 ping 和跟踪的问题的必要信息。我和我的主人谈过，但他们说这超出了他们的影响范围。我可以/应该做什么才能再次访问 euw1.api.riotgames.com (104.160.144.188)？
图片中的文字：
root@ # ping euw1.api.riotgames.com
PING rapi.redge.globalriot.aws-rclusterprod-euc1-1.riotapi.rc.pvp.net (104.160.144.188) 56(84) bytes of data.
From 61.43.235.210 (61.43.235.210) icmp_seq=25 Destination Net Unreachable
From 61.43.235.210 (61.43.235.210) icmp_seq=54 Destination Net Unreachable
From 61.43.235.210 (61.43.235.210) icmp_seq=64 Destination Net Unreachable
From 61.43.235.210 (61.43.235.210) icmp_seq=65 Destination Net Unreachable
^C
--- rapi.redge.globalriot.aws-rclusterprod-euc1-1.riotapi.rc.pvp.net ping statistics ---
67 packets transmitted, 0 received, +4 errors, 100% packet loss, time 527ms
root@ # ping 61.43.235.210
PING 61.43.235.210 (61.43.235.210) 56(84) bytes of data.
64 bytes from 61.43.235.210: icmp_seq=1 ttl=54 time=322 ms
64 bytes from 61.43.235.210: icmp_seq=3 ttl=54 time=318 ms
64 bytes from 61.43.235.210: icmp_seq=4 ttl=54 time=209 ms
64 bytes from 61.43.235.210: icmp_seq=5 ttl=54 time=210 ms
^C
--- 61.43.235.210 ping statistics ---
5 packets transmitted, 4 received, 20% packet loss, time 39ms
rtt min/avg/max/mdev = 209.163/264.866/322.044/55.318 ms
root@ # traceroute euw1.api.riotgames.com
traceroute to euw1.api.riotgames.com (104.160.144.188), 30 hops max, 60 byte packets
1 * * *
2 * * *
3 ae6-core4.core3.ffm3.de (45.138.175.61) 5.139 ms 5.161 ms 5.143 ms
4 160.20.144.69 (160.20.144.69) 5.286 ms 5.265 ms 5.235 ms
5 ae14-2021.fra10.core-backbone.com (80.255.14.5) 5.165 ms 5.151 ms
5.137 ms
6 core-backbone.uplus.co.kr (5.56.19.98) 5.120 ms 5.145 ms 5.117 ms
7 1.208.104.217 (1.208.104.217) 179.002 ms 181.657 ms 183.618 ms
8 1.208.107.77 (1.208.107.77) 214.308 ms 61.42.0.117 (61.42.0.117) 213.980 ms 1.208.105.141 (1.208.105.141) 216.979 ms
9 1.208.104.166 (1.208.104.166) 211.839 ms !N 1.208.104.194 (1.208.104.194) 214.205 ms !N 1.208.104.166 (1.208.104.166) 219.410 ms !N
root@ # ping na1.api.riotgames.com
PING rapi.redge.globalriot.aws-rclusterprod-usw1-1.riotapi.rc.pvp.net (104.160.150.26) 56(84) bytes of data.
64 bytes from 104.160.150.26 (104.160.150.26): icmp_seq=1 ttl=50 time=257 ms
64 bytes from 104.160.150.26 (104.160.150.26): icmp_seq=2 ttl=50 time=260 ms
64 bytes from 104.160.150.26 (104.160.150.26): icmp_seq=3 ttl=50 time=256 ms
^C
--- rapi.redge.globalriot.aws-rclusterprod-usw1-1.riotapi.rc.pvp.net ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 3ms
rtt min/avg/max/mdev = 256.319/257.835/260.417/1.925 ms
在此先感谢您的帮助！
法布西