Is this why my net is slow/unstable?

  • Thread starter Thread starter liverpool79
  • Start date Start date
  • Replies Replies 16
  • Views Views 3,683
L

liverpool79

Newbie
Messages
212
Location
Bangalore
ISP
Airtel
Since yesterday afternoon my connection is slow/unstable.For 3 hours it was down,called CC to complain.They have not called back yet.I did some speedtest and pings just to check.

Are these normal?

Pinging google.com:
Reply from 172.217.26.206: bytes=32 time=2419ms TTL=55
Reply from 172.217.26.206: bytes=32 time=3010ms TTL=55
Reply from 172.217.26.206: bytes=32 time=2907ms TTL=55
Reply from 172.217.26.206: bytes=32 time=1948ms TTL=55
Reply from 172.217.26.206: bytes=32 time=1816ms TTL=55
Reply from 172.217.26.206: bytes=32 time=1993ms TTL=55
Reply from 172.217.26.206: bytes=32 time=1874ms TTL=55
Reply from 172.217.26.206: bytes=32 time=2730ms TTL=55
Reply from 172.217.26.206: bytes=32 time=2544ms TTL=55
Reply from 172.217.26.206: bytes=32 time=2293ms TTL=55
Reply from 172.217.26.206: bytes=32 time=2466ms TTL=55
Reply from 172.217.26.206: bytes=32 time=1625ms TTL=55
Reply from 172.217.26.206: bytes=32 time=1460ms TTL=55
Reply from 172.217.26.206: bytes=32 time=1515ms TTL=55
Request timed out.
Reply from 172.217.26.206: bytes=32 time=2242ms TTL=55
Reply from 172.217.26.206: bytes=32 time=2515ms TTL=55
Reply from 172.217.26.206: bytes=32 time=3204ms TTL=55
Reply from 172.217.26.206: bytes=32 time=2320ms TTL=55
Reply from 172.217.26.206: bytes=32 time=1833ms TTL=55
Reply from 172.217.26.206: bytes=32 time=3084ms TTL=55
Reply from 172.217.26.206: bytes=32 time=2408ms TTL=55
Request timed out.
Request timed out.
Reply from 172.217.26.206: bytes=32 time=2140ms TTL=55
Reply from 172.217.26.206: bytes=32 time=3212ms TTL=55
Reply from 172.217.26.206: bytes=32 time=2382ms TTL=55
Reply from 172.217.26.206: bytes=32 time=1466ms TTL=55
Reply from 172.217.26.206: bytes=32 time=1973ms TTL=55
Reply from 172.217.26.206: bytes=32 time=1868ms TTL=55
Reply from 172.217.26.206: bytes=32 time=2108ms TTL=55
Reply from 172.217.26.206: bytes=32 time=3004ms TTL=55
Reply from 172.217.26.206: bytes=32 time=1681ms TTL=55
Reply from 172.217.26.206: bytes=32 time=2052ms TTL=55
Reply from 172.217.26.206: bytes=32 time=1958ms TTL=55
Reply from 172.217.26.206: bytes=32 time=1987ms TTL=55
Reply from 172.217.26.206: bytes=32 time=2429ms TTL=55
Reply from 172.217.26.206: bytes=32 time=2885ms TTL=55
Reply from 172.217.26.206: bytes=32 time=2493ms TTL=55
Request timed out.
Reply from 172.217.26.206: bytes=32 time=2428ms TTL=55
Reply from 172.217.26.206: bytes=32 time=2346ms TTL=55
Reply from 172.217.26.206: bytes=32 time=3257ms TTL=55
Reply from 172.217.26.206: bytes=32 time=2629ms TTL=55
Reply from 172.217.26.206: bytes=32 time=2106ms TTL=55
Reply from 172.217.26.206: bytes=32 time=2328ms TTL=55
Reply from 172.217.26.206: bytes=32 time=3076ms TTL=55
Request timed out.
Reply from 172.217.26.206: bytes=32 time=2999ms TTL=55
Reply from 172.217.26.206: bytes=32 time=2685ms TTL=55
Reply from 172.217.26.206: bytes=32 time=2661ms TTL=55
Reply from 172.217.26.206: bytes=32 time=3014ms TTL=55
Reply from 172.217.26.206: bytes=32 time=1930ms TTL=55
Request timed out.
Request timed out.
Reply from 172.217.26.206: bytes=32 time=1811ms TTL=55
Request timed out.
Request timed out.
Click to expand...
 
So now while trying to log into a site,captcha is failing:
The page at google.com says:

Cannot contact reCAPTCHA.Check your connection and try again.
Click to expand...

Did i mention that loading this forum (broadbandforum) is very slow as well?
 
Yes,those times did look really slow.

Spoke to CC,they made me change my router/modem secondary DNS and gave me a new one.Not much changed except my speed increased a little bit more to around .49-.80 (it's fluctuating) Mbps,still well short of my 1 Mbps.And now Captcha is working.


Check out my Internet Speed! What's your speed?
Check out my Internet Speed! What's your speed?
Check out my Internet Speed! What's your speed?

Pinging google.com [172.217.31.206] with 32 bytes of data:

Request timed out.
Reply from 172.217.31.206: bytes=32 time=2340ms TTL=56
Request timed out.
Request timed out.
Reply from 172.217.31.206: bytes=32 time=1794ms TTL=56
Reply from 172.217.31.206: bytes=32 time=1661ms TTL=56
Reply from 172.217.31.206: bytes=32 time=1878ms TTL=56
Reply from 172.217.31.206: bytes=32 time=1971ms TTL=56
Request timed out.
Reply from 172.217.31.206: bytes=32 time=1111ms TTL=56
Request timed out.
Reply from 172.217.31.206: bytes=32 time=309ms TTL=56
Reply from 172.217.31.206: bytes=32 time=202ms TTL=56
Reply from 172.217.31.206: bytes=32 time=81ms TTL=56
Reply from 172.217.31.206: bytes=32 time=179ms TTL=56
Reply from 172.217.31.206: bytes=32 time=167ms TTL=56
Reply from 172.217.31.206: bytes=32 time=128ms TTL=56
Reply from 172.217.31.206: bytes=32 time=127ms TTL=56
Reply from 172.217.31.206: bytes=32 time=227ms TTL=56
Reply from 172.217.31.206: bytes=32 time=92ms TTL=56
Reply from 172.217.31.206: bytes=32 time=80ms TTL=56
Reply from 172.217.31.206: bytes=32 time=147ms TTL=56
Reply from 172.217.31.206: bytes=32 time=322ms TTL=56
Reply from 172.217.31.206: bytes=32 time=126ms TTL=56
Reply from 172.217.31.206: bytes=32 time=144ms TTL=56
Reply from 172.217.31.206: bytes=32 time=132ms TTL=56
Reply from 172.217.31.206: bytes=32 time=159ms TTL=56
Reply from 172.217.31.206: bytes=32 time=329ms TTL=56
Reply from 172.217.31.206: bytes=32 time=131ms TTL=56
Reply from 172.217.31.206: bytes=32 time=102ms TTL=56
Reply from 172.217.31.206: bytes=32 time=107ms TTL=56
Reply from 172.217.31.206: bytes=32 time=79ms TTL=56
Reply from 172.217.31.206: bytes=32 time=538ms TTL=56
Reply from 172.217.31.206: bytes=32 time=935ms TTL=56
Reply from 172.217.31.206: bytes=32 time=766ms TTL=56
Reply from 172.217.31.206: bytes=32 time=739ms TTL=56
Reply from 172.217.31.206: bytes=32 time=415ms TTL=56
Reply from 172.217.31.206: bytes=32 time=2267ms TTL=56
Reply from 172.217.31.206: bytes=32 time=1565ms TTL=56
Reply from 172.217.31.206: bytes=32 time=1281ms TTL=56
Reply from 172.217.31.206: bytes=32 time=797ms TTL=56
Reply from 172.217.31.206: bytes=32 time=523ms TTL=56
Reply from 172.217.31.206: bytes=32 time=198ms TTL=56
Reply from 172.217.31.206: bytes=32 time=343ms TTL=56
Reply from 172.217.31.206: bytes=32 time=97ms TTL=56
Reply from 172.217.31.206: bytes=32 time=86ms TTL=56
Reply from 172.217.31.206: bytes=32 time=90ms TTL=56
Click to expand...


Pinging my public IP.What is this "General failure" ???
Pinging 122.xxx.xxx.xxx with 32 bytes of data:

Reply from my public ip: bytes=32 time=1ms TTL=64
General failure.
Reply from 122.: bytes=32 time=1ms TTL=64
Reply from 122.: bytes=32 time=1ms TTL=64
Reply from 122.: bytes=32 time=1ms TTL=64
Reply from 122.: bytes=32 time=1ms TTL=64
Reply from 122.: bytes=32 time=1ms TTL=64
Reply from 122.: bytes=32 time=1ms TTL=64
Reply from 122.: bytes=32 time=4ms TTL=64
Reply from 122.: bytes=32 time=1ms TTL=64
Reply from 122.: bytes=32 time=1ms TTL=64
Reply from 122.: bytes=32 time=1ms TTL=64
General failure.
Reply from 122.: bytes=32 time=1ms TTL=64
Reply from 122.: bytes=32 time=3ms TTL=64
Reply from 122.: bytes=32 time=1ms TTL=64
Reply from 122.: bytes=32 time=1ms TTL=64
Reply from 122.: bytes=32 time=1ms TTL=64
Reply from 122.: bytes=32 time=1ms TTL=64
Reply from 122.: bytes=32 time=1ms TTL=64
Reply from 122.: bytes=32 time=1ms TTL=64
Reply from 122.: bytes=32 time=1ms TTL=64
Reply from 122.: bytes=32 time=21ms TTL=64
Reply from 122.: bytes=32 time=33ms TTL=64
Reply from 122.: bytes=32 time=1ms TTL=64
Click to expand...
 
your pings are still fluctuating a lot. are you sure your wiring is fine?
 

Sushubh said:
your pings are still fluctuating a lot. are you sure your wiring is fine?
Click to expand...

Well,the wiring to modem/router looks fine when i checked, 4 green lights on router/modem as usual.I should add that my Airtel landline is dead though.


@Karan

Is that the 'statistics' page my router/modem product page?

Screenshot of whole page or only the ADSL stats?
 
Thanks, those numbers are all messed up, the upstream is especially poor. Since your line is also dead, that means this is definitely line trouble. This is something you can't fix, airtel has to fix this. When you called airtel, did you complain about slow speeds or dead phone line? If it has been more than 4 hours, call back and ask for an update. If they don't give you a straight forward reply, escalate to a supervisor.
 
Actually i lodged the complaint yesterday 3 pm when net stopped working completely.It resumed working at 6pm same day and since then has been slow.CC did not call me,in fact i called them a second time today 2 pm to inform about slow speeds.

They knew about the dead line since yesterday.the complaint is still open.
 
hows the airtel guys at your place? at my place, i just take the number of the local guy and call him directly after filing a complaint through twitter.
 
Ok, the slow speeds are a result of the line being dead/not working properly. Whenever you have a dead phone line and net not working or working slowly, just complain about the phone, most of the time, when the phone gets fixed, the net also gets restored at the same time.

Call them again, ask what is taking so long to fix this? They usually give a 4 hours time to respond to the issue. It has been way more than that.
 

Similar threads

N
High Ping since a week
2 3 4 5 6
Replies
82
Views
6,528
nishantt6969
havoc
Ping/Traceroute Test & Results
Replies
5
Views
1,206
havoc
L
Unable to diagnose frequent downtime issue with my FTTH
Replies
6
Views
1,112
laboreddislodge
P
  • Locked
Poorly performing Airtel Xstream Fibre
Replies
7
Views
915
Tejas01
Top