Airtel fiber and its pathetic routing to ME

[raghav_xd]

@raghav_xd unless you give us the proper hostname and domain OR the IP address we cant check from our end and neither will Airtel be able to resolve your issue unless you know these details. No details = no resolution. So, tell me, how did yuou get that '120 ms' ping value you referred to??

when we play a game there is option to enable latency, its always on the screen but ip is hidden .

 

[Chip]

Alright bro, then I am afraid you're not going to this resolved. Airtel staff will ask you for hostname and site. In the meantime you can try using a VPN..

See here The Bahrain servers in the middle east have become so laggy

 

[raghav_xd]

Call of Duty uses AWS for Bahrain, Airtel has a direct peering tunnel from Mumbai to AWS, so the high latency issue is with AWS's internal network and not Airtel itself.
Fornite uses anycast addresses ie, AWS Mumbai, so that should not be an issue.

i cross checked with jio fiber at my workplace and am getting 50/60ms , checked with local isp of my friend and same 50/60ms. only airtel fiber has 125/130ms latency.

even airtel 4g wireless is giving 80ms ping, but i get 5% packet loss with that.

the problem is exclusively on airtel fiber only, and not just on few ip adresses ..you connect to any game which has middle east servers and you end up with same ping as europe which is not normal.

 

[mikrotik]

We are not here for your tech support. You are being extremely unreasonable with your requests. If you cannot share IP or hostname, we cannot help you narrow down your issue and nor can Airtel. They will just ignore you like we will.

 

[raghav_xd]

the host is AWS Bahrain
game name is call of duty warzone.
latency is 130ms. (supposed to be 70 max).

already contacted nodal email .
use of third party apps like vpns can lead to permanent ban on my account, is there any other workaround? to force my route through maharashtra?

 

[Chip]

@raghav_xd "AWS Bahrain" is the PAAS/IAAS hosting service plus country and certainly not host + domain name or IP address.

Unless you have these details we, or for that matter the service provider, cannot help you. You just have to live with it.

 

[JB701]

15.184.0.253

15.185.32.254

157.175.10.11

these appear to be Bahrain ips from here EC2 Reachability Test

Excitel:

 Host                                                                        Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. xxxxxxxxx  xxx                                                           0.0%     7    1.5   1.6   1.0   2.2   0.4
 2. 103.212.157.1                                                            57.1%     7   50.7  19.8   3.8  50.7  26.8
 3. (waiting for reply)
 4. 99.83.70.236                                                              0.0%     7    4.9   6.6   3.2  22.8   7.2
 5. 52.93.98.124                                                              0.0%     7    4.2   4.6   4.0   5.6   0.6
 6. 52.93.116.79                                                              0.0%     7    4.0   5.9   3.4  16.6   4.7
 7. (waiting for reply)
 8. 52.93.225.238                                                             0.0%     7   56.8  57.4  56.0  62.0   2.1
 9. 52.93.225.255                                                             0.0%     7   57.4  57.0  56.2  57.7   0.6
10. 52.93.226.100                                                             0.0%     6   57.3  57.7  56.6  59.6   1.1
11. 52.93.226.93                                                              0.0%     6   59.5  58.9  58.3  59.9   0.6
12. 52.93.227.82                                                              0.0%     6   59.2  58.7  57.6  60.5   1.1
13. (waiting for reply)
14. (waiting for reply)
15. (waiting for reply)
16. ec2-15-184-0-253.me-south-1.compute.amazonaws.com                         0.0%     6   56.3  56.7  56.0  57.9   0.6

Airtel:

 Host                                                                        Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. abts-north-static-x.airtelbroadband.in                      0.0%     4    2.4   2.5   2.4   2.7   0.1
 2. 125.17.145.29                                                             0.0%     4    2.6   2.7   2.5   3.1   0.3
 3. 182.79.154.77                                                             0.0%     4    3.9   6.7   3.6  11.1   3.6
 4. 99.83.64.168                                                              0.0%     4    8.6   6.6   5.5   8.6   1.4
 5. 150.222.217.100                                                           0.0%     4    5.0   5.1   4.7   5.5   0.4
 6. 150.222.217.109                                                           0.0%     4    5.1   5.7   5.0   7.0   0.9
 7. (waiting for reply)
 8. 52.93.226.84                                                              0.0%     4  125.5 126.8 124.8 130.1   2.9
 9. 52.93.226.95                                                              0.0%     3  127.3 131.3 123.8 142.7  10.1
10. 52.93.225.248                                                             0.0%     3  126.3 126.3 126.1 126.5   0.2
11. 52.93.225.247                                                             0.0%     3  126.1 126.8 125.1 129.3   2.2
12. 52.93.227.86                                                              0.0%     3  126.2 125.7 125.3 126.2   0.5
13. (waiting for reply)
14. (waiting for reply)
15. (waiting for reply)
16. ec2-15-184-0-253.me-south-1.compute.amazonaws.com                         0.0%     3  124.0 124.4 124.0 125.0   0.5

 

[Lolita_Magnum]

And according to this, it's pretty clear the issue is on AWS's side.

3 5 ms 5 ms 5 ms nsg-corporate-5.210.186.122.airtel.in [122.186.210.5]
4 8 ms 6 ms 7 ms 116.119.73.28
5 5 ms 5 ms 5 ms 99.82.179.110
6 6 ms 6 ms 5 ms 52.95.64.107
7 * * * Request timed out.
8 7 ms 7 ms 6 ms 52.95.65.37
9 6 ms 6 ms 5 ms 52.95.66.209
10 * * * Request timed out.
11 104 ms 104 ms 103 ms 52.93.225.236
12 103 ms 102 ms 103 ms 52.93.225.253
13 104 ms 103 ms 103 ms 52.93.225.218
14 103 ms 103 ms 102 ms 52.93.225.213
15 104 ms 103 ms 107 ms 52.93.227.80
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 102 ms 102 ms 102 ms ec2-15-184-0-253.me-south-1.compute.amazonaws.com [15.184.0.253]

Alternatively, you can also use some kind of network monitor like Glasswire or Windows Resource Monitor itself to track IPs.

 

[Chip]

Ping tests to those 3 IPs from here vary between 135-141 ms each

 

[itachi]

Yes, you will need to die in-game for 7 months, regardless there are no cable breakages as latencies for me are just perfect.

Unfortunately, we need that 1ms advantage to win any game nowadays especially since everyone has super fast connection and everyone has an aimbot.

The game is to beat the aimboters. It is impossible but that is the game.