Anyone facing crazy latency to google and cloudflare right now?

  • Thread starter Thread starter sloj
  • Start date Start date
  • Replies Replies 8
  • Views Views 1,038
sloj

sloj

Disconnected
Messages
1,776
Location
Guwahati
ISP
BSNL
Code: 
Pinging 1.1.1.1 with 32 bytes of data:
Request timed out.
Reply from 1.1.1.1: bytes=32 time=1243ms TTL=56
Reply from 1.1.1.1: bytes=32 time=1266ms TTL=56
Reply from 1.1.1.1: bytes=32 time=1276ms TTL=56

Code: 
Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=1596ms TTL=113
Request timed out.
Request timed out.
Request timed out.

BSNL DNS seems to be doing fine although 61.1.1.1 is a little higher than usual under 20 ms.

Code: 
Pinging 61.1.1.1 with 32 bytes of data:
Reply from 61.1.1.1: bytes=32 time=56ms TTL=251
Reply from 61.1.1.1: bytes=32 time=55ms TTL=251
Reply from 61.1.1.1: bytes=32 time=55ms TTL=251
Reply from 61.1.1.1: bytes=32 time=56ms TTL=251

Code: 
Pinging 218.248.112.225 with 32 bytes of data:
Reply from 218.248.112.225: bytes=32 time=8ms TTL=251
Reply from 218.248.112.225: bytes=32 time=8ms TTL=251
Reply from 218.248.112.225: bytes=32 time=10ms TTL=251
Reply from 218.248.112.225: bytes=32 time=8ms TTL=251
 
I get this when my assigned IP is 59.xx or some 117.xx too. Was getting over 500ms to google. Restart the modem, you'll get a new IP. Rinse and repeat till you find a good one and don't turn off. Mine current is a good 117.xx and it's about 20-30ms.
 
Things are normal now. Temporary issues. I had it yesterday afternoon too. I always get 117.x.x.x since June 2nd. Now it's 117.241.x.x. Didn't have to restart.

Code: 
Pinging 1.1.1.1 with 32 bytes of data:
Reply from 1.1.1.1: bytes=32 time=48ms TTL=56
Reply from 1.1.1.1: bytes=32 time=48ms TTL=56
Reply from 1.1.1.1: bytes=32 time=49ms TTL=56
Reply from 1.1.1.1: bytes=32 time=49ms TTL=56

Code: 
Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=69ms TTL=113
Reply from 8.8.8.8: bytes=32 time=70ms TTL=113
Reply from 8.8.8.8: bytes=32 time=69ms TTL=113
Reply from 8.8.8.8: bytes=32 time=70ms TTL=113

Code: 
Pinging 61.1.1.1 with 32 bytes of data:
Reply from 61.1.1.1: bytes=32 time=18ms TTL=251
Reply from 61.1.1.1: bytes=32 time=17ms TTL=251
Reply from 61.1.1.1: bytes=32 time=19ms TTL=251
Reply from 61.1.1.1: bytes=32 time=18ms TTL=251

Code: 
Pinging 218.248.112.225 with 32 bytes of data:
Reply from 218.248.112.225: bytes=32 time=10ms TTL=251
Reply from 218.248.112.225: bytes=32 time=8ms TTL=251
Reply from 218.248.112.225: bytes=32 time=8ms TTL=251
Reply from 218.248.112.225: bytes=32 time=9ms TTL=251
 
dkdhanda8 said:
Suffering from bad ping and low internet speed since morning on 59.xx.xx.xx
Click to expand...

I've rebooted countless times. Got the 59.xx and 117.xx gateway. Both of them responds under 20ms sometimes and sometimes over 1000ms. I've stopped blaming the IPs.

Your download speed issue could be fixed by rebooting if it's that severe. I have noticed uploads are unaffected all the time.

It's entirely dependent on BSNL's load.
 

For me usually 117.xx is better , on 59.xx IP range I was getting download speed of 3-5ish Mbps and upload of 39mbps , maybe BSNL exchange was upgrading stuff? Or something who knows. Rebooted ont multiple times in the morning kept getting 59.xx and low speed at that time , now it's fixed .

@slog fiber to my city is connected from other city I think , and normally ping to ookla Servers is 10-20 ms , on 59.xx I was getting more than 150-200 on nearest server , ping test to all DNS except BSNL 61.1.1.1 and other was above 100 ( Google and cloudflared is usually in low ranges)
 
Could be traffic congestion. I was getting slightly above 100 ms on cloudflare, google was fine when you posted. But it's still better to test by downloading some file than using test servers on Ookla.
 

Top