Same issue from me as well , this started around 12PM . getting relatively high ping and packet loss to AWS servers.
I usually et 40-45ms to Mumbai AWS servers
Pinging 13.126.0.252 with 32 bytes of data:
Reply from 13.126.0.252: bytes=32 time=65ms TTL=234
Request timed out.
Request timed out.
Reply from 13.126.0.252: bytes=32 time=65ms TTL=234
Request timed out.
Reply from 13.126.0.252: bytes=32 time=65ms TTL=234
Reply from 13.126.0.252: bytes=32 time=65ms TTL=234
Reply from 13.126.0.252: bytes=32 time=65ms TTL=234
Reply from 13.126.0.252: bytes=32 time=65ms TTL=234
Reply from 13.126.0.252: bytes=32 time=66ms TTL=234
Reply from 13.126.0.252: bytes=32 time=65ms TTL=234
Reply from 13.126.0.252: bytes=32 time=65ms TTL=234
Reply from 13.126.0.252: bytes=32 time=66ms TTL=234
Reply from 13.126.0.252: bytes=32 time=65ms TTL=234
Reply from 13.126.0.252: bytes=32 time=65ms TTL=234
Reply from 13.126.0.252: bytes=32 time=65ms TTL=234
Reply from 13.126.0.252: bytes=32 time=66ms TTL=234
Reply from 13.126.0.252: bytes=32 time=65ms TTL=234
Reply from 13.126.0.252: bytes=32 time=65ms TTL=234
Reply from 13.126.0.252: bytes=32 time=65ms TTL=234
Reply from 13.126.0.252: bytes=32 time=66ms TTL=234
Reply from 13.126.0.252: bytes=32 time=66ms TTL=234
Reply from 13.126.0.252: bytes=32 time=66ms TTL=234
Request timed out.
Request timed out.
Reply from 13.126.0.252: bytes=32 time=66ms TTL=234
Reply from 13.126.0.252: bytes=32 time=65ms TTL=234
Reply from 13.126.0.252: bytes=32 time=65ms TTL=234
Ping statistics for 13.126.0.252:
Packets: Sent = 28, Received = 23, Lost = 5 (17% loss),
Approximate round trip times in milli-seconds:
Minimum = 65ms, Maximum = 66ms, Average = 65ms