AWS EC2 can not connect to Viettel ISP

Question

Hi AWS,

We're facing a problem that our EC2 instance can not be connected to our client server which is hosted at Viettel ISP.

I have used traceroute, netcat, telnet but all failed, connection timeout

```
traceroute api.wallet.airpay.vn
traceroute to api.wallet.airpay.vn (103.78.79.218), 30 hops max, 60 byte packets
 1  ec2-18-141-171-7.ap-southeast-1.compute.amazonaws.com (18.141.171.7)  1.793 ms  1.758 ms *
 2  100.65.39.240 (100.65.39.240)  5.404 ms 100.65.38.160 (100.65.38.160)  8.479 ms *
 3  * * 100.66.16.92 (100.66.16.92)  5.860 ms
 4  100.66.19.120 (100.66.19.120)  14.479 ms 100.66.19.156 (100.66.19.156)  7.453 ms 100.66.19.102 (100.66.19.102)  14.203 ms
 5  100.66.6.79 (100.66.6.79)  18.272 ms 100.66.7.29 (100.66.7.29)  12.916 ms 100.66.6.201 (100.66.6.201)  13.354 ms
 6  100.66.4.31 (100.66.4.31)  5.739 ms 100.66.4.19 (100.66.4.19)  13.984 ms 100.66.4.63 (100.66.4.63)  21.894 ms
 7  100.65.10.193 (100.65.10.193)  0.407 ms 100.65.10.129 (100.65.10.129)  0.416 ms 100.65.9.129 (100.65.9.129)  0.313 ms
 8  203.83.223.76 (203.83.223.76)  1.536 ms 203.83.223.18 (203.83.223.18)  1.217 ms 150.222.108.195 (150.222.108.195)  1.680 ms
 9  240.1.172.13 (240.1.172.13)  0.677 ms 240.1.172.14 (240.1.172.14)  0.619 ms  0.734 ms
10  242.4.85.129 (242.4.85.129)  1.432 ms 242.4.84.1 (242.4.84.1)  1.223 ms 242.4.84.5 (242.4.84.5)  1.231 ms
11  240.3.72.13 (240.3.72.13)  20.506 ms  20.553 ms  20.483 ms
12  242.8.20.3 (242.8.20.3)  20.516 ms 242.8.21.135 (242.8.21.135)  22.327 ms 242.8.21.131 (242.8.21.131)  20.524 ms
13  99.83.115.164 (99.83.115.164)  29.636 ms  29.665 ms 99.83.115.162 (99.83.115.162)  30.312 ms
14  99.83.115.163 (99.83.115.163)  30.478 ms 99.83.115.165 (99.83.115.165)  30.700 ms 99.83.115.163 (99.83.115.163)  30.325 ms
15  * * *
16  * * static.vnpt.vn (113.171.5.17)  63.066 ms
17  static.vnpt.vn (113.171.33.82)  56.675 ms  51.137 ms  52.064 ms
```

netcat -v api.wallet.airpay.vn 443
telnet api.wallet.airpay.vn 443

But when i tried the same command in our internal server. It's work

```
traceroute api.wallet.airpay.vn
traceroute to api.wallet.airpay.vn (103.78.79.218), 30 hops max, 60 byte packets
 1  10.0.70.1 (10.0.70.1)  1.033 ms  1.008 ms  0.999 ms
 2  169.254.103.137 (169.254.103.137)  0.993 ms  0.986 ms  0.980 ms
 3  42.96.40.2 (42.96.40.2)  2.233 ms  2.282 ms  2.318 ms
 4  static.cmcti.vn (183.91.12.194)  1.128 ms static.cmcti.vn (101.99.0.26)  1.142 ms  1.103 ms
 5  static.cmcti.vn (103.246.223.121)  3.998 ms  4.048 ms  3.995 ms
 6  103.1.208.14 (103.1.208.14)  3.416 ms 103.1.208.26 (103.1.208.26)  2.482 ms 103.1.208.30 (103.1.208.30)  2.753 ms
```

netcat -v api.wallet.airpay.vn 443
Connection to api.wallet.airpay.vn (103.78.79.218) 443 port [tcp/https] succeeded!

telnet api.wallet.airpay.vn 80
Trying 103.78.79.218...
Connected to api.wallet.airpay.vn

Please give me advise in this situation.
Thanks

**---------------------------------------------**

**----- UPDATED Oct 19, 2023 -------**

**---------------------------------------------**

I have tested by creating several  EC2 instance in other Regions

With **eu-west-2** , **es-east-1**, **ap-south-1** . i am able to successfully tracert, netcat, telnet

With **ap-northeast-2** , **ap-northeast-1** , **ap-southeast-1** , It's requests timeout

I used command below for checking
```
traceroute api.wallet.airpay.vn
netcat -v api.wallet.airpay.vn 443
telnet api.wallet.airpay.vn 80
```

**It seems like networking issue of AWS regions**

Please check the attached file

![ap-south-1](/media/postImages/original/IM7gUgLEpKSZ69dsstiFTpqg)
![eu-west-2](/media/postImages/original/IMR1Xxo90oTZ2H9iLE5Vb6lg)
![es-east-1](/media/postImages/original/IMAISmj6PdTFKIrjDZOXyCWA)
![ap-southeast-1](/media/postImages/original/IM1zB4hYfERDGTm87VIwH1cg)
![ap-northeast-1](/media/postImages/original/IMkQVIqbBtSvSbas9FBtuOzQ)
![ap-northeast-2](/media/postImages/original/IM3YfhxC_wTDStP9xEE2upMg)

Answer

**ap-northeast-1**
```
traceroute to api.wallet.airpay.vn (103.78.79.218), 30 hops max, 60 byte packets
 1  *
 2  240.3.112.1 (240.3.112.1)  0.241 ms
 3  242.8.187.145 (242.8.187.145)  3.470 ms
 4  240.1.172.13 (240.1.172.13)  68.839 ms
 5  242.4.85.135 (242.4.85.135)  67.951 ms
 6  240.3.72.13 (240.3.72.13)  94.379 ms
 7  242.8.21.5 (242.8.21.5)  87.597 ms
 8  99.83.115.164 (99.83.115.164)  81.773 ms
 9  static.vnpt.vn (113.171.45.37)  89.623 ms
10  *
11  static.vnpt.vn (113.171.33.82)  87.423 ms
12  static.vnpt.vn (113.164.3.150)  3182.598 ms
13  *
14  103.78.84.66 (103.78.84.66)  93.362 ms
15  103.78.79.218 (103.78.79.218)   91.795 ms
```
**ap-southeast-1**
```
traceroute to api.wallet.airpay.vn (103.78.79.218), 30 hops max, 60 byte packets
 1  *
 2  *
 3  *
 4  *
 5  241.0.13.10 (241.0.13.10)  0.266 ms
 6  242.7.245.135 (242.7.245.135)  21.079 ms
 7  240.3.72.13 (240.3.72.13)  27.613 ms
 8  242.8.20.135 (242.8.20.135)  28.451 ms
 9  99.83.115.164 (99.83.115.164)  20.088 ms
10  *
11  *
12  static.vnpt.vn (113.171.5.202)  41.294 ms
13  static.vnpt.vn (113.164.3.150)  4803.587 ms
14  *
15  103.78.79.218 (103.78.79.218)   37.353 ms
```
**ap-northeast-2**
```
traceroute to api.wallet.airpay.vn (103.78.79.218), 30 hops max, 60 byte packets
 1  *
 2  *
 3  *
 4  *
 5  *
 6  *
 7  100.65.9.1 (100.65.9.1)  0.832 ms
 8  52.93.247.3 (52.93.247.3)  1.420 ms
 9  54.239.123.6 (54.239.123.6)  2.471 ms
10  54.239.123.65 (54.239.123.65)  1.953 ms
11  100.91.151.149 (100.91.151.149)  17.272 ms
12  240.2.0.13 (240.2.0.13)  27.622 ms
13  242.5.68.131 (242.5.68.131)  28.972 ms
14  240.1.172.5 (240.1.172.5)  86.106 ms
15  242.4.84.1 (242.4.84.1)  88.551 ms
16  240.3.72.13 (240.3.72.13)  102.277 ms
17  242.8.21.7 (242.8.21.7)  101.145 ms
18  99.83.115.164 (99.83.115.164)  116.303 ms
19  *
20  static.vnpt.vn (113.171.50.10)  125.902 ms
21  static.vnpt.vn (113.171.33.82)  141.260 ms
22  static.vnpt.vn (113.164.3.150)  2410.173 ms
23  *
24  103.78.84.66 (103.78.84.66)  139.230 ms
25  103.78.79.218 (103.78.79.218)   133.779 ms
```

---

Are you still facing the issue ?

Answer

i am able to successfully tracert this target URI from an ec2 instance in EU regions. 
although i get the same response as you from Mumbai(AP-South-1)
ping does work although so network connectivity is there

further if i try just he airpay.vn I get redirected to shopeepay.vn - which i cannot traceroute to either

AWS EC2 can not connect to Viettel ISP

Relevant content