Manky™, post: 93044, member: 15413 Wrote:What about me? i am getting 90 ms on valve servers in Singapore.
Double post
Thanx matt and bison ping is fixed now 
<3
Matt can u pls tell me waht did they do
Double post
Rockstar, post: 92574, member: 10627 Wrote:1} Guys heres the traceroute to 180.92.185.162 and 119.81.28.241
[attachment=2017][attachment=2018]
guys pls compare the two trace route , in the first it can reach singapore around 75 ms adn in the second my ping is going up y is taht guys ??/
The second one is going to Los Angeles, CA, U.S.A. before going to Singapore.
Guys like the another day today i m getting a ping of 250+ only leesss than 300 Here is the trace route (taken today)[
attachment=2045]
Now i think the problem is from your side because i have 14ms on my third hop which as you say is MTNL . Am i right?
Take a look at the Traceroute. I even checked on Pingtest.net & it gave me 75 ms for Singapore server hosted by Telin.
Rockstar, post: 93189, member: 10627 Wrote:Guys like the another day today i m getting a ping of 250+ only leesss than 300 Here is the trace route (taken today)
If BSNL fixes their routing you will have anywhere from 35ms to 50ms.
Note: The high latency on hop #11 and #12 are due to the reverse route (your end).
Traceroute to Rockstar Wrote:1 119.81.33.41-static.reverse.softlayer.com (119.81.33.41) 0.298 ms 0.337 ms 0.333 ms
2 ae11.dar02.sr03.sng01.networklayer.com (174.133.118.132) 39.999 ms 39.998 ms 40.037 ms
3 ae9.bbr01.eq01.sng02.networklayer.com (50.97.18.198) 0.796 ms 0.784 ms 0.787 ms
4 unknown.telstraglobal.net (202.126.128.17) 4.611 ms 4.612 ms 4.609 ms
5 i-2-0-0.istt-core01.bi.telstraglobal.net (202.84.180.157) 2.015 ms 2.081 ms 2.087 ms
6 i-0-2-0-0.6ntp02.bi.telstraglobal.net (202.84.243.114) 5.914 ms 5.225 ms 5.203 ms
7 ix-1-1-2-0.tcore2.svw-singapore.as6453.net (180.87.15.217) 3.642 ms 3.822 ms 3.613 ms
8 if-6-2.tcore2.CXR-Chennai.as6453.net (180.87.37.13) 50.396 ms if-5-2.tcore2.CXR-Chennai.as6453.net (180.87.15.70) 45.369 ms 35.564 ms
9 180.87.37.46 (180.87.37.46) 35.440 ms 35.437 ms 35.178 ms
10 * * *
11 115.114.130.50.STATIC-Chennai.vsnl.net.in (115.114.130.50) 219.839 ms 219.518 ms 219.793 ms
12 218.248.255.5 (218.248.255.5) 213.984 ms 213.939 ms 214.599 ms
13 * * *
Killer K, post: 93494, member: 16584 Wrote:Now i think the problem is from your side
Here's what our end looks like (you can see it goes straight to India):
Note: The high latency on hop #10 and #11 are due to the reverse route (your end).
Traceroute to Killer K Wrote:1 119.81.33.41-static.reverse.softlayer.com (119.81.33.41) 0.443 ms 0.531 ms 0.474 ms
2 ae11.dar02.sr03.sng01.networklayer.com (174.133.118.132) 0.190 ms 0.198 ms 0.196 ms
3 ae9.bbr01.eq01.sng02.networklayer.com (50.97.18.198) 0.757 ms 0.802 ms 0.799 ms
4 unknown.telstraglobal.net (202.126.128.17) 5.037 ms 5.033 ms 5.123 ms
5 i-2-0-0.istt-core01.bi.telstraglobal.net (202.84.180.157) 1.992 ms 1.990 ms 2.032 ms
6 i-0-2-0-0.6ntp02.bi.telstraglobal.net (202.84.243.114) 5.402 ms 5.238 ms 5.227 ms
7 ix-1-1-2-0.tcore2.SVW-Singapore.as6453.net (180.87.15.217) 3.871 ms 3.665 ms 31.813 ms
8 180.87.15.6 (180.87.15.6) 35.991 ms 35.255 ms 35.516 ms
9 * * *
10 121.244.68.101.static-lvsb.vsnl.net.in (121.244.68.101) 278.855 ms 280.817 ms 278.901 ms
11 static-mum-59.185.211.249.mtnl.net.in (59.185.211.249) 265.664 ms 264.589 ms 266.975 ms
12 * * *
What the helll :mad: When I contacted my ISP (MTNL) they said we dont have any facilty to lower your ping, we only test ping.Now there seems no way i could lower my ping
Killer K, post: 93566, member: 16584 Wrote:What the helll :mad: When I contacted my ISP (MTNL) they said we dont have any facilty to lower your ping, we only test ping.Now there seems no way i could lower my ping
ThatsWhatSheSaid^^^^^
Seems a bit stupid, why even bother testing the ping if they can't do anything about it. Seems like the call center drone just sold you a poor story. All ISP's have the capability to fix their routes, even if it's just talking to their upstream transit providers.
It seems changing my ISP is the only option now,isn't it?:confused:
give a threat to them that you will change your isp if they won't do anything about their routing issue.