High Ping on Amazon EC2 servers (PUBG, Fortnite and Overwatch)

[arzain.macabale]

[Moderator Note: Moving post to Networking.]

I've been having this recurring problem with my ISP and I feel so in the dark about it since the people that answer their support hotlines don't provide you much information. I'm from the Philippines and my family is subscribed to PLDT's 50mbps Fiber. I'm getting high ping ONLY on games that use Amazon servers like the ones mentioned in the title. I usually get 30ms when playing on Singapore servers but now it's constant 200ms. I play other games like DotA 2, CS:GO and Rainbow Six Siege but I get 30ms in those games, why is it only with Amazon servers? I want to know whether or not if it's my ISP's fault, the area I live in or Amazon's. I have friends who are subscribed to PLDT as well but don't have this problem. Here's a traceroute of mine to one of Amazon's Singapore servers.

C:\Users\arzain>tracert 54.254.128.1

Tracing route to ec2-54-254-128-1.ap-southeast-1.compute.amazonaws.com [54.254.128.1]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms router.asus.com [192.168.2.1]
2 1 ms 1 ms 1 ms 192.168.1.1
3 3 ms 2 ms 2 ms 119.94.176.1.static.pldt.net [119.94.176.1]
4 2 ms 2 ms 2 ms 124.106.9.230
5 5 ms 3 ms 2 ms 210.213.131.62.static.pldt.net [210.213.131.62]
6 2 ms 2 ms 2 ms 122.2.175.30.static.pldt.net [122.2.175.30]
7 3 ms 2 ms 2 ms 210.213.130.170.static.pldt.net [210.213.130.170]
8 203 ms 202 ms 203 ms 116.51.31.169
9 209 ms 204 ms 204 ms ae-0.a00.sngpsi05.sg.bb.gin.ntt.net [129.250.7.9]
10 209 ms 209 ms 209 ms ae-6.r01.sngpsi07.sg.bb.gin.ntt.net [129.250.7.26]
11 203 ms 202 ms 202 ms ae-1.a01.sngpsi07.sg.bb.gin.ntt.net [129.250.2.240]
12 199 ms 199 ms 199 ms ae-1.amazon.sngpsi07.sg.bb.gin.ntt.net [116.51.17.130]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 200 ms 199 ms 199 ms 203.83.223.29
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 199 ms 199 ms 199 ms ec2-54-254-128-1.ap-southeast-1.compute.amazonaws.com [54.254.128.1]

Trace complete.

Pinging 54.254.128.1 with 32 bytes of data:
Reply from 54.254.128.1: bytes=32 time=200ms TTL=234
Reply from 54.254.128.1: bytes=32 time=199ms TTL=234
Reply from 54.254.128.1: bytes=32 time=199ms TTL=234
Reply from 54.254.128.1: bytes=32 time=200ms TTL=234

Ping statistics for 54.254.128.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 199ms, Maximum = 200ms, Average = 199ms

 

[bill001g]

You could try 8.8.8.8 and see if that is different. It is a google dns server that they duplicate the ip in many locations. It generally has very low latency.

All you can say is your ISP has a issue connecting the ISP NTT in hop 8. You would have to try to find other IP addresses that do not go via NTT.

It is nothing at your end in any case you can not do anything about the path traffic takes in the internet. Your ISP may have a problem with one of their interconnects to other ISP. You would think they know about this and are working on it. It could be on a backup path if the main has something like a fiber cut.

If is stays that way hopefully their connectivity to other ISP is better. You could then attempt to look for a VPN service on one of those other ISP. Not the best solution but not much else if the ISP does not correct this issue.