Server routing issue

[wo0dy .gFN-]

Hi

I am based in India and regularly play CS GO but have been having trouble from last week. There are 2 server locations in India - Mumbai & Chennai. Being in India, I should automatically connect to either of these. However, I have been unable to find a direct route to either of these 2 servers and God knows why, I am getting a direct route to Hong Kong & Singapore servers. I have always played over WIFI so that should not be an issue now. However, I did try connecting a LAN cable to my modem and using it, but same result. I am getting pings which are in triple digits when I connect to my own country's servers. Can someone please help me solve this issue asap? Below is the ping info from the game's console.

Refreshing ping measurements
RelayNetWorkStatus: avail=OK config=OK anyrelay=OK (Refreshing ping measurements)
Relay sto#153 (162.254.198.103:27027) is going offline in 249 seconds
Ping measurement has been active for 5.0s. Sending what we have to GC
ams: 121ms via par (front=111ms, back=10ms)
atl: 200ms via par (front=111ms, back=89ms)
bom: 114ms via sgp (front=63ms, back=51ms)
can: 228ms via cant (front=228ms, back=0ms)
canm: 228ms via cant (front=228ms, back=0ms)
cant: 228ms via direct route
canu: 228ms via cant (front=228ms, back=0ms)
dxb: 140ms via sgp (front=63ms, back=77ms)
eat: 217ms via sea (front=212ms, back=5ms)
fra: 120ms via par (front=111ms, back=9ms)
gru: 331ms via par (front=111ms, back=220ms)
hkg: 92ms via sgp (front=63ms, back=29ms)
iad: 187ms via par (front=111ms, back=76ms)
jnb: 275ms via par (front=111ms, back=164ms)
lax: 228ms via direct route
lhr: 119ms via par (front=111ms, back=8ms)
lim: 301ms via direct route
lux: 116ms via par (front=111ms, back=5ms)
maa: 95ms via sgp (front=63ms, back=32ms)
mad: 130ms via par (front=111ms, back=19ms)
okc: 224ms via par (front=111ms, back=113ms)
ord: 203ms via par (front=111ms, back=92ms)
par: 111ms via direct route
pwg: 238ms via direct route
pwj: 368ms via direct route
pwu: 358ms via direct route
pww: 244ms via direct route
pwz: 256ms via direct route
scl: 330ms via lim (front=301ms, back=29ms)
sea: 212ms via direct route
sgp: 64ms via direct route
sha: 201ms via shau (front=201ms, back=0ms)
sham: 201ms via shau (front=201ms, back=0ms)
shat: 201ms via shau (front=201ms, back=0ms)
shau: 201ms via direct route
shb: 261ms via direct route
sto: 139ms via par (front=111ms, back=28ms)
sto2: 140ms via par (front=111ms, back=29ms)
syd: 289ms via direct route
tsn: 248ms via tsnt (front=248ms, back=0ms)
tsnm: 248ms via tsnt (front=248ms, back=0ms)
tsnt: 248ms via direct route
tsnu: 248ms via tsnt (front=248ms, back=0ms)
tyo: 146ms via sgp (front=63ms, back=83ms)
tyo1: 146ms via sgp (front=63ms, back=83ms)
vie: 125ms via direct route
waw: 136ms via par (front=111ms, back=25ms)
Ping measurement completed
Ping location: sgp=63+6/64+6,hkg=102+10/92+6,maa=251+25/95+6,par=111+11,bom=246+24/114+6,lux=131+13/116+11,lhr=133+13/119+11,fra=122+12/120+11,ams=130+13/121+11,vie=125+12,iad=243+24/187+11,gru=330+33/331+11
RelayNetWorkStatus: avail=OK config=OK anyrelay=OK (Refreshing ping measurements)

[aiusepsi]

Hmm, on the assumption that the info in the "ping location" section is in the form A/B where A is the direct ping measurement and B is ping via the relay system, it seems like the basic problem is that for some reason the direct routes from you to the Valve datacentres in India are horrific.

For maa (Chennai) it says 251+25/95+6, which implies the direct route is 251 ms and the relayed route is 95 ms, which per the information earlier is 63 ms to Singapore, plus 32 ms over Valve's relay network back to Chennai.

It's picking the relayed route because it's somehow much better than the direct route! Not sure exactly how to diagnose this; you'd probably want to run a traceroute[en.wikipedia.org] to a Valve server in Chennai to see where the delay is being introduced. But I'm not sure exactly how you'd get the IP address of one of those servers.

[wo0dy .gFN-]

Thanks for explaining that, mate. However, my friends over here in India are not facing this issue. It just seems to be me who is having server routing trouble.

[aiusepsi]

Ah ha, I just remembered something, there is a way to lookup the IP addresses; the SteamDB guys helpfully track the network config[github.com] that Steam uses.

Try doing a traceroute to 155.133.232.98, which is the address of Valve's relay in Chennai. On a Windows machine, you'd press Windows Key + R, then enter "tracert 155.133.232.98" without the quote marks. Then copy & paste what you see.

For me it looks like:

Tracing route to 155.133.232.98 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  ttrouter [192.168.1.1]
  2    12 ms    12 ms    12 ms  ae50-ner002.loh.as13285.net [78.144.1.23]
  3    12 ms    12 ms    11 ms  ae50-scr102.loh.as13285.net [78.144.1.22]
  4    11 ms    11 ms    11 ms  host-78-144-14-160.as13285.net [78.144.14.160]
  5    12 ms    11 ms    11 ms  host-78-144-3-91.as13285.net [78.144.3.91]
  6    12 ms    12 ms    12 ms  xe-9-1-0.0.pjr04.ldn004.flagtel.com [85.95.27.197]
  7   152 ms   151 ms   151 ms  xe-0-0-1.0.pjr04.mmb004.flagtel.com [85.95.26.158]
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10   173 ms   173 ms   173 ms  220.227.125.117
 11     *        *        *     Request timed out.
 12   173 ms   173 ms   173 ms  155.133.232.98

Trace complete.

I'm in London, so yours will look very different. You can see though the big increase in latency at what looks like either end of a London to Mumbai (assuming mmb is short for Mumbai) link.

It's probably not happening to your friends because it's something very specific about the route from your computer to Valve's. The trace should hopefully show what.

[wo0dy .gFN-]

That looks helpful. Any thoughts on how to get the routing to get corrected though? :)

[aiusepsi]

Send your traceroute to Steam support and to your ISP's support, stating the problem. With any luck, it should reach someone who can figure out what's going wrong and solve the issue.

[wo0dy .gFN-]

Thanks mate.

[Iceira]

Do contact own ISP first. Valve cant fix local ISP and expansion in region you are in, that ISP and ISP they work with, then that is said. as you point out steam might to have have other tunnel to that new region, so spread out with diffrent tunnel, but this is normaly not that simple require region have super high ways, but sure go ahead ask steam support. it cant hurt to do that. ( normal this is part of steam own solutions so i doubt its that )

[MONU]

Is it fixed ? I also have the same problem using ACT fiber

[wo0dy .gFN-]

yep, it was fixed. You need to contact the ISP provider and explain the issue to them.

[Mr.Mamor]

Originally posted by Chod Commissioner:

Is it fixed ? I also have the same problem using ACT fiber

WAT&

[Yankiiii]

I used to have low ping on mumbai servers when directly routed but now it routes to mumbai via chennai server due to which i get 70 ping in mumbai server. I used the traceroute command on mumbai server and it shows 33 ping but in game it is still 70. Can someone help me?

[wo0dy .gFN-]

just contact your ISP provider and explain them the issue. They will sort it out.

[War_commander xd!!]

bro can anyone help me in cs2 i got packet loss in mumbai server around 5%- to 15% . in valve only i get losses and there is two mumbai servers as u know bom1 and bom2 so in in bom i get losses..please help me to fix it