reverse trace to 180.151.203.x
reverse trace to 180.151.117.0
Yup seems to be fixed atleast the reverse route. I think the traceroute was fine so this should all around fix this.
Also this goes through mumbai unlike 224 subnet which had 42 ms ping so this will add about 20-40 ms more latency but still so much better now its very much usable
Code:
My traceroute [v0.86]
localhost (0.0.0.0) Mon Apr 29 20:27:51 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.3 0.0% 7 11.6 5.1 0.7 14.4 5.6
2. 139.162.0.13 0.0% 7 11.9 8.2 0.7 13.8 5.0
3. ix-ae-19-0.tcore1.svw-singapore. 0.0% 7 3.8 8.7 1.5 13.6 4.7
4. if-ae-2-2.tcore2.svw-singapore.a 0.0% 7 3.0 5.4 1.9 16.2 4.9
5. 180.87.15.202 0.0% 7 74.6 74.0 71.2 77.1 1.7
6. 172.23.78.226 0.0% 7 67.6 74.7 67.6 91.2 8.4
7. 115.113.165.50.static-mumbai.vsn 0.0% 6 78.4 77.3 74.1 80.2 2.9
8. 203.92.38.49.reverse.spectranet. 0.0% 6 76.5 76.9 74.3 82.9 3.4
9. 203.92.63.62.reverse.spectranet. 0.0% 6 71.6 71.8 66.2 79.6 5.1
10. 203.92.63.182.reverse.spectranet 0.0% 6 69.7 75.5 66.9 86.0 7.7
11. ???
12. 180.151.203.x.reverse.spectran 0.0% 6 80.6 70.9 66.9 80.6 4.9
reverse trace to 180.151.117.0
Code:
My traceroute [v0.86]
localhost (0.0.0.0) Mon Apr 29 20:29:52 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.3 0.0% 5 3.5 4.7 1.2 8.9 2.9
2. 139.162.0.13 0.0% 5 7.1 7.1 2.1 11.5 3.8
3. ix-ae-19-0.tcore1.svw-singapore. 0.0% 5 2.2 12.0 2.2 36.3 14.0
4. if-ae-2-2.tcore2.svw-singapore.a 0.0% 5 4.8 4.4 0.9 7.8 3.4
5. 180.87.15.202 0.0% 5 79.4 70.7 66.7 79.4 5.2
6. 172.23.78.226 0.0% 5 68.1 70.4 66.9 76.1 3.5
7. 115.113.165.50.static-mumbai.vsn 0.0% 5 72.5 73.8 70.6 80.1 3.6
8. 203.92.38.49.reverse.spectranet. 0.0% 5 73.6 75.5 72.6 78.4 2.3
9. 203.92.63.145.reverse.spectranet 0.0% 5 62.3 66.9 62.3 76.2 5.4
10. 203.92.63.182.reverse.spectranet 0.0% 5 64.6 65.7 61.5 71.0 4.5
11. ???
Yup seems to be fixed atleast the reverse route. I think the traceroute was fine so this should all around fix this.
Also this goes through mumbai unlike 224 subnet which had 42 ms ping so this will add about 20-40 ms more latency but still so much better now its very much usable