Ping 1586 ms

  • Thread starter Thread starter Deleted member 10390
  • Start date Start date
  • Replies Replies 19
  • Views Views 2,418
D

Deleted member 10390

ping 8.8.4.4

Pinging 8.8.4.4 with 32 bytes of data:
Reply from 8.8.4.4: bytes=32 time=1153ms TTL=57
Reply from 8.8.4.4: bytes=32 time=1245ms TTL=57
Reply from 8.8.4.4: bytes=32 time=1394ms TTL=57
Reply from 8.8.4.4: bytes=32 time=1586ms TTL=57

Ping statistics for 8.8.4.4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1153ms, Maximum = 1586ms, Average = 1344ms

God save BSNL !!!
 
Downloading at 100 - 150 KBps though.
 
BSNL DNS beats them by miles

ping Google

Pinging Google [74.125.236.47] with 32 bytes of data:
Reply from 74.125.236.47: bytes=32 time=3290ms TTL=56
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 74.125.236.47:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 3290ms, Maximum = 3290ms, Average = 3290ms


And download stops in between as well.
 
Firefox updating at 7.8 KBps :sigh:
 
Last edited by a moderator:
Luckily seems fixed now

ping www.google.com

Pinging www.google.com [74.125.236.52] with 32 bytes of data:
Reply from 74.125.236.52: bytes=32 time=49ms TTL=56
Reply from 74.125.236.52: bytes=32 time=49ms TTL=56
Reply from 74.125.236.52: bytes=32 time=55ms TTL=56
Reply from 74.125.236.52: bytes=32 time=49ms TTL=56

Ping statistics for 74.125.236.52:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 49ms, Maximum = 55ms, Average = 50ms
 
Again ..

ping Google

Pinging Google [74.125.236.52] with 32 bytes of data:
Reply from 74.125.236.52: bytes=32 time=49ms TTL=56
Reply from 74.125.236.52: bytes=32 time=49ms TTL=56
Reply from 74.125.236.52: bytes=32 time=55ms TTL=56
Reply from 74.125.236.52: bytes=32 time=49ms TTL=56

Ping statistics for 74.125.236.52:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 49ms, Maximum = 55ms, Average = 50ms
 

Now this is a real test of my patience. The bad connection persisted all through last 24 hours and wondering what happened to my ping statistics now. It looks different (currently on Google DNS)

ping Google
PING Google (74.125.236.48) 56(84) bytes of data.
64 bytes from maa03s04-in-f16.1e100.net (74.125.236.48): icmp_seq=1 ttl=56 time=8846 ms
64 bytes from maa03s04-in-f16.1e100.net (74.125.236.48): icmp_seq=2 ttl=56 time=8955 ms
64 bytes from maa03s04-in-f16.1e100.net (74.125.236.48): icmp_seq=3 ttl=56 time=8622 ms
64 bytes from maa03s04-in-f16.1e100.net (74.125.236.48): icmp_seq=4 ttl=56 time=8232 ms
64 bytes from maa03s04-in-f16.1e100.net (74.125.236.48): icmp_seq=5 ttl=56 time=7536 ms
64 bytes from maa03s04-in-f16.1e100.net (74.125.236.48): icmp_seq=6 ttl=56 time=6702 ms
64 bytes from maa03s04-in-f16.1e100.net (74.125.236.48): icmp_seq=7 ttl=56 time=6075 ms
64 bytes from maa03s04-in-f16.1e100.net (74.125.236.48): icmp_seq=8 ttl=56 time=5415 ms
64 bytes from maa03s04-in-f16.1e100.net (74.125.236.48): icmp_seq=9 ttl=56 time=4681 ms
64 bytes from maa03s04-in-f16.1e100.net (74.125.236.48): icmp_seq=10 ttl=56 time=5955 ms
64 bytes from maa03s04-in-f16.1e100.net (74.125.236.48): icmp_seq=11 ttl=56 time=5952 ms
64 bytes from maa03s04-in-f16.1e100.net (74.125.236.48): icmp_seq=12 ttl=56 time=5945 ms
64 bytes from maa03s04-in-f16.1e100.net (74.125.236.48): icmp_seq=13 ttl=56 time=5986 ms
64 bytes from maa03s04-in-f16.1e100.net (74.125.236.48): icmp_seq=14 ttl=56 time=6003 ms
64 bytes from maa03s04-in-f16.1e100.net (74.125.236.48): icmp_seq=15 ttl=56 time=5884 ms
64 bytes from maa03s04-in-f16.1e100.net (74.125.236.48): icmp_seq=16 ttl=56 time=5596 ms
64 bytes from maa03s04-in-f16.1e100.net (74.125.236.48): icmp_seq=17 ttl=56 time=5630 ms
 
Funny thing with BSNL, the employees get a fortune for a job they do. But if you are facing an issue with BSNL on a weekend, you are on your own. They talk of all those things like bad govt. policy helping private players, commitment and loss incurred in providing service in rural areas and what not. But can't spare someone to work on shifts and be available on weekends at least to ensure an up time. Most people use internet for day to day communication these days. Why would common man be sympathetic to BSNL ?
 
Actually NOT many common people, especially its customers are sympathetic to BSNL... And now here is coming a new nation wide strike by BSNL employees on March2015... Do you think there will be public support to those employees, who are doing 5% of the job done by pvt players' employees, but still getting more than thrice salary?
 
Here is the latest mess

ping Google
PING Google (74.125.236.212) 56(84) bytes of data.
64 bytes from 74.125.236.212: icmp_seq=1 ttl=56 time=6428 ms
64 bytes from 74.125.236.212: icmp_seq=2 ttl=56 time=6618 ms
64 bytes from 74.125.236.212: icmp_seq=3 ttl=56 time=6806 ms
64 bytes from 74.125.236.212: icmp_seq=4 ttl=56 time=6939 ms
64 bytes from 74.125.236.212: icmp_seq=5 ttl=56 time=7045 ms
64 bytes from 74.125.236.212: icmp_seq=6 ttl=56 time=7189 ms
64 bytes from 74.125.236.212: icmp_seq=7 ttl=56 time=7431 ms
64 bytes from 74.125.236.212: icmp_seq=8 ttl=56 time=5863 ms
64 bytes from 74.125.236.212: icmp_seq=9 ttl=56 time=4974 ms
64 bytes from 74.125.236.212: icmp_seq=10 ttl=56 time=4227 ms
64 bytes from 74.125.236.212: icmp_seq=11 ttl=56 time=3326 ms
64 bytes from 74.125.236.212: icmp_seq=12 ttl=56 time=5705 ms
64 bytes from 74.125.236.212: icmp_seq=13 ttl=56 time=5673 ms
64 bytes from 74.125.236.212: icmp_seq=14 ttl=56 time=5672 ms
64 bytes from 74.125.236.212: icmp_seq=15 ttl=56 time=5997 ms
64 bytes from 74.125.236.212: icmp_seq=16 ttl=56 time=6689 ms
64 bytes from 74.125.236.212: icmp_seq=17 ttl=56 time=7471 ms
64 bytes from 74.125.236.212: icmp_seq=18 ttl=56 time=7871 ms
 

Similar threads

P
  • Featured
Looks like BSNL enabled IPv6 in Telangana!
Replies
8
Views
773
!!..PD..!!
N
High Ping since a week
2 3 4 5 6
Replies
82
Views
6,560
nishantt6969
L
Unable to diagnose frequent downtime issue with my FTTH
Replies
6
Views
1,115
laboreddislodge
P
  • Solved
Exposing application on IPV6 Airtel Xstream for self hosting purpose
2
Replies
22
Views
2,270
panic0
Top