high ping since cyclone?

  • Thread starter Thread starter Ashurain
  • Start date Start date
  • Replies Replies 20
  • Views Views 5,825
Have a feeling this might not be fixed anytime soon.
Also the ACT customer care literally has no clue what am talking about :D
hi ashurain.. im currently facing same high ping this 2-3 months. im from bangalore. in spite their high ping they have good internet conection and no downtime so i wont be parting with it anytime. so if you can add me up and discuss or update each other about ping, it will be great. add me up on facebook - Chad kamei (profile name) plw_kamei@yahoo.com email...
or chadkamei - steam.. or you can drop ur id here and then i can add you. will bookmark this page.
 
hey guys, please check if the issue is fixed I had posted my problem about high pings to singapore servers from bangalore, they seem to have fixed it, your responses will be helpful
 
Relatively high pings to google. Is this new or old?
Code:
C:\>tracert google.com

Tracing route to google.com [216.58.197.46]
over a maximum of 30 hops:

  1    <1 ms     1 ms     1 ms  192.168.1.1
  2     2 ms     1 ms     1 ms  10.226.0.1
  3     *        2 ms     *     broadband.actcorp.in [103.16.203.186]
  4     2 ms     2 ms     2 ms  broadband.actcorp.in [103.16.203.138]
  5     *        *        *     Request timed out.
  6    35 ms    35 ms    35 ms  72.14.194.18
  7    35 ms    35 ms    35 ms  209.85.242.219
  8    36 ms    36 ms    36 ms  209.85.250.65
  9    36 ms    34 ms    34 ms  maa03s20-in-f14.1e100.net [216.58.197.46]

Trace complete.

Code:
C:\>tracert google.co.in

Tracing route to google.co.in [172.217.26.195]
over a maximum of 30 hops:

  1  <1 ms  <1 ms  <1 ms  192.168.1.1
  2  3 ms  2 ms  1 ms  10.226.0.1
  3  2 ms  *  2 ms  broadband.actcorp.in [103.16.203.186]
  4  2 ms  2 ms  3 ms  broadband.actcorp.in [103.16.203.138]
  5  *  *  *  Request timed out.
  6  35 ms  34 ms  34 ms  72.14.194.18
  7  34 ms  34 ms  34 ms  72.14.235.69
  8  35 ms  35 ms  35 ms  108.170.237.55
  9  35 ms  35 ms  35 ms  maa03s23-in-f3.1e100.net [172.217.26.195]

Trace complete.
 
Looks like they've done something about it. I've noticed it months ago but didn't bother about it. But soon after I posted about it.... Coincidence?
Code:
C:\>tracert google.com

Tracing route to google.com [216.58.197.46]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     9 ms     2 ms     1 ms  10.226.0.1
  3     3 ms     *        *     broadband.actcorp.in [103.16.203.186]
  4     8 ms     3 ms     2 ms  broadband.actcorp.in [103.16.203.138]
  5     4 ms     3 ms     3 ms  broadband.actcorp.in [103.16.203.106]
  6     3 ms     2 ms     2 ms  72.14.194.18
  7     3 ms     3 ms     3 ms  209.85.242.219
  8     3 ms     3 ms     3 ms  209.85.250.65
  9     3 ms     2 ms     2 ms  maa03s20-in-f14.1e100.net [216.58.197.46]

Trace complete.
Code:
C:\>tracert google.co.in

Tracing route to google.co.in [216.58.197.35]
over a maximum of 30 hops:

  1    <1 ms    <1 ms     1 ms  192.168.1.1
  2     2 ms     1 ms     1 ms  10.226.0.1
  3     *        *        2 ms  broadband.actcorp.in [103.16.203.186]
  4     2 ms     2 ms     2 ms  broadband.actcorp.in [103.16.203.138]
  5     6 ms     3 ms     4 ms  broadband.actcorp.in [103.16.203.106]
  6     3 ms     2 ms     3 ms  72.14.194.18
  7     3 ms     3 ms     3 ms  209.85.242.219
  8     3 ms     3 ms     3 ms  209.85.250.65
  9     3 ms     2 ms     2 ms  maa03s20-in-f35.1e100.net [216.58.197.35]

Trace complete.
 
Looks like there was an issue/maintenance with Google's Chennai POP and the traffic was diverted to Singapore. They have resolved it now.
 
I think the problem was at ACT's end.
Hop 5: ACT's end.
Hop 6: Google's end.
The host name of google's server also suggests that they are Chennai based.
 
Back