Railwire ping issues on 3rd party DNS from Kerala

[jithinjacob]

Hi,

Is there anyone else have facing this issue?
When I change the DNS to Cloudflare or Google, the pings are really high to google services and also to gaming servers sometimes starts from 30 then finally goes upto 100 or more.
I have traced this issue and could see that the route is made through Mumbai servers instead going to Chennai which causing these problems.
Also I have mentioned these problems on the tickets and surprisingly non of them responded so far.

Please tell me if someone knows something about this situation.

 

[Sayan97]

They have been doing that for a while. Complained multiple times Even yesterday ping to SGP servers were above 93 all day. Their support doesn't gives a fuck it's ran by brainless retards who don't care if your latency is bad and blame that on LCO Everytime whereas my LCO showed in his network rack room that's railwire issue. Iam going to switch to airtel in next 7 days

FYI their international gateway in Chennai is ran by airtel which is overloaded

 

[jithinjacob]

Hi,

Thanks man, appreciate your reply.
I have tried the default railtel dns which is fine but the issue is on the third party dns.
I have not tested the pings in games with default dns..
As you said the Chennai server is overloaded that could be the reason for reroute to Mumbai.
Hopefully they will increase the gateway capacity or resource in Chennai..

 

[Sayan97]

They won't be upgrading their servers soon. I could not even maintain a steady connection to my OVH VPS in singapore..the terminal lags while typing due to the latency just forget playing games

 

[jithinjacob]

└──╼ $ping google.com
PING google.com (172.217.167.174) 56(84) bytes of data.
64 bytes from bom12s01-in-f14.1e100.net (172.217.167.174): icmp_seq=1 ttl=113 time=40.5 ms
64 bytes from bom12s01-in-f14.1e100.net (172.217.167.174): icmp_seq=2 ttl=113 time=41.0 ms
64 bytes from bom12s01-in-f14.1e100.net (172.217.167.174): icmp_seq=3 ttl=113 time=40.7 ms
64 bytes from bom12s01-in-f14.1e100.net (172.217.167.174): icmp_seq=4 ttl=113 time=40.4 ms
64 bytes from bom12s01-in-f14.1e100.net (172.217.167.174): icmp_seq=5 ttl=113 time=40.8 ms
--- google.com ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 6009ms
rtt min/avg/max/mdev = 40.175/40.736/41.327/0.448 ms

└──╼ $ping google.com
PING google.com (172.217.163.174) 56(84) bytes of data.
64 bytes from maa05s05-in-f14.1e100.net (172.217.163.174): icmp_seq=1 ttl=116 time=14.1 ms
64 bytes from maa05s05-in-f14.1e100.net (172.217.163.174): icmp_seq=2 ttl=116 time=15.8 ms
64 bytes from maa05s05-in-f14.1e100.net (172.217.163.174): icmp_seq=3 ttl=116 time=15.8 ms
64 bytes from maa05s05-in-f14.1e100.net (172.217.163.174): icmp_seq=4 ttl=116 time=15.4 ms
64 bytes from maa05s05-in-f14.1e100.net (172.217.163.174): icmp_seq=5 ttl=116 time=15.1 ms

This what Im facing now, the adjacent 2 ping test shows me 2 results thats been from Mumbai and second is Chennai.
I use google DNS now.

Something is really weird.