I agree. Due to load the speed goes down. Will there be any permanent solution to solve this?
If you're talking about a solution from our (customer) side, then no. Only BSNL people can fix it by either upgrading their bandwidth according to number of customers, or by not taking more customers than their capacity.
But they will not do this unless we keep poking them, complaining etc. Or else, just be happy with the dial-up speed while they promise 3.2Mbps broadband (ha, even broadband is defined as 256 kbps in our country, sigh)
---------- Post added at 11:33 AM ---------- Previous post was at 11:27 AM ----------
lol, check this out which happens after I download something (normal, not torrent) for a long time, almost a minute lag! BSNL is awesome
shaan@shaan-
laptop:~$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_req=1 ttl=52 time=43897 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=51 time=47037 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=51 time=49372 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=52 time=50849 ms
64 bytes from 8.8.8.8: icmp_req=6 ttl=52 time=52402 ms
64 bytes from 8.8.8.8: icmp_req=7 ttl=52 time=52473 ms
64 bytes from 8.8.8.8: icmp_req=8 ttl=51 time=53497 ms
64 bytes from 8.8.8.8: icmp_req=9 ttl=52 time=56097 ms
64 bytes from 8.8.8.8: icmp_req=10 ttl=52 time=59733 ms
64 bytes from 8.8.8.8: icmp_req=11 ttl=51 time=60861 ms
64 bytes from 8.8.8.8: icmp_req=12 ttl=51 time=65455 ms
64 bytes from 8.8.8.8: icmp_req=13 ttl=51 time=67389 ms
64 bytes from 8.8.8.8: icmp_req=14 ttl=51 time=68666 ms
64 bytes from 8.8.8.8: icmp_req=15 ttl=51 time=70201 ms
64 bytes from 8.8.8.8: icmp_req=16 ttl=51 time=71132 ms
64 bytes from 8.8.8.8: icmp_req=17 ttl=51 time=71528 ms
64 bytes from 8.8.8.8: icmp_req=18 ttl=51 time=72041 ms
64 bytes from 8.8.8.8: icmp_req=19 ttl=51 time=75601 ms
64 bytes from 8.8.8.8: icmp_req=20 ttl=51 time=80092 ms