BSNL very slow speed and high pings

  • Thread starter Thread starter Realme
  • Start date Start date
  • Replies Replies 9
  • Views Views 906
Messages
999
Location
NA
ISP
BSNL
Yet another BSNL post to notify that my speeds are in kbps (Wish I didn't restart) and altho' when dns.google pings are greater than 20 ms is sign of BSNL network quality degrading, right now I'm getting 130+ ms to google dns..

Are you guys also experiencing the same?
 
Nope. It's probably just a localised issue in your area?
 
It Seems like that, I'll be waiting for others data.

If you don't mind sharing, what's your regional gateway?

 
BSNL has been working great for me for the past 2 and half months. No Downtime(16 hours of the day), Plan Speeds are consistent.
I am in the Bangalore region.
Pings are also good for my region.

Hope it remains like that
 
Last edited:
Not facing such an issue. Pings to dns.google are under 5ms. But my optical power is touching -31dbm and somehow connection is still working without any connection drop. Told about the issue to LCO, he doesn't care until the connection stop working completely.
And the gateway assing to me right now is 59.91.104.1
 
Last edited:
@Realme Seems to be a localised issue for you. Pings to google dns are between 15-20ms and cloud flare between 25-30ms.

traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 38 byte packets
1 xx.xxx.xxx.xxx (x.x.x.x) 0.000 ms 0.000 ms 0.000 ms
2 218.248.170.131 (218.248.170.131) 10.000 ms 0.000 ms 0.000 ms
3 static.ill.218.248.108.14/24.bsnl.in (218.248.108.14) 0.000 ms 10.000 ms 0.000 ms
4 * * *
5 * * *
6 72.14.211.114 (72.14.211.114) 20.000 ms 72.14.218.250 (72.14.218.250) 20.000 ms 20.000 ms
7 10.252.188.222 (10.252.188.222) 20.000 ms 74.125.242.145 (74.125.242.145) 20.000 ms 10.252.171.190 (10.252.171.190) 20.000 ms
8 142.251.55.73 (142.251.55.73) 20.000 ms dns.google (8.8.8.8) 20.000 ms 20.000 ms
 


Last edited:
I dunno how to check gateway on my phone I haven't installed any terminal but I'm in Pune with 117 series ip address.
 
i m facing the same issue
Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=318ms TTL=117
Reply from 8.8.8.8: bytes=32 time=273ms TTL=117
Reply from 8.8.8.8: bytes=32 time=321ms TTL=117
Reply from 8.8.8.8: bytes=32 time=241ms TTL=117

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


from your post connected to 117.216.207.202 , or 203 one
117.222 ip set
 
Things are back to normal on my end.

Has things improved for you @JSMFPPJK

Hey @pillaicha , notice those two * rows just be fore 72.xx ip, those are regional gateways[ Earlier they were easily resolvable now BSNL adds some kind of packet loss, that if you don't ping them twice or thrice, they don't reveal themselves]
Edit your post to remove your LCO gateway
 
Yes they are, also i noticed something on cloudflare warp. Earlier i used to get a london ip now i get a mumbai one which is great and ping gets better using warp, which earlier for me would get worst.
Only if BSNL peers directly with cloudflare then i would get less than 40ms to cloudflare and my pings will be awesome.
I am from Kashmir getting 40-60 ms to cloudflare.
 
Last edited:

Back