So i did all those thing i even made 100% sure that the every port was open but i did do as followed from the one person who commented and trace routed the ISP he entered and these are the results. As we can see here the issue is coming from the NTT network.


Tracing route to 204.2.229.97 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 192.168.0.1
2 28 ms 17 ms 13 ms 142.254.153.249
3 22 ms 29 ms 20 ms gig4-2.instoh1-rtr1.insight.rr.com [65.24.192.205]
4 31 ms 22 ms 32 ms agg9.wachoh0402h.midwest.rr.com [65.189.106.146]
5 23 ms 24 ms 29 ms tge1-2-0-16.clmcohib01r.midwest.rr.com [24.33.161.80]
6 55 ms 29 ms 31 ms be27.clevohek01r.midwest.rr.com [65.29.1.38]
7 72 ms 38 ms 67 ms bu-ether17.vinnva0510w-bcr00.tbone.rr.com [66.109.6.70]
8 40 ms 40 ms 46 ms bu-ether11.asbnva1611w-bcr00.tbone.rr.com [66.109.6.30]
9 36 ms 39 ms 36 ms 0.ae2.pr1.dca10.tbone.rr.com [107.14.17.204]
10 36 ms 37 ms 36 ms ix-ae-17-0.tcore2.aeq-ashburn.as6453.net [216.6.87.149]
11 37 ms 36 ms 37 ms if-ae-2-2.tcore1.aeq-ashburn.as6453.net [216.6.87.2]
12 37 ms 36 ms 40 ms 66.198.154.71
13 41 ms 37 ms 36 ms ae-8.r23.asbnva02.us.bb.gin.ntt.net [129.250.2.23]
14 100 ms 103 ms 106 ms ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
15 104 ms 117 ms 104 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
16 108 ms 104 ms 104 ms ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
17 105 ms 106 ms 105 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
18 * 105 ms 106 ms 204.2.229.234
19 115 ms 106 ms 106 ms 204.2.229.97

Trace complete.