Excitel: High Ping to Singapore Servers?

[JB701]

Tracing route to 40.65.169.147 over a maximum of 30 hops

1 1 ms 2 ms 1 ms 192.168.5.1
2 1 ms <1 ms 1 ms 10.89.139.1
3 2 ms 1 ms 1 ms 103.248.93.1
4 3 ms 2 ms 3 ms 163.53.87.1
5 5 ms 4 ms 4 ms aninetwork.del01-96cbe-1a.ntwk.msn.net [207.46.219.130]
6 34 ms 34 ms 33 ms ae29-0.ear01.bom02.ntwk.msn.net [104.44.234.158]
7 87 ms 87 ms 86 ms be-20-0.ibr01.bom02.ntwk.msn.net [104.44.23.213]
8 85 ms 86 ms 85 ms be-5-0.ibr01.maa02.ntwk.msn.net [104.44.18.238]
9 86 ms 86 ms 86 ms be-1-0.ibr01.maa30.ntwk.msn.net [104.44.18.137]
10 86 ms 87 ms 86 ms be-9-0.ibr01.sg3.ntwk.msn.net [104.44.18.201]
11 85 ms 85 ms 84 ms ae103-0.icr02.sg2.ntwk.msn.net [104.44.20.0]
12 * * * Request timed out.
13 ^C

Seems like Azure is peered with ANI-IX

 

[Deleted member 63558]

Well, for me I don't see any sort of transit. All my Excitel Traffic is going through Excitel to Microsoft directly.

There is no transit. Neither Tata, Extreme IX or Airtel.

I'm back to Excitel as the reason for Excitel users having this issue.

Screenshot:

103.56.231.1 and ....66 are Excitel's IPs.

The next hop in the line is Microsoft Azure Directly.

--------------------

Here is the Airtel Broadband Tracert for the IP.

Not being Biased but Airtel seems to have better routing as it's going through all the loops, first it goes through del pop of microsoft azure, then mumbai and then it's going to singapore which I believe why there is very less room of spike in ping whenever I am on Airtel.

If everything is normal and no ping issue. I see huge ping spikes (both lower and higher) in the case of Excitel. Maybe that's something to note that Excitel is sending all the data by skipping a lot of hops in between? Which is def. bad for FPS games as the game's engine and networking module sometimes can't priorities our hit reg over the other person because our ping is fluctuation a lot.

Siege has a learning mechanics so if you have been playing for a long-time on a same ping or similar range ping, and as soon as you have a ping which is very lower and higher then your avg. ping in past, they would throw a ping error with packet loss error as a possibility of not counting our hit reg. Siege which is far dependent upon the headshot compared to CS, It's very important that ping spike should be least or within the room of ~10ms only.

So what happens with Excitel sometimes is that 60-70ms is average (if everything is normal) but suddenly it goes as high as 110-160ms (since I got the connection). So maybe that's something related to wrong routing too?

Any how, I will keep an eye. But, Excitel is not dependent upon any transit seeing the tracert I believe. (Which I don't know if it's good or bad)

 

[itzmynet]

Overloaded Microsoft Azure servers @ Chennai

 

[Deleted member 63558]

@itzmynet Didn't get you?

I checked the Microsoft Azure Status Page, the most recent they have is July 2019. No mention of September.

Checked for both India and South East Asia (Singapore)

 

[itzmynet]

i am assuming because the spike in ping is always on the second hop after reaching Chennai (maa) Azure server. or probably the azure peering between Chennai & Singapore is congested

 

[Lousyaim]

Well, for me I don't see any sort of transit. All my Excitel Traffic is going through Excitel to Microsoft directly.

There is no transit. Neither Tata, Extreme IX or Airtel.

I'm back to Excitel as the reason for Excitel users having this issue.

Screenshot:

103.56.231.1 and ....66 are Excitel's IPs.

The next hop in the line is Microsoft Azure Directly.

--------------------

Here is the Airtel Broadband Tracert for the IP.

Not being Biased but Airtel seems to have better routing as it's going through all the loops, first it goes through del pop of microsoft azure, then mumbai and then it's going to singapore which I believe why there is very less room of spike in ping whenever I am on Airtel.

If everything is normal and no ping issue. I see huge ping spikes (both lower and higher) in the case of Excitel. Maybe that's something to note that Excitel is sending all the data by skipping a lot of hops in between? Which is def. bad for FPS games as the game's engine and networking module sometimes can't priorities our hit reg over the other person because our ping is fluctuation a lot.

Siege has a learning mechanics so if you have been playing for a long-time on a same ping or similar range ping, and as soon as you have a ping which is very lower and higher then your avg. ping in past, they would throw a ping error with packet loss error as a possibility of not counting our hit reg. Siege which is far dependent upon the headshot compared to CS, It's very important that ping spike should be least or within the room of ~10ms only.

So what happens with Excitel sometimes is that 60-70ms is average (if everything is normal) but suddenly it goes as high as 110-160ms (since I got the connection). So maybe that's something related to wrong routing too?

Any how, I will keep an eye. But, Excitel is not dependent upon any transit seeing the tracert I believe. (Which I don't know if it's good or bad)

@ajgamer My trace route doesn't show any transit IPs either, it goes directly to azure servers after my ISPs IP same like you. But there is some underlying transit route which we don't know(because local ISPs can't route beyond the state or city they are operating at). After that they use lines of the big ones to route data. So there is some issues in the routing from India to Singapore azure servers.

 

[Lousyaim]

i am assuming because the spike in ping is always on the second hop after reaching Chennai (maa) Azure server. or probably the azure peering between Chennai & Singapore is congested

This makes sense because I am not on excitel yet I am having the exact same issue as the excitel users. This is definitely some India wide issue.

 

[Deleted member 63558]

@ajgamer My trace route doesn't show any transit IPs either, it goes directly to azure servers after my ISPs IP same like you. But there is some underlying transit route which we don't know(because local ISPs can't route beyond the state or city they are operating at). After that they use lines of the big ones to route data. So there is some issues in the routing from India to Singapore azure servers.

It's quite possible that Excitel might have upgraded their licensing. Secondly, all the traffic are routing through Chennai/Bombay first (in every ISP). So Excitel don't need Airtel/Tata's backbone to handle it if they have upgraded their licensing.

Given that Excitel is growing in multiple cities, it's quite possible they did it.

So, it's basically, Excitel Delhi -> Microsoft Chennai -> Microsoft Singapore. (It's not Excitel Delhi -> Microsoft Singapore)

@JB700 is it possible?

 

[Deleted member 63558]

i am assuming because the spike in ping is always on the second hop after reaching Chennai (maa) Azure server. or probably the azure peering between Chennai & Singapore is congested

This can be the possibility as well. Can't deny but again, for many people this issue is constant and for some it's like on-and-off.

 

[Lousyaim]

It's quite possible that Excitel might have upgraded their licensing. Secondly, all the traffic are routing through Chennai/Bombay first (in every ISP). So Excitel don't need Airtel/Tata's backbone to handle it if they have upgraded their licensing.

Given that Excitel is growing in multiple cities, it's quite possible they did it.

So, it's basically, Excitel Delhi -> Microsoft Chennai -> Microsoft Singapore. (It's not Excitel Delhi -> Microsoft Singapore)

@JB700 is it possible?

That's definitely not the case here since I don't use excitel and I don't even live anywhere close to where excitel operates. This issue is there in a common point where both your and my isp is routing the data through to Singapore Microsoft azure probably in a node in Chennai or mumbai. It can be a node of Microsoft's Indian azure server itself where the ping spikes start. We don't know but it's definitely not excitel only.