[help] Spectra Ping / Traceroute results to Singapore

varkey

Regulars
Jun 11, 2006
508
166
Now my IP address changed to 180.151.117.xxx. Even this is having 150+ ms pings to Linode / DO Singapore.

Announced as 180.151.117.0/24 (Shyam Spectra Pvt Ltd)
Announced as 180.151.112.0/21 (Shyam Spectra Pvt Ltd)
 

Anvith

Member
[OP]
Jan 19, 2019
42
14
Yeah most of the ip's gets you the same result.
I think the last time I had good ping was 180.156.x.x probably
 
  • Sad
Reactions: varkey

Anvith

Member
[OP]
Jan 19, 2019
42
14
They did also say that we can't optimized reverse path for non static ip's but getting a getting IP requires business connection as they deny to provide static IP to home users
 


Anvith

Member
[OP]
Jan 19, 2019
42
14
Even bsnl has proper latency that's what is shocking to me (cause usually bsnl was the worst offender)
Now i gotta either go for speed or latency
 

Anvith

Member
[OP]
Jan 19, 2019
42
14
@varkey just tried to mess with switching routers and renewing my ip address
got nated to
Code:
IP address                    10.201.116.2
Subnet mask                    255.255.255.0
Gateway IP address            10.201.116.1
with a public facing ip 180.151.118.xxx

here's the traceroute

Code:
                                                        My traceroute  [v0.86]
NAS (0.0.0.0)                                                                                                 Sun Mar 31 10:24:35 2019
Resolver: Received error response 2. (server failure)er of fields   quit
                                                                                              Packets               Pings
 Host                                                                                       Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. dlinkrouter.Dlink                                                                        0.0%     8    0.7   0.7   0.6   0.8   0.0
 2. 10.201.116.1                                                                             0.0%     8    1.3   1.8   1.2   5.0   1.1
 3. 203.92.63.177.reverse.spectranet.in                                                      0.0%     8    1.5   1.7   1.5   2.1   0.0
 4. 203.92.63.158.reverse.spectranet.in                                                      0.0%     8    8.6  13.1   8.5  34.1   9.0
 5. 180.151.59.30.reverse.spectranet.in                                                      0.0%     8    9.1   9.8   8.8  14.3   1.7
 6. 219.65.111.13.STATIC-Chennai.vsnl.net.in                                                 0.0%     8   26.5  27.8  26.1  35.5   3.1
 7. 172.31.167.45                                                                            0.0%     8   27.4  27.7  27.1  28.7   0.0
 8. ix-ae-2-1334.tcore2.svw-singapore.as6453.net                                             0.0%     7   61.8  62.1  61.5  63.0   0.0
 9. if-ae-2-2.tcore1.svw-singapore.as6453.net                                                0.0%     7   61.4  61.9  61.4  62.6   0.0
10. 180.87.67.42                                                                             0.0%     7   65.3  65.3  64.8  67.0   0.6
11. 139.162.0.14                                                                             0.0%     7   62.3  62.5  62.3  63.2   0.0
12. speedtest.singapore.linode.com                                                          14.3%     7   59.8  60.3  59.8  60.9   0.0
Code:
                                                        My traceroute  [v0.86]
NAS (0.0.0.0)                                                                                                 Sun Mar 31 10:25:09 2019
Keys:  Help   Display mode   Restart statistics   Order of fields   quit
                                                                                              Packets               Pings
 Host                                                                                       Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. dlinkrouter.Dlink                                                                        0.0%     5    0.8   0.7   0.7   0.8   0.0
 2. 10.201.116.1                                                                             0.0%     5    1.4   1.5   1.4   1.6   0.0
 3. 203.92.63.177.reverse.spectranet.in                                                      0.0%     5    1.6   1.8   1.5   2.1   0.0
 4. 203.92.63.158.reverse.spectranet.in                                                      0.0%     5    8.8   9.0   8.8   9.2   0.0
 5. 180.151.59.30.reverse.spectranet.in                                                      0.0%     5    9.2   9.4   9.0  10.2   0.0
 6. 219.65.111.13.STATIC-Chennai.vsnl.net.in                                                 0.0%     5   56.6  34.6  26.0  56.6  12.7
 7. 172.31.167.45                                                                            0.0%     5   27.8  27.7  27.3  28.1   0.0
 8. ix-ae-4-2.tcore1.cxr-chennai.as6453.net                                                  0.0%     5   30.0  30.6  29.9  32.8   1.0
 9. if-ae-13-2.tcore1.svw-singapore.as6453.net                                               0.0%     4   66.2  65.7  65.3  66.2   0.0
10. if-ae-11-2.thar1.svq-singapore.as6453.net                                                0.0%     4   64.9  65.5  64.9  66.4   0.0
11. 120.29.214.50                                                                            0.0%     4   62.4  64.2  62.4  69.5   3.5
12. 138.197.245.3                                                                            0.0%     4   65.6  66.1  65.2  66.7   0.6
13. ???
14. 159.89.192.182                                                                           0.0%     4   66.2  65.9  65.6  66.4   0.0



Also reverse trace to my ip from singapore server

Code:
                                         My traceroute  [v0.86]
localhost (0.0.0.0)                                                             Sun Mar 31 10:26:03 2019
Resolver: Received error response 2. (server failure)er of fields   quit
                                                                Packets               Pings
 Host                                                         Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. 103.3.60.2                                                 0.0%     3    0.7   2.8   0.7   6.8   3.4
 2. 139.162.0.5                                                0.0%     3    6.7   7.2   2.9  12.0   4.5
 3. ix-ae-19-0.tcore1.svw-singapore.as6453.net                 0.0%     3    4.0   3.5   1.2   5.4   2.0
 4. if-ae-2-2.tcore2.svw-singapore.as6453.net                  0.0%     3    5.0   3.9   1.0   5.6   2.3
 5. 180.87.15.202                                              0.0%     3   66.5  69.1  65.4  75.4   5.5
 6. 172.23.78.226                                              0.0%     3   71.3  68.7  67.4  71.3   2.1
 7. 115.113.165.50.static-mumbai.vsnl.net.in                   0.0%     3   70.4  71.5  68.4  75.6   3.7
 8. 203.92.38.49.reverse.spectranet.in                         0.0%     3   64.2  71.2  64.2  82.8  10.1
 9. 203.92.63.145.reverse.spectranet.in                        0.0%     3   61.6  63.6  61.6  65.4   1.9
10. 203.92.63.182.reverse.spectranet.in                        0.0%     3   64.2  62.9  62.0  64.2   1.0
now this reverse route is good enough though i would have expected it to be routed through chennai but mubai works too i guess
 

varkey

Regulars
Jun 11, 2006
508
166
Interesting, perhaps its just the way Spectra is announcing these routes? 🤔 Since its clear that some subnets get reverse routed bad, I guess it's something Spectra can fix if they want to. 🤷‍♂️
 


Anvith

Member
[OP]
Jan 19, 2019
42
14
They can but they won't on non static ip's for some reason. If you do remember last time it was 320ms plus ping Singapore servers. But they did say they can optimized it but later it somehow camedown to 165 as they changed the routing
 

Anurag Bhatia

Member
Jun 28, 2013
26
28
Rohtak
Hi

Forward trace: Spectra (India) > Linode (Singapore) seems fine. Return trace: Linode (Singapore) > Spectra (India) seems not optimised as routing via Europe.



anuragbhatia@linode01:~$ traceroute 180.151.124.1
traceroute to 180.151.124.1 (180.151.124.1), 30 hops max, 60 byte packets
1 103.3.60.2 (103.3.60.2) 0.491 ms 0.609 ms 0.824 ms
2 139.162.0.1 (139.162.0.1) 0.501 ms 139.162.0.5 (139.162.0.5) 0.407 ms 0.401 ms
3 139.162.0.18 (139.162.0.18) 0.371 ms 0.382 ms ix-ae-19-0.tcore1.svw-singapore.as6453.net (180.87.67.41) 0.828 ms
4 ix-ae-19-0.tcore1.svw-singapore.as6453.net (180.87.67.41) 0.820 ms if-ae-31-7.tcore1.wyn-marseille.as6453.net (80.231.217.94) 159.036 ms if-ae-26-2.tcore2.mlv-mumbai.as6453.net (180.87.39.158) 164.994 ms
5 if-ae-8-1600.tcore1.pye-paris.as6453.net (80.231.217.6) 149.427 ms if-ae-31-8.tcore1.wyn-marseille.as6453.net (80.231.217.88) 159.485 ms if-ae-26-2.tcore2.mlv-mumbai.as6453.net (180.87.39.158) 161.976 ms
6 80.231.154.118 (80.231.154.118) 355.105 ms if-ae-8-1600.tcore1.pye-paris.as6453.net (80.231.217.6) 149.123 ms if-ae-2-2.tcore1.mlv-mumbai.as6453.net (180.87.38.1) 169.201 ms
7 if-ae-5-2.tcore1.wyn-marseille.as6453.net (80.231.217.29) 155.038 ms 203.92.63.145.reverse.spectranet.in (203.92.63.145) 168.400 ms 167.388 ms
8 203.92.63.145.reverse.spectranet.in (203.92.63.145) 167.136 ms 203.92.63.182.reverse.spectranet.in (203.92.63.182) 156.795 ms 156.752 ms
9 203.92.63.62.reverse.spectranet.in (203.92.63.62) 182.975 ms 203.92.63.182.reverse.spectranet.in (203.92.63.182) 156.752 ms *
10 * * *
11 * * *
12 * * *


These issues happen when a network buys IP transit outside in one direction (Europe) only. Either of the following would have fixed the issue:

  1. Buy IP transit from the same provider in West as well as East (so in Singapore/HK etc).
  2. Just don't buy transit but simply peer at an IX and keep routes local so that their announcement in EU stays within EU and doesn't reach Asia. But for that, they need to have a cover prefix. So /24 goes via AS6453 from Europe and /23 is announced to transit in India (which maintains it's own connectivity to East and West).
I have written a mail to known contacts in Spectra (I worked there in past) and have requested them to announce a corresponding /22 to Indian transit provider and use a BGP community to for their existing /23 announcement to ensure that doesn't reach Linode (AS63949) and that way Linode will have a better return path towards you.

Let's see how it goes. Good luck!
 
Last edited:
  • Like
Reactions: Anvith and varkey

varkey

Regulars
Jun 11, 2006
508
166
Thank you @Anurag Bhatia 🙇‍♂️

A follow up question, how is it working better for some Spectra subnets? Are they using the method you described but only for that specific subnet? When the allocated IP address is from 180.151.118.x, the pings are better as @Anvith shared earlier -- [help] Spectra Ping / Traceroute results to Singapore | Spectra

Also, it doesn't appear to be just with Linode, looks like anything to/fro Singapore. Even speedtest-sgp1.digitalocean.com showed the same 160+ms pings.
 

Anurag Bhatia

Member
Jun 28, 2013
26
28
Rohtak
Hi

route-views>sh ip bgp 180.151.118.0/24 long
BGP table version is 101216436, local router ID is 128.223.51.103
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale, m multipath, b backup-path, f RT-Filter,
x best-external, a additional-path, c RIB-compressed,
Origin codes: i - IGP, e - EGP, ? - incomplete
RPKI validation codes: V valid, I invalid, N Not found

Network Next Hop Metric LocPrf Weight Path
* 180.151.118.0/24 193.0.0.56 0 3333 1273 55410 10029 i
* 202.93.8.242 0 24441 3491 3491 55410 10029 i
* 37.139.139.0 0 57866 6453 4755 10029 i
* 140.192.8.16 0 54728 20130 6939 3491 55410 10029 i
* 91.218.184.60 0 0 49788 174 6453 4755 10029 i
* 203.181.248.168 0 7660 2516 6453 4755 10029 i
* 134.222.87.1 700 0 286 6453 4755 10029 i
* 154.11.12.212 0 0 852 3491 55410 10029 i
* 103.197.104.1 0 134708 9902 3491 55410 10029 i
* 209.124.176.223 0 101 101 11164 3491 55410 10029 i
* 137.39.3.55 0 701 1273 55410 10029 i
* 94.142.247.3 0 0 8283 3491 55410 10029 i
* 208.51.134.254 0 0 3549 3356 6453 4755 10029 i
* 162.251.163.2 0 53767 3257 6453 4755 10029 i
* 212.66.96.126 0 20912 174 3491 55410 10029 i
* 198.58.198.255 0 1403 6453 4755 10029 i
* 198.58.198.254 0 1403 6453 4755 10029 i
* 202.232.0.2 0 2497 3491 55410 10029 i
* 203.62.252.83 0 1221 4637 1273 55410 10029 i
* 195.208.112.161 0 3277 39710 9002 3491 55410 10029 i
* 64.71.137.241 0 6939 3491 55410 10029 i
* 194.85.40.15 0 0 3267 1299 1273 55410 10029 i
* 132.198.255.253 0 1351 6939 1273 55410 10029 i
* 206.24.210.80 0 3561 209 6453 4755 10029 i
* 207.172.6.20 82 0 6079 3491 55410 10029 i
* 207.172.6.1 0 0 6079 3491 55410 10029 i
* 208.74.64.40 0 19214 3257 6453 4755 10029 i
* 162.250.137.254 0 4901 6079 3491 55410 10029 i
* 217.192.89.50 0 3303 1273 55410 10029 i
* 114.31.199.1 0 4826 3491 55410 10029 i
* 173.205.57.234 0 53364 3257 3491 55410 10029 i
* 144.228.241.130 80 0 1239 6453 4755 10029 i
*> 12.0.1.63 0 7018 6453 4755 10029 i
route-views>
180.151.118.0/24 is announced to their domestic IP transit provider (AS55410 - Vodafone and AS4755 - Tata Comm). Both Vodafone and Tata have PoPs in Singapore and Europe and maintain routing accordingly. They would simply announce route at both locations and hence networks in Singapore will pick their Singapore announcement, networks in Europe will pick Europe announcement.

That way you don't have a case where it's just being announced in Europe and everyone in World has to send traffic via EU for that pool.
 
  • Wow
Reactions: varkey and Anvith