Slow Download speeds on most servers

  • Thread starter Thread starter Sanchit3412
  • Start date Start date
  • Replies Replies 38
  • Views Views 3,618
Messages
59
Location
Jammu
ISP
BSNL Bharat Fiber, Airtel Xstream Fiber
Download speeds on most servers are very slow. All speed tests ( Fast, Ookla, BSNL) except the Google one are showing down speeds b/w 30-60 Mbps but the upload speeds seem to be constant everywhere. Download speed on Steam is also very slow. I am on the 799 Plan. Speeds on Google Apps (Play STORE, YouTube etc) are fine. (Google Speed test is showing 110 up and down.)
 
Internet Speed Test (30 Mbps down and 100 up)





Google Speed test -
Source



Source
 
Last edited:
Yes today the internet is unusable and I am using mobile data at home for the first time after BSNL fibre connection.
 


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
 
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
40-45ms for me on the same.
 
LOL something is wrong , now Cloudflare ping is jumped to 300+ ms for me 😀

Pinging 1.1.1.1 with 32 bytes of data:
Reply from 1.1.1.1: bytes=32 time=316ms TTL=54
Reply from 1.1.1.1: bytes=32 time=333ms TTL=54
Reply from 1.1.1.1: bytes=32 time=363ms TTL=54
Reply from 1.1.1.1: bytes=32 time=341ms TTL=54
Reply from 1.1.1.1: bytes=32 time=345ms TTL=54
Reply from 1.1.1.1: bytes=32 time=337ms TTL=54
Reply from 1.1.1.1: bytes=32 time=321ms TTL=54
Reply from 1.1.1.1: bytes=32 time=340ms TTL=54
Reply from 1.1.1.1: bytes=32 time=319ms TTL=54

Ping statistics for 1.1.1.1:
Packets: Sent = 9, Received = 9, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 316ms, Maximum = 363ms, Average = 335ms
 
Again back to normal now

Pinging 1.1.1.1 with 32 bytes of data:
Reply from 1.1.1.1: bytes=32 time=38ms TTL=54
Reply from 1.1.1.1: bytes=32 time=37ms TTL=54
Reply from 1.1.1.1: bytes=32 time=36ms TTL=54
Reply from 1.1.1.1: bytes=32 time=38ms TTL=54
Reply from 1.1.1.1: bytes=32 time=40ms TTL=54
Reply from 1.1.1.1: bytes=32 time=37ms TTL=54
Reply from 1.1.1.1: bytes=32 time=37ms TTL=54
Reply from 1.1.1.1: bytes=32 time=37ms TTL=54
Reply from 1.1.1.1: bytes=32 time=37ms TTL=54
Reply from 1.1.1.1: bytes=32 time=37ms TTL=54
Reply from 1.1.1.1: bytes=32 time=37ms TTL=54
Reply from 1.1.1.1: bytes=32 time=37ms TTL=54
Reply from 1.1.1.1: bytes=32 time=36ms TTL=54
Reply from 1.1.1.1: bytes=32 time=37ms TTL=54
Reply from 1.1.1.1: bytes=32 time=37ms TTL=54

Ping statistics for 1.1.1.1:
Packets: Sent = 15, Received = 15, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 36ms, Maximum = 40ms, Average = 37ms
 

Top