Airtel havin High/Unstable pings in Punjab or elsewhere?

  • Thread starter Thread starter sarcastic
  • Start date Start date
  • Replies Replies 10
  • Views Views 2,787
S

sarcastic

Newbie
Messages
11
Location
NA
ISP
Airtel
Anyone getting high or unstable pings having Airtel in Punjab?After Airtel has started applying FUP here (dey didn't count the data usage before in Jalandhar), from 8th April, I am getting high pings in daytime and it magically gets back to normal after 1:30 am. Complained to nodal office, a person visited my house and pinged some 202. ip which he got ping of 45 and said it is normal and cannot be reduced further.If anyone having issues plz post.Tracert for vs server, 2nd hop is itself showing 100ms :/Tracing route to 110.234.0.4 over a maximum of 30 hops 1 1 ms 1 ms 1 ms 192.168.1.1 2 105 ms 95 ms 90 ms 122.173.109.1 3 103 ms 88 ms * 122.176.125.46 4 52 ms 64 ms 85 ms 122.176.125.113 5 84 ms 76 ms 96 ms 125.19.76.117 6 79 ms 74 ms 75 ms 203.101.100.30 7 90 ms 91 ms 97 ms 218.100.48.31 8 91 ms 93 ms 66 ms 110.234.0.4Trace complete.
 
Me only? No one else? 🙁
 
I'm guessing that IP belongs to Tulip (?). Airtel does seem to be having problems with tulip ips as can be seen in the other threads.
 
I'm guessing that IP belongs to Tulip (?). Airtel does seem to be having problems with tulip ips as can be seen in the other threads.

Yes indeed dey are having problems wid tulip, but my point is dat the second hop in the tracert shows around 100ms and it is Airtel's router only....and for dis reason m getting unstable pings on every server (non-tulips also).
 
Would this be enough to tell these noobs that there is some problem at their end?Ping statistics for very first hop in the above tracert (their very own gateway):Reply from 122.173.109.1: bytes=32 time=81ms TTL=126Reply from 122.173.109.1: bytes=32 time=32ms TTL=126Reply from 122.173.109.1: bytes=32 time=54ms TTL=126Reply from 122.173.109.1: bytes=32 time=53ms TTL=126Reply from 122.173.109.1: bytes=32 time=51ms TTL=126Reply from 122.173.109.1: bytes=32 time=55ms TTL=126Reply from 122.173.109.1: bytes=32 time=63ms TTL=126Reply from 122.173.109.1: bytes=32 time=87ms TTL=126Reply from 122.173.109.1: bytes=32 time=78ms TTL=126Request timed out.Reply from 122.173.109.1: bytes=32 time=42ms TTL=126Reply from 122.173.109.1: bytes=32 time=90ms TTL=126Reply from 122.173.109.1: bytes=32 time=93ms TTL=126Reply from 122.173.109.1: bytes=32 time=32ms TTL=126Reply from 122.173.109.1: bytes=32 time=65ms TTL=126Reply from 122.173.109.1: bytes=32 time=42ms TTL=126Reply from 122.173.109.1: bytes=32 time=65ms TTL=126Reply from 122.173.109.1: bytes=32 time=78ms TTL=126Reply from 122.173.109.1: bytes=32 time=65ms TTL=126Reply from 122.173.109.1: bytes=32 time=39ms TTL=126Reply from 122.173.109.1: bytes=32 time=37ms TTL=126Reply from 122.173.109.1: bytes=32 time=70ms TTL=126Reply from 122.173.109.1: bytes=32 time=78ms TTL=126Reply from 122.173.109.1: bytes=32 time=56ms TTL=126Reply from 122.173.109.1: bytes=32 time=50ms TTL=126Reply from 122.173.109.1: bytes=32 time=92ms TTL=126Reply from 122.173.109.1: bytes=32 time=33ms TTL=126Look at the fluctuations :/And can u plz tell me that where shud I comlaint coz last time I complained to the nodal/appellate authority and dey sent a local guy to my house who said everything is fine...I dont want those illiterates to visit my house coz they have their own theories. He told me that ping upto 100 is all right and I was like rofl.I also told him that when ping increased there is a loss too....and guess what he told me " Sir copper loss hota h itna to." ....these bots have created there own protocol in which loss is acceptable xDShud I email directly to appellate officrer? Or shud I go for aritel presence?
 

Airtel presence worked well for me for dth, works well for most stuff. If all else fails, threaten them with disconnection. Ideally, pings to their own gateway should give you 5-6 ms on copper
 
I was facing the same problem in Delhi a few days ago. Exactly the same! High pings to their gateway no matter what server I connected to. But the problem lasted only for 4-5 hours. And then it got automatically corrected. Here's what I get when I ping to 202.56.215.55(Airtel DNS)Pinging 202.56.215.55 with 32 bytes of data:Reply from 202.56.215.55: bytes=32 time=25ms TTL=251Reply from 202.56.215.55: bytes=32 time=24ms TTL=251Reply from 202.56.215.55: bytes=32 time=24ms TTL=251Reply from 202.56.215.55: bytes=32 time=25ms TTL=251Ping statistics for 202.56.215.55: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 24ms, Maximum = 25ms, Average = 24ms@x720 How can you possibly get 5-6ms to your local gateway with copper? I mean DSL technology doesn't gives you such low pings...
 
Ping to their DNS is also dependent on their routers. Have a look:Tracing route to 202.56.215.55 over a maximum of 30 hops 1 1 ms 1 ms 1 ms 192.168.1.1 2 62 ms 42 ms 84 ms 122.173.109.1 3 47 ms 47 ms 60 ms 202.56.215.55Trace complete.The problem is again the 122.173.109.1 switch.....I hope dese airtel ppl understand what I am saying.
 
After banging my head in the wall wid airtel people, including appellate authority, the problem still persists....but I have done a bit of research by consulting other friends who have airtel, I have found out that the I am the only one facing high/unstable latency problem...But I dont understand is that what is the reason behind it....coz the only choice for me is to either myself recognize the fault and tell the airtel ppl or surrender my connection....Even a frnd of mine living 1 km away is not having any issue......any guesses about what cud be the source of this ?Reply from 122.173.109.1: bytes=32 time=77ms TTL=126Reply from 122.173.109.1: bytes=32 time=90ms TTL=126Reply from 122.173.109.1: bytes=32 time=93ms TTL=126Reply from 122.173.109.1: bytes=32 time=87ms TTL=126Reply from 122.173.109.1: bytes=32 time=65ms TTL=126Reply from 122.173.109.1: bytes=32 time=78ms TTL=126Reply from 122.173.109.1: bytes=32 time=65ms TTL=126Reply from 122.173.109.1: bytes=32 time=78ms TTL=126Reply from 122.173.109.1: bytes=32 time=65ms TTL=126Reply from 122.173.109.1: bytes=32 time=99ms TTL=126Reply from 122.173.109.1: bytes=32 time=100ms TTL=126Reply from 122.173.109.1: bytes=32 time=70ms TTL=126Reply from 122.173.109.1: bytes=32 time=86ms TTL=126
 

Top