Thanks man. Direct TW user so was wondering how it looked like for PTCL guys because I had a feeling it would look good. Currently this IP address is irrelevant and useless, but I'm assuming AWS will be using this ISP in Bahrain for their servers. Think it's operational in March.Huh. When I tried it last night on my PTCL connection, I got this (ignore the fluctuations - see the lowest reading. I took this from an app on the phone, which has latencies varying on wifi but stable on 4G)
Trace to 89.148.12.15
1 - 192.168.100.1 (––)
499 4 (ms)
Avg: 251 ms Loss: 0/2 (0 %)
2 - 182.176.0.120 (PK)
7 17 (ms)
Avg: 12 ms Loss: 0/2 (0 %)
3 - 10.10.100.2 (––)
6 10 (ms)
Avg: 8 ms Loss: 0/2 (0 %)
4 - 10.0.2.149 (––)
25 374 (ms)
Avg: 199 ms Loss: 0/2 (0 %)
5 - 10.1.1.6 (––)
29 46 (ms)
Avg: 37 ms Loss: 0/2 (0 %)
6 - 202.125.128.157 (PK)
29 30 (ms)
Avg: 29 ms Loss: 0/2 (0 %)
7 - 221.120.248.1 (PK)
45 51 (ms)
Avg: 48 ms Loss: 0/2 (0 %)
8 - 195.229.28.104 (AE)
Loss: 2/2 (100 %)
9 - 195.229.31.80 (AE)
Loss: 2/2 (100 %)
10 - 195.229.29.226 (AE)
64 512 (ms)
Avg: 288 ms Loss: 0/2 (0 %)
11 -
12 -
13 - 89.148.12.15 (BH)
62 105 (ms)
Avg: 83 ms Loss: 0/2 (0 %)
62ms. Approx. Not bad. And I'm in Islamabad.
As for Mobilink 4G, which uses TW (for comparison sake), this is what I get:
Trace to 89.148.12.15
1 -
2 - 10.227.18.101 (––)
49 42 (ms)
Avg: 45 ms Loss: 0/2 (0 %)
3 - 10.232.40.165 (––)
30 66 (ms)
Avg: 48 ms Loss: 0/2 (0 %)
4 - 10.232.40.161 (––)
35 47 (ms)
Avg: 41 ms Loss: 0/2 (0 %)
5 - 10.232.40.13 (––)
Loss: 2/2 (100 %)
6 - 10.232.40.6 (––)
83 115 (ms)
Avg: 99 ms Loss: 0/2 (0 %)
7 - 119.30.105.237 (PK)
28 38 (ms)
Avg: 33 ms Loss: 0/2 (0 %)
8 - 119.30.105.201 (PK)
25 55 (ms)
Avg: 40 ms Loss: 0/2 (0 %)
9 - 119.30.106.41 (PK)
56 52 (ms)
Avg: 54 ms Loss: 0/2 (0 %)
10 - 117.20.31.5 (PK)
56 53 (ms)
Avg: 54 ms Loss: 0/2 (0 %)
11 - 110.93.252.190 (PK)
61 84 (ms)
Avg: 72 ms Loss: 0/2 (0 %)
12 - 213.144.176.232 (IT)
212 184 (ms)
Avg: 198 ms Loss: 0/2 (0 %)
13 - 213.144.176.177 (IT)
166 171 (ms)
Avg: 168 ms Loss: 0/2 (0 %)
14 - 89.211.6.225 (QA)
159 163 (ms)
Avg: 161 ms Loss: 0/2 (0 %)
15 - 89.211.3.74 (QA)
164 159 (ms)
Avg: 161 ms Loss: 0/2 (0 %)
16 - 82.148.106.102 (QA)
Loss: 2/2 (100 %)
17 -
18 -
19 - 89.148.12.15 (BH)
257 253 (ms)
Avg: 255 ms Loss: 0/2 (0 %)
Sent from my Pixel 2 using Tapatalk
Interestingly, if you ping the second last hop on the PTCL traceroute from your TW connection you will route perfectly so a connection exists but may need some tinkering from the Arab ISP or TW.