Who are you?


  • Total voters
    61

sygeek

Technomancer
Not yet, here's mine (BSNL)

1 <1 ms <1 ms <1 ms D-Link.Home [192.168.1.1]
2 24 ms 23 ms 23 ms 117.197.32.1
3 25 ms 25 ms 35 ms 218.248.166.202
4 58 ms 57 ms 57 ms 218.248.181.18
5 289 ms 289 ms 288 ms jfk-edge-23.inet.qwest.net [63.148.22.161]
6 314 ms 314 ms 313 ms sgx-edge-05.inet.qwest.net [67.14.99.106]
7 316 ms 317 ms 316 ms 63.150.136.54
8 315 ms 315 ms 316 ms sgp-2.valve.net [103.10.124.1]

- - - Updated - - -

Niilesh, tell me when you are free to play? Can we do this now?
 

Piyush

Lanaya
C:\Users\Home_pc>tracert sgp-1.valve.net

Tracing route to sgp-1.valve.net [103.28.54.1]
over a maximum of 30 hops:

1 24 ms 33 ms 13 ms 10.171.0.1
2 33 ms 36 ms 13 ms 10.171.0.1
3 121 ms 137 ms 147 ms 202.88.216.21
4 121 ms 79 ms 82 ms 202.88.216.13
5 73 ms 59 ms 78 ms 202.88.216.1
6 94 ms 98 ms 83 ms 14.140.243.97.static-Delhi-vsnl.net.in [14.140.243.97]
7 166 ms 122 ms 116 ms 172.31.17.5
8 176 ms 162 ms 79 ms ix-4-2.tcore1.CXR-Chennai.as6453.net [180.87.36.9]
9 180 ms 179 ms 181 ms if-5-2.tcore1.SVW-Singapore.as6453.net [180.87.12.53]
10 190 ms 178 ms 166 ms 180.87.12.150
11 133 ms 177 ms 148 ms unknown.hwng.net [173.245.210.218]
12 170 ms 143 ms 119 ms 103-28-54-229.valve.net [103.28.55.229]
13 182 ms 142 ms 139 ms sgp [103.28.54.1]

Trace complete.

Hathway, Gzb
 
as6453.net < the laggy part of the routing. I've used their looking glass to ping my primary gateway and traceroute it. From what I can infer, it seems that all traffic are routed via Delhi for some reason. I can't confirm this because my search only deals with public ip databases and recorded information. What we all have been *****ing about is actually true, we have very shitty routing tables. Like I said to some people earlier, all the major gateway routers and cables are owned by tata telecom. Writing to them to improve their routing pathways might see some improvement. This is totally possible and it is in this shitty state because they can't possibly know such demand exists and for them delivery is probably more prioritized.

TL;DR Delhi/nearby places might get better pings than the rest of India in the case of BSNL customers. Delhi afaik has MTNL, and despite being the nation's largest internet provider BSNL can't do much, they buy their international bandwidth from TATA.
 

theserpent

Firecracker to the moon
Why not start a campaign on change.org for Tata and/or other ISPs to fix their routing tables?

No use mate.Airtel,BSNL,Tata won't do anything by hearing what HSR says or what a few 5-10% of the Indian broadband users say.

- - - Updated - - -

Well [MENTION=22610]hsr[/MENTION] try it out anyway,And also get the help from milton from dev.dota
 

arijitsinha

﴾͡๏̯͡๏﴿ O'RLY?
as6453.net < the laggy part of the routing. I've used their looking glass to ping my primary gateway and traceroute it. From what I can infer, it seems that all traffic are routed via Delhi for some reason. I can't confirm this because my search only deals with public ip databases and recorded information. What we all have been *****ing about is actually true, we have very shitty routing tables. Like I said to some people earlier, all the major gateway routers and cables are owned by tata telecom. Writing to them to improve their routing pathways might see some improvement. This is totally possible and it is in this shitty state because they can't possibly know such demand exists and for them delivery is probably more prioritized.

TL;DR Delhi/nearby places might get better pings than the rest of India in the case of BSNL customers. Delhi afaik has MTNL, and despite being the nation's largest internet provider BSNL can't do much, they buy their international bandwidth from TATA.

The main issue of the high ping is the routing goes like this,

India - > US
US -> Singapore.

While the local ISP's routing goes directly from India -> Singapore. Even it is goes by Delhi, not an issue.

Apart from this from my observation, when I give my personal PC's IP address, sometime it shows the location as Delhi, though I am in Chennai. So I believe that the DB where you querying for the IP address's location, does not have exact information for all the IP range. and it shows default as Delhi when it cannot find the exact state.
 
Yeah and that applies to the US ip as well, it is not exactly routed to US but it's an IP range under the country and hence we get the result as it being delivered to 'murica. Finding the location of an IP address by just using that specific IP address is just idiotic in my opinion, as you pointed out it can give you absurd results. What you have to do is do a tracert to the IP and get the gateway before the IP, find it's location. Chances are those IPs never change locations and we can confirm the location is correct.

- - - Updated - - -

Also when you do a tracert TO valve you get one route and that doesn't mean it comes back FROM valve via the same. For that we are helpless as there is no way to know but ask them. What we can do is find the gateways/routers through which it passes the packets and do a traceroute from them (almost all gateways allow this as it is mandatory to provide the same iirc).

- - - Updated - - -

No use mate.Airtel,BSNL,Tata won't do anything by hearing what HSR says or what a few 5-10% of the Indian broadband users say.

- - - Updated - - -

Well [MENTION=22610]hsr[/MENTION] try it out anyway,And also get the help from milton from dev.dota

Yeah, posting to that BSNL thread on dev.dota. [MENTION=149723]gta0gagan[/MENTION] is also there posting tracerts :lol:

- - - Updated - - -

On a side note, the 'murican NSA surveillance clauses say that every traffic that goes through US soil can be intercepted upon. Well good job BSNL, in you we trust!
 

Desmond

Destroy Erase Improve
Staff member
Admin
I have observed this when I was on Hathway. I used to get pings of around 65-70 ms.

Then when I moved to Tata Docomo Broadband, I get around 100-150 ms.
 

ACidBaseD

ACid DrinkeR
I used to get 300+ ping on MTNL mumbai until Q1 2013.. then they somehow fixed it.. Well I'm happy they did.

PM'd you the tracert results.
 
Last edited:
Updated, pings are normal now...
Code:
Tracing route to sgp-1.valve.net [103.28.54.1]
over a maximum of 30 hops:

  1     3 ms     3 ms     1 ms  D-Link.Home [192.168.1.1]
  2    31 ms    34 ms    31 ms  117.196.160.1
  3    31 ms    30 ms    31 ms  218.248.166.46
  4    83 ms    50 ms    48 ms  218.248.235.129
  5    47 ms    47 ms    92 ms  218.248.235.214
  6    47 ms    46 ms    60 ms  14.141.139.145.static-chennai.vsnl.net.in [14.141.139.145]
  7    92 ms    56 ms    57 ms  ix-4-2.tcore1.CXR-Chennai.as6453.net [180.87.36.9]
  8    79 ms    81 ms    80 ms  if-5-2.tcore1.SVW-Singapore.as6453.net [180.87.12.53]
  9    81 ms    80 ms    81 ms  180.87.12.154
 10    82 ms    82 ms    82 ms  unknown.hwng.net [173.245.210.218]
 11    85 ms    82 ms    82 ms  103-28-54-229.valve.net [103.28.55.229]
 12    82 ms    83 ms    83 ms  sgp-1.valve.net [103.28.54.1]

Trace complete.

And the traceroute back to my gateway from singapore:
Code:
Router: R1.SI (Singapore, SG)
lg@r1.si> traceroute 117.196.160.1 source 173.245.210.1 no-resolve wait 1 
 traceroute to 117.196.160.1 (117.196.160.1) from 173.245.210.1, 30 hops max, 40 byte packets
  1  180.87.12.149  0.478 ms  0.430 ms  0.438 ms
  2  180.87.98.37  18.632 ms  19.196 ms  18.630 ms
      MPLS Label=597952 CoS=0 TTL=1 S=1
  3  180.87.96.21  1.096 ms  1.073 ms  1.159 ms
  4  120.29.215.74  40.798 ms 120.29.214.6  1.089 ms 120.29.215.150  0.973 ms
  5  61.95.191.9  35.280 ms 61.95.210.146  34.571 ms  34.951 ms
  6  125.17.12.54  40.782 ms  41.974 ms  43.178 ms
  7  218.248.236.229  43.267 ms  43.166 ms  107.797 ms
  8  117.196.160.1  51.502 ms  53.043 ms  [B]52.210[/B] ms
 
 lg@r1.si>
 

gagan_kumar

Wise Old Owl
my tracert after fixing my routes manually...........


Code:
Tracing route to sgp-1.valve.net [103.28.54.1]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  ADSL [192.168.1.1]
  2    19 ms    19 ms    20 ms  117.192.48.1
  3    20 ms    19 ms    20 ms  218.248.160.42
  4    64 ms    27 ms    28 ms  218.248.235.213
  5    28 ms    27 ms    26 ms  218.248.235.214
  6     *       47 ms    46 ms  14.141.139.145
  7    48 ms    48 ms    47 ms  ix-4-2.tcore1.CXR-Chennai.as6453.net [180.87.36.
9]
  8    62 ms    61 ms    62 ms  if-5-2.tcore1.SVW-Singapore.as6453.net [180.87.1
2.53]
  9    63 ms    60 ms    62 ms  180.87.12.150
 10    63 ms    63 ms    63 ms  unknown.hwng.net [173.245.210.218]
 11    64 ms    63 ms    63 ms  103-28-54-229.valve.net [103.28.55.229]
 12    64 ms    64 ms    64 ms  sgp-1.valve.net [103.28.54.1]

Trace complete.
 

gagan_kumar

Wise Old Owl
TL;DR
Traffic is now routed via Bangalore(218.248.236.229) and that fixes the problems.

its temporary man soon ur pings will shoot up to 200-300........

- - - Updated - - -

Correct me if I'm wrong, but I don't think we can use our own (manual) routing once the packet leaves the primary gateway.

nope but we can choose our primary gateway can't we.........
 
Top Bottom