High ping to Europe

  • Thread starter Thread starter Meowmath
  • Start date Start date
  • Replies Replies 151
  • Views Views 31,010
Pings are still high for me.
 
Basically, it seems that Airtel is giving more priority to its mobile network over broadband. I have tested on the same London server on both Broadband and Mobile data. Surprisingly mobile data gives better latency over broadband.
2Xt1ULL.jpg
lvhcPCq.jpg
 
Hello folks

I see it is fixed for multiple IPs I was tracking. I see a direct route now as well as drop-in latency. For anyone still getting high latency on Airtel with EU servers, can you please share your WAN IP (or just the first three blocks of it) so I can do a return trace to verify?

A couple of traces that clearly show a direct path now to this specific destination in India:

ionos01.ring.nlnog.net | CHANGED | rc=0 >>
traceroute to 182.74.20.9 (182.74.20.9), 30 hops max, 60 byte packets
1 ip217-160-211-253.pbiaas.com (217.160.211.253) 0.407 ms 0.403 ms 0.403 ms
2 ae-16-101.bb-a.fra3.fra.de.net.ionos.com (212.227.120.174) 0.458 ms 0.459 ms 0.456 ms
3 dx1.in.airtel.com (80.81.194.250) 36.300 ms 36.297 ms 36.279 ms
4 116.119.44.230 (116.119.44.230) 181.307 ms 181.327 ms 181.328 ms
5 116.119.72.113 (116.119.72.113) 182.042 ms 182.079 ms 182.021 ms
6 182.74.20.9 (182.74.20.9) 189.710 ms 191.059 ms 191.043 ms
plutex01.ring.nlnog.net | CHANGED | rc=0 >>
traceroute to 182.74.20.9 (182.74.20.9), 30 hops max, 60 byte packets
1 91-202-41-254.static.plutex.de (91.202.41.254) 0.245 ms 0.247 ms 0.243 ms
2 lwlcom.dc01.plutex.net (91.202.40.226) 0.229 ms * *
3 * * *
4 * ae0-70.cr10.bre06.lwlcom.net (185.146.230.31) 8.284 ms 8.327 ms
5 ae3-100.cr10.dus01.lwlcom.net (185.146.230.107) 5.550 ms 5.572 ms 5.569 ms
6 ae5-60.cr10.ams01.lwlcom.net (185.146.230.131) 7.991 ms 8.338 ms 8.353 ms
7 speed-ix.netix.net (185.1.95.161) 8.329 ms 8.338 ms 8.289 ms
8 185.1.226.123 (185.1.226.123) 28.309 ms 28.161 ms 28.123 ms
9 116.119.44.230 (116.119.44.230) 195.387 ms 198.731 ms 198.550 ms
10 116.119.72.113 (116.119.72.113) 195.866 ms 196.103 ms 196.066 ms
11 182.74.20.9 (182.74.20.9) 197.129 ms 197.046 ms 197.092 ms
hostwayde01.ring.nlnog.net | CHANGED | rc=0 >>
traceroute to 182.74.20.9 (182.74.20.9), 30 hops max, 60 byte packets
1 83.246.46.1 (83.246.46.1) 0.487 ms 0.686 ms 0.929 ms
2 cr01.h.as24679.net (195.47.229.254) 0.401 ms 0.421 ms 0.422 ms
3 dx1.in.airtel.com (80.81.194.250) 36.255 ms 36.224 ms 36.243 ms
4 116.119.44.230 (116.119.44.230) 202.234 ms 202.271 ms *
5 116.119.72.113 (116.119.72.113) 194.503 ms 194.601 ms 194.724 ms
6 182.74.20.9 (182.74.20.9) 197.265 ms 198.226 ms 198.271 ms
iabg01.ring.nlnog.net | CHANGED | rc=0 >>
traceroute to 182.74.20.9 (182.74.20.9), 30 hops max, 60 byte packets
1 host-83-170-60-34.customer.teleport-iabg.de (83.170.60.34) 0.637 ms 0.631 ms 0.729 ms
2 core1-gi-0-0-0.as29259.net (83.170.0.38) 0.285 ms 0.293 ms 0.292 ms
3 host-212-18-22-97.customer.m-online.net (212.18.22.97) 1.154 ms 1.156 ms 1.155 ms
4 ae7.rt-decix-2.m-online.net (212.18.6.179) 6.775 ms 6.782 ms 6.782 ms
5 dx1.in.airtel.com (80.81.194.250) 22.606 ms 22.601 ms 22.588 ms
6 116.119.44.230 (116.119.44.230) 187.405 ms 187.312 ms 187.298 ms
7 116.119.72.113 (116.119.72.113) 187.975 ms 188.000 ms 188.036 ms
8 182.74.20.9 (182.74.20.9) 191.017 ms 191.071 ms 191.238 ms
 
I've a static ip connection, it starts with 122.16X.XX.X. This reverse lookup is through vultr london. It seems like they are routing through Los angeles, earlier my ping were ~140 to most of the EU servers now they are above 240.

Code:
HOST: vm1359261.vultr.com                                  Loss%   Snt   Last   Avg  Best  Wrst StDev
1.|-- ???                                                  100.0    10    0.0   0.0   0.0   0.0   0.0
2.|-- vl101-ds1-u1-r52b7.lon3.constant.com                  0.0%    10    0.5   0.4   0.3   0.5   0.1
3.|-- ???                                                  100.0    10    0.0   0.0   0.0   0.0   0.0
4.|-- ???                                                  100.0    10    0.0   0.0   0.0   0.0   0.0
5.|-- ldn-b9-link.ip.twelve99.net                           0.0%    10    2.7   1.2   0.3   3.2   1.2
6.|-- ldn-bb4-link.ip.twelve99.net                          0.0%    10    0.7   1.1   0.6   3.4   0.8
7.|-- nyk-bb1-link.ip.twelve99.net                          0.0%    10   70.0  70.0  69.9  70.1   0.1
8.|-- rest-bb1-link.ip.twelve99.net                         0.0%    10  132.6 132.7 132.5 133.0   0.2
9.|-- las-b22-link.ip.twelve99.net                         80.0%    10  134.5 134.6 134.5 134.6   0.0
10.|-- bhartiairtel-svc069282-ic354140.ip.twelve99-cust.net  0.0%    10  132.5 132.5 132.3 133.4   0.3
11.|-- 116.119.57.98                                         0.0%    10  236.6 236.7 236.5 236.9   0.1
12.|-- 125.18.117.222                                        0.0%    10  239.1 240.8 239.1 255.3   5.1
13.|-- abts-kk-static-179.84.166.122.airtelbroadband.in      0.0%    10  241.3 241.3 241.0 241.6   0.2
 
Hi, I need three blocks at least to look for the most specific /24 equivalent route if present. Airtel has huge address range & different pools can be routed differently.

122.16X.XX.X. is quite a bit of masking. Share x.x.x.y (you can mask the y part).

But yes from your trace it seems like the issue is still there on that pool. Can cross-check announcements to networks other than Telia to validate it once you share more specific IPs.
 
Ok so that IP is part of 122.166.84.0/24 and their upstream are still learning that in US. I just checked one of their upstream (Telia AS1299) and they still have the BGP tag 1299:2009(Do NOT announce to ANY peer in Europe). So this confirms the routing is intentional and issue is still there.



Earlier everyone was impacted but now:

  1. Their downstream customer IPs are fixed. I am personally on a small downstream ISP of Airtel. Their routing has fixed. My WAN IP is from 202.9.120.0/24 and that along with many other downstream is being announced to Telia in Europe.
  2. Airtel backbone AS9498 own IPs routing seems direct.
  3. Airtel Telemedia (the DSL + FTTH part of it - AS24560) - it's routing still seems to be from US.
Just updated the thread I am maintaining for this issue: EU -> Airtel high latency
 
Code:
 1  192.168.60.1  1.366 ms  0.665 ms  0.778 ms
 2  122.161.47.255  43.788 ms  36.732 ms  27.310 ms
 3  125.21.160.21  17.571 ms
    125.18.73.17  15.501 ms  14.468 ms
 4  182.79.222.81  135.859 ms  137.211 ms  135.777 ms
 5  62.115.42.118  268.740 ms  266.486 ms  267.332 ms
 6  62.115.124.58  289.606 ms  290.326 ms  288.290 ms
 7  62.115.113.147  281.052 ms  281.408 ms  280.340 ms
 8  62.115.33.119  281.056 ms
    62.115.171.181  293.789 ms
    62.115.33.119  279.901 ms
 9  * * *
10  * * *
11  * * *
 
Hey anurag I have been closely following all the info you have been posting Twitter, all the information you have been providing about this issue has been helpful since Airtel hasn't said a word about what's going on. Thank you
 

Top