[SOLVED] .::The Official Mega PTCL Thread::. -- A Sequel Without Drama!! || [All is well!]

Status
Not open for further replies.

manobilla

Proficient
Jun 3, 2018
568
7
14
1.1.1.1 - Islamabad. I'm from Rawalpindi.

Sent from my Pixel 2 using Tapatalk
i am less than 200km from Islamabad getting higher ping compared to Karachi. I was getting 41ms to Karachi but Islamabad is 50ms
Pinging 1.0.0.1 with 32 bytes of data:
Reply from 1.0.0.1: bytes=32 time=51ms TTL=247
Reply from 1.0.0.1: bytes=32 time=51ms TTL=247
Reply from 1.0.0.1: bytes=32 time=51ms TTL=247
Reply from 1.0.0.1: bytes=32 time=51ms TTL=247
Pinging 1.1.1.1 with 32 bytes of data:
Reply from 1.1.1.1: bytes=32 time=48ms TTL=247
Reply from 1.1.1.1: bytes=32 time=48ms TTL=247
Reply from 1.1.1.1: bytes=32 time=48ms TTL=247
Reply from 1.1.1.1: bytes=32 time=48ms TTL=247
 

Farrukhkazimi

Proficient
Jul 3, 2012
559
6
23
Karachi
PTCL is definitely feeling the heat and now they are constantly working towards their shit routing and improving day by day. I never expected that I will get this ping towards EUROPE any day.

C:\Users\QC>tracert lux.valve.net

Tracing route to lux.valve.net [146.66.152.2]
over a maximum of 30 hops:


1 <1 ms <1 ms <1 ms 192.168.10.1
2 15 ms 147 ms 8 ms 39.50.128.1
3 10 ms 7 ms 7 ms 10.0.4.241
4 8 ms 7 ms 7 ms 10.0.4.90
5 11 ms 11 ms 11 ms static-10ge-khi275-p01-swb.pie.net.pk [202.125.1
28.156]
6 11 ms 11 ms 11 ms hi77c2-sw494b.pie.net.pk [202.125.128.134]
7 25 ms 25 ms 25 ms 195.229.27.133
8 25 ms 25 ms 24 ms 195.229.0.93
9 124 ms 124 ms 124 ms 195.229.0.135
10 200 ms 200 ms 200 ms decix.valve.net [80.81.193.63]
11 197 ms 212 ms 195 ms 192.168.135.7
12 * * * Request timed out.
13 * * * Request timed out.
14 127 ms 129 ms 127 ms fw0.lux.valve.net [146.66.152.2]


Trace complete.
 

manobilla

Proficient
Jun 3, 2018
568
7
14
PTCL is definitely feeling the heat and now they are constantly working towards their shit routing and improving day by day. I never expected that I will get this ping towards EUROPE any day.
here 166ms
Pinging lux.valve.net [146.66.152.2] with 32 bytes of data:
Reply from 146.66.152.2: bytes=32 time=166ms TTL=248
Reply from 146.66.152.2: bytes=32 time=165ms TTL=248
Reply from 146.66.152.2: bytes=32 time=165ms TTL=248
Reply from 146.66.152.2: bytes=32 time=165ms TTL=248
 

maazsk97

Active member
Jun 23, 2017
382
18
13
Pakistan, Lahore
They finally fixed high pings to Singapore servers for me too after a couple of emails but ping to EU is bad now which I don't care much about but it would be amazing if they can somehow improve routing for both regions. Would definitely love to play some matches on EU and I have a much better rank in EU too.
 

murtaza12

Global Moderator
Global Mod
Oct 27, 2011
10,758
128
69
They finally fixed high pings to Singapore servers for me too after a couple of emails but ping to EU is bad now which I don't care much about but it would be amazing if they can somehow improve routing for both regions. Would definitely love to play some matches on EU and I have a much better rank in EU too.
Lol can't ask for too much now [emoji23]

Can you post a trace route to these AWS servers?

Frankfurt:

35.156.63.252

Singapore;

13.250.0.253

Ireland:

79.125.120.9
 

maazsk97

Active member
Jun 23, 2017
382
18
13
Pakistan, Lahore
Lol can't ask for too much now [emoji23]

Can you post a trace route to these AWS servers?

Frankfurt:

35.156.63.252

Singapore;

13.250.0.253

Ireland:

79.125.120.9
Spoiler: show


Tracing route to ec2-35-156-63-252.eu-central-1.compute.amazonaws.com [35.156.63.252]
over a maximum of 30 hops:


1 <1 ms <1 ms <1 ms DumaOS.lan [192.168.88.1]
2 1 ms <1 ms <1 ms 192.168.10.1
3 * * * Request timed out.
4 9 ms 10 ms 9 ms 10.0.6.1
5 5 ms 5 ms 5 ms 10.0.3.89
6 23 ms 23 ms 23 ms 10.2.1.10
7 31 ms 30 ms 30 ms static-10ge-khi494-p01-khi494-swb.pie.net.pk [202.125.128.157]
8 29 ms 27 ms 30 ms khi494.nxa.2c.ptcl.com.pk [221.120.248.5]
9 119 ms 119 ms 119 ms te0-7-0-7.ccr21.mrs01.atlas.cogentco.com [149.14.126.9]
10 140 ms 140 ms 139 ms be3080.ccr51.zrh02.atlas.cogentco.com [130.117.49.2]
11 149 ms 149 ms 149 ms be3072.ccr21.muc03.atlas.cogentco.com [130.117.0.18]
12 152 ms 151 ms 151 ms be2959.ccr41.fra03.atlas.cogentco.com [154.54.36.53]
13 149 ms 152 ms 150 ms a100-row.demarc.cogentco.com [149.14.158.178]
14 * * * Request timed out.
15 149 ms 148 ms 151 ms 52.93.111.182
16 216 ms 215 ms 218 ms 52.93.111.191
17 208 ms 208 ms 208 ms 54.239.107.161
18 208 ms 209 ms 207 ms 52.93.23.126
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 216 ms 215 ms 215 ms ec2-35-156-63-252.eu-central-1.compute.amazonaws.com [35.156.63.252]


Trace complete.


Tracing route to ec2-13-250-0-253.ap-southeast-1.compute.amazonaws.com [13.250.0.253]
over a maximum of 30 hops:


1 <1 ms <1 ms <1 ms DumaOS.lan [192.168.88.1]
2 1 ms <1 ms <1 ms 192.168.10.1
3 * * * Request timed out.
4 22 ms 16 ms 34 ms 10.0.6.1
5 5 ms 7 ms 6 ms 10.0.3.89
6 23 ms 23 ms 22 ms 10.2.1.10
7 28 ms 26 ms 26 ms khi275.c2.nxa.ptcl.com.pk [221.120.248.12]
8 27 ms 26 ms 26 ms khi494.nxa.2c.ptcl.com.pk [221.120.248.5]
9 124 ms 124 ms 124 ms te0-0-0-1.ccr21.mrs01.atlas.cogentco.com [149.14.125.209]
10 127 ms 128 ms 127 ms pccw.mrs01.atlas.cogentco.com [130.117.14.62]
11 290 ms 291 ms 291 ms TenGE0-1-0-17.br02.hkg12.pccwbtn.net [63.218.174.61]
12 293 ms 298 ms 299 ms amazon.buneth1.br02.hkg12.pccwbtn.net [63.217.254.74]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 293 ms 289 ms 290 ms 52.93.9.144
18 289 ms 286 ms 289 ms 52.93.10.239
19 296 ms 290 ms 291 ms 52.93.10.236
20 296 ms 289 ms 286 ms 52.93.9.141
21 289 ms 289 ms 285 ms 52.93.10.101
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 291 ms 292 ms * ec2-13-250-0-253.ap-southeast-1.compute.amazonaws.com [13.250.0.253]
28 305 ms 297 ms 292 ms ec2-13-250-0-253.ap-southeast-1.compute.amazonaws.com [13.250.0.253]


Trace complete.


Tracing route to ec2-79-125-120-9.eu-west-1.compute.amazonaws.com [79.125.120.9]
over a maximum of 30 hops:


1 <1 ms <1 ms <1 ms DumaOS.lan [192.168.88.1]
2 1 ms <1 ms <1 ms 192.168.10.1
3 * * * Request timed out.
4 5 ms 9 ms 5 ms 10.0.6.5
5 5 ms 5 ms 5 ms 182.176.139.250
6 23 ms 22 ms 28 ms 10.2.1.10
7 24 ms 27 ms 27 ms khi275.c2.nxa.ptcl.com.pk [221.120.248.12]
8 30 ms 30 ms 31 ms static.khi77.pie.net.pk [202.125.128.171]
9 123 ms 123 ms 124 ms te0-7-0-12.ccr21.mrs01.atlas.cogentco.com [149.14.126.17]
10 138 ms 137 ms 137 ms be3092.ccr41.par01.atlas.cogentco.com [130.117.49.153]
11 137 ms 137 ms 137 ms be3684.ccr51.lhr01.atlas.cogentco.com [154.54.60.170]
12 141 ms 141 ms 141 ms be3671.agr21.lhr01.atlas.cogentco.com [130.117.48.138]
13 144 ms 144 ms 144 ms a100-row.demarc.cogentco.com [149.14.196.218]
14 217 ms 218 ms 220 ms 52.95.61.22
15 210 ms 210 ms 210 ms 52.95.61.31
16 * * * Request timed out.
17 226 ms 226 ms 227 ms 54.239.41.122
18 * * * Request timed out.
19 234 ms 222 ms 241 ms 52.93.6.146
20 227 ms 226 ms 226 ms 52.93.101.15
21 194 ms 153 ms 181 ms 52.93.101.22
22 155 ms 155 ms 155 ms 52.93.7.149
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 155 ms 155 ms 155 ms ec2-79-125-120-9.eu-west-1.compute.amazonaws.com [79.125.120.9]


Trace complete.

 
Last edited by a moderator:

shaheerk

Well-known member
Feb 5, 2013
2,370
106
68
PTCL is definitely feeling the heat and now they are constantly working towards their shit routing and improving day by day. I never expected that I will get this ping towards EUROPE any day.
Yeah, I've noticed that pings have improved CONSIDERABLY to various websites. Which is great! Pings to Europe (France, Greece) are comparable to pings to Singapore - impressive (though it doesn't make sense why, since France is geographically farther away from Pakistan than Singapore is, I think).

here 166ms
Pinging lux.valve.net [146.66.152.2] with 32 bytes of data:
Reply from 146.66.152.2: bytes=32 time=166ms TTL=248
Reply from 146.66.152.2: bytes=32 time=165ms TTL=248
Reply from 146.66.152.2: bytes=32 time=165ms TTL=248
Reply from 146.66.152.2: bytes=32 time=165ms TTL=248
Pinging from Karachi vs. Islamabad (in my case) results in pings being about 25ms lower (from Karachi). I'm getting 155ms (fiber, Islamabad).

Lol can't ask for too much now [emoji23]

Can you post a trace route to these AWS servers?

Frankfurt:

35.156.63.252
Spoiler: show


Tracing route to ec2-35-156-63-252.eu-central-1.compute.amazonaws.com [35.156.63.252]
over a maximum of 30 hops:


1 3 ms 2 ms 1 ms 192.168.100.1
2 3 ms 3 ms 3 ms 182.176.0.120
3 4 ms 4 ms 4 ms 10.0.2.221
4 4 ms 4 ms 14 ms 10.0.2.149
5 22 ms 22 ms 23 ms 10.1.1.6
6 24 ms 24 ms 24 ms static-10GE-KHI494-P01-KHI494-SWB.pie.net.pk [202.125.128.157]
7 27 ms 24 ms 24 ms khi494.nxa.2c.ptcl.com.pk [221.120.248.5]
8 126 ms 125 ms 125 ms te0-0-0-14.ccr21.mrs01.atlas.cogentco.com [149.14.125.225]
9 156 ms 142 ms 142 ms be3080.ccr51.zrh02.atlas.cogentco.com [130.117.49.2]
10 155 ms 152 ms 153 ms be3072.ccr21.muc03.atlas.cogentco.com [130.117.0.18]
11 148 ms 147 ms 148 ms be2959.ccr41.fra03.atlas.cogentco.com [154.54.36.53]
12 157 ms 153 ms 153 ms a100-row.demarc.cogentco.com [149.14.158.178]
13 148 ms 148 ms 148 ms 54.239.107.102
14 * * * Request timed out.
15 149 ms 149 ms 148 ms 52.93.111.147
16 149 ms 149 ms 150 ms 54.239.107.29
17 149 ms 149 ms 149 ms 52.93.23.126
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 151 ms 151 ms 150 ms ec2-35-156-63-252.eu-central-1.compute.amazonaws.com [35.156.63.252]

Singapore;

13.250.0.253
This one is particularly slow. It seems to go to France first (Marseilles) and then Hong Kong. But interestingly, pings to France are very, very low!

Tracing route to ec2-13-250-0-253.ap-southeast-1.compute.amazonaws.com [13.250.0.253]
over a maximum of 30 hops:


1 2 ms 2 ms 1 ms 192.168.100.1
2 10 ms 3 ms 4 ms 182.176.0.120
3 5 ms 5 ms 12 ms 10.10.100.2
4 4 ms 6 ms 3 ms 10.0.2.149
5 23 ms 23 ms 27 ms 10.1.1.6
6 24 ms 25 ms 25 ms rwp44.pie.net.pk [221.120.248.11]
7 26 ms 29 ms 29 ms static.khi77.pie.net.pk [202.125.128.151]
8 124 ms 125 ms 119 ms te0-0-0-1.ccr21.mrs01.atlas.cogentco.com [149.14.125.209]
9 119 ms 120 ms 119 ms pccw.mrs01.atlas.cogentco.com [130.117.14.62]
10 289 ms 288 ms 288 ms TenGE0-1-0-17.br02.hkg12.pccwbtn.net [63.218.174.61]
11 289 ms 289 ms 290 ms amazon.buneth1.br02.hkg12.pccwbtn.net [63.217.254.74]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 290 ms 288 ms 288 ms 52.93.9.104
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 387 ms 386 ms 386 ms ec2-13-250-0-253.ap-southeast-1.compute.amazonaws.com [13.250.0.253]

Ireland:

79.125.120.9
Tracing route to ec2-79-125-120-9.eu-west-1.compute.amazonaws.com [79.125.120.9]
over a maximum of 30 hops:


1 2 ms 1 ms 1 ms 192.168.100.1
2 3 ms 3 ms 3 ms 182.176.0.120
3 6 ms 4 ms 4 ms 10.0.0.1
4 4 ms 4 ms 4 ms 10.0.2.149
5 24 ms 25 ms 23 ms 10.1.1.6
6 27 ms 26 ms 26 ms khi275.c2.nxa.ptcl.com.pk [221.120.248.12]
7 24 ms 23 ms 24 ms khi494.nxb.2c.ptcl.com.pk [221.120.248.45]
8 131 ms 131 ms 134 ms te0-4-0-17.ccr21.mrs01.atlas.cogentco.com [149.14.125.241]
9 138 ms 138 ms 138 ms be3092.ccr41.par01.atlas.cogentco.com [130.117.49.153]
10 154 ms 154 ms 154 ms be3684.ccr51.lhr01.atlas.cogentco.com [154.54.60.170]
11 154 ms 154 ms 156 ms be3671.agr21.lhr01.atlas.cogentco.com [130.117.48.138]
12 154 ms 153 ms 151 ms a100-row.demarc.cogentco.com [149.14.196.218]
13 165 ms 155 ms 173 ms 52.95.61.22
14 156 ms 163 ms 159 ms 52.95.61.147
15 * * * Request timed out.
16 169 ms 168 ms 168 ms 176.32.106.239
17 * * * Request timed out.
18 169 ms 171 ms 169 ms 52.93.6.148
19 165 ms 168 ms 165 ms 52.93.101.21
20 159 ms 159 ms 158 ms 52.93.101.44
21 165 ms 165 ms 165 ms 52.93.7.139
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 158 ms 158 ms 158 ms ec2-79-125-120-9.eu-west-1.compute.amazonaws.com [79.125.120.9]

 
Last edited by a moderator:

murtaza12

Global Moderator
Global Mod
Oct 27, 2011
10,758
128
69
Yeah, I've noticed that pings have improved CONSIDERABLY to various websites. Which is great! Pings to Europe (France, Greece) are comparable to pings to Singapore - impressive (though it doesn't make sense why, since France is geographically farther away from Pakistan than Singapore is, I think).



Pinging from Karachi vs. Islamabad (in my case) results in pings being about 25ms lower (from Karachi). I'm getting 155ms (fiber, Islamabad).



Spoiler: show


Tracing route to ec2-35-156-63-252.eu-central-1.compute.amazonaws.com [35.156.63.252]
over a maximum of 30 hops:


1 3 ms 2 ms 1 ms 192.168.100.1
2 3 ms 3 ms 3 ms 182.176.0.120
3 4 ms 4 ms 4 ms 10.0.2.221
4 4 ms 4 ms 14 ms 10.0.2.149
5 22 ms 22 ms 23 ms 10.1.1.6
6 24 ms 24 ms 24 ms static-10GE-KHI494-P01-KHI494-SWB.pie.net.pk [202.125.128.157]
7 27 ms 24 ms 24 ms khi494.nxa.2c.ptcl.com.pk [221.120.248.5]
8 126 ms 125 ms 125 ms te0-0-0-14.ccr21.mrs01.atlas.cogentco.com [149.14.125.225]
9 156 ms 142 ms 142 ms be3080.ccr51.zrh02.atlas.cogentco.com [130.117.49.2]
10 155 ms 152 ms 153 ms be3072.ccr21.muc03.atlas.cogentco.com [130.117.0.18]
11 148 ms 147 ms 148 ms be2959.ccr41.fra03.atlas.cogentco.com [154.54.36.53]
12 157 ms 153 ms 153 ms a100-row.demarc.cogentco.com [149.14.158.178]
13 148 ms 148 ms 148 ms 54.239.107.102
14 * * * Request timed out.
15 149 ms 149 ms 148 ms 52.93.111.147
16 149 ms 149 ms 150 ms 54.239.107.29
17 149 ms 149 ms 149 ms 52.93.23.126
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 151 ms 151 ms 150 ms ec2-35-156-63-252.eu-central-1.compute.amazonaws.com [35.156.63.252]



This one is particularly slow. It seems to go to France first (Marseilles) and then Hong Kong. But interestingly, pings to France are very, very low!

Tracing route to ec2-13-250-0-253.ap-southeast-1.compute.amazonaws.com [13.250.0.253]
over a maximum of 30 hops:


1 2 ms 2 ms 1 ms 192.168.100.1
2 10 ms 3 ms 4 ms 182.176.0.120
3 5 ms 5 ms 12 ms 10.10.100.2
4 4 ms 6 ms 3 ms 10.0.2.149
5 23 ms 23 ms 27 ms 10.1.1.6
6 24 ms 25 ms 25 ms rwp44.pie.net.pk [221.120.248.11]
7 26 ms 29 ms 29 ms static.khi77.pie.net.pk [202.125.128.151]
8 124 ms 125 ms 119 ms te0-0-0-1.ccr21.mrs01.atlas.cogentco.com [149.14.125.209]
9 119 ms 120 ms 119 ms pccw.mrs01.atlas.cogentco.com [130.117.14.62]
10 289 ms 288 ms 288 ms TenGE0-1-0-17.br02.hkg12.pccwbtn.net [63.218.174.61]
11 289 ms 289 ms 290 ms amazon.buneth1.br02.hkg12.pccwbtn.net [63.217.254.74]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 290 ms 288 ms 288 ms 52.93.9.104
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 387 ms 386 ms 386 ms ec2-13-250-0-253.ap-southeast-1.compute.amazonaws.com [13.250.0.253]



Tracing route to ec2-79-125-120-9.eu-west-1.compute.amazonaws.com [79.125.120.9]
over a maximum of 30 hops:


1 2 ms 1 ms 1 ms 192.168.100.1
2 3 ms 3 ms 3 ms 182.176.0.120
3 6 ms 4 ms 4 ms 10.0.0.1
4 4 ms 4 ms 4 ms 10.0.2.149
5 24 ms 25 ms 23 ms 10.1.1.6
6 27 ms 26 ms 26 ms khi275.c2.nxa.ptcl.com.pk [221.120.248.12]
7 24 ms 23 ms 24 ms khi494.nxb.2c.ptcl.com.pk [221.120.248.45]
8 131 ms 131 ms 134 ms te0-4-0-17.ccr21.mrs01.atlas.cogentco.com [149.14.125.241]
9 138 ms 138 ms 138 ms be3092.ccr41.par01.atlas.cogentco.com [130.117.49.153]
10 154 ms 154 ms 154 ms be3684.ccr51.lhr01.atlas.cogentco.com [154.54.60.170]
11 154 ms 154 ms 156 ms be3671.agr21.lhr01.atlas.cogentco.com [130.117.48.138]
12 154 ms 153 ms 151 ms a100-row.demarc.cogentco.com [149.14.196.218]
13 165 ms 155 ms 173 ms 52.95.61.22
14 156 ms 163 ms 159 ms 52.95.61.147
15 * * * Request timed out.
16 169 ms 168 ms 168 ms 176.32.106.239
17 * * * Request timed out.
18 169 ms 171 ms 169 ms 52.93.6.148
19 165 ms 168 ms 165 ms 52.93.101.21
20 159 ms 159 ms 158 ms 52.93.101.44
21 165 ms 165 ms 165 ms 52.93.7.139
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 158 ms 158 ms 158 ms ec2-79-125-120-9.eu-west-1.compute.amazonaws.com [79.125.120.9]

The route to Europe is pretty good, should be the same hopefully when I switch back to PTCL.

It's Singapore that's gonna be a pain. They need to get that fixed.
 

shaheerk

Well-known member
Feb 5, 2013
2,370
106
68
The route to Europe is pretty good, should be the same hopefully when I switch back to PTCL.

It's Singapore that's gonna be a pain. They need to get that fixed.
I think they'll get it fixed eventually. They did fix Europe (because I was getting 300ms to websites in Europe and 220ms to websites in the US...)

Also, PTCL needs to figure out which CDNs are in Singapore and route traffic to there instead of Europe. And Google DNS needs to get its act together (it's giving me IPs to farther away CDNs). But it's probably not a Google issue since OpenDNS is giving me farther away IPs as well. I only use these two DNS servers because they work properly for Akamai.

For example, Google/OpenDNS give me
Server: google-public-dns-a.google.com
Address: 8.8.8.8


Non-authoritative answer:
Name: en.wikipedia.org
Addresses: 2001:df2:e500:ed1a::1
103.102.166.224

Pinging en.wikipedia.org [103.102.166.224] with 32 bytes of data:
Reply from 103.102.166.224: bytes=32 time=217ms TTL=55
Reply from 103.102.166.224: bytes=32 time=217ms TTL=55
Reply from 103.102.166.224: bytes=32 time=217ms TTL=55
Reply from 103.102.166.224: bytes=32 time=219ms TTL=55
And if I use C&W's DNS (located in Europe - which isn't good for Akamai requests but gives me IPs to servers in Europe, which mean consistent pings to European servers (unless PTCL's route entail shifting traffic towards Singapore or Dubai), then this is what I get:
Server: cns1.cw.net
Address: 141.1.1.1


Non-authoritative answer:
Name: en.wikipedia.org
Addresses: 2620:0:862:ed1a::1
91.198.174.192


Pinging 91.198.174.192 with 32 bytes of data:Reply from 91.198.174.192: bytes=32 time=159ms TTL=57
Reply from 91.198.174.192: bytes=32 time=164ms TTL=57
Reply from 91.198.174.192: bytes=32 time=162ms TTL=57
Reply from 91.198.174.192: bytes=32 time=156ms TTL=57
Usually, when I try to ping ax.itunes.apple.com, it gives me an IP to a local Akamai server (either in Karachi or somewhere else in Pakistan - maybe Islamabad? Can't recall) but right now, it's giving me an IP to somewhere in Europe.
 

manobilla

Proficient
Jun 3, 2018
568
7
14
Lol can't ask for too much now [emoji23]

Can you post a trace route to these AWS servers?

Frankfurt:

35.156.63.252

Singapore;

13.250.0.253

Ireland:

79.125.120.9
Spoiler: show


Tracing route to ec2-35-156-63-252.eu-central-1.compute.amazonaws.com [35.156.63.252]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 <1 ms <1 ms <1 ms 192.168.10.1
3 102 ms 260 ms 280 ms 182.187.0.1
4 23 ms 22 ms 22 ms 10.0.5.45
5 66 ms 22 ms 23 ms 182.176.139.181
6 45 ms 45 ms 45 ms 10.2.1.10
7 42 ms 43 ms 43 ms khi275.c1.nxa.ptcl.com.pk [221.120.248.11]
8 46 ms 43 ms 43 ms khi494.nxb.2c.ptcl.com.pk [221.120.248.45]
9 167 ms 175 ms 171 ms te0-0-0-14.ccr21.mrs01.atlas.cogentco.com [149.14.125.225]
10 192 ms 198 ms 198 ms be3080.ccr51.zrh02.atlas.cogentco.com [130.117.49.2]
11 192 ms 194 ms 193 ms be3072.ccr21.muc03.atlas.cogentco.com [130.117.0.18]
12 198 ms 197 ms 202 ms be2959.ccr41.fra03.atlas.cogentco.com [154.54.36.53]
13 208 ms 204 ms 209 ms a100-row.demarc.cogentco.com [149.14.158.178]
14 167 ms 167 ms 167 ms 54.239.107.146
15 168 ms 168 ms 167 ms 52.93.111.158
16 169 ms 171 ms 169 ms 52.93.111.157
17 169 ms 169 ms 169 ms 54.239.107.139
18 167 ms 167 ms 167 ms 52.93.23.126
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 171 ms 171 ms 171 ms ec2-35-156-63-252.eu-central-1.compute.amazonaws.com [35.156.63.252]

Trace complete.



Tracing route to ec2-13-250-0-253.ap-southeast-1.compute.amazonaws.com [13.250.0.253]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 <1 ms <1 ms <1 ms 192.168.10.1
3 259 ms 325 ms 164 ms 182.187.0.1
4 21 ms 21 ms 22 ms 10.0.5.81
5 22 ms 22 ms 22 ms 182.176.139.181
6 40 ms 39 ms 40 ms 10.2.1.10
7 42 ms 43 ms 43 ms khi275.c1.nxa.ptcl.com.pk [221.120.248.11]
8 45 ms 43 ms 42 ms static.khi77.pie.net.pk [202.125.128.151]
9 152 ms 150 ms 150 ms te0-7-0-7.ccr21.mrs01.atlas.cogentco.com [149.14.126.9]
10 158 ms 155 ms 152 ms pccw.mrs01.atlas.cogentco.com [130.117.14.62]
11 486 ms 483 ms 472 ms hundredge0-3-0-0.br02.hkg12.pccwbtn.net [63.218.174.193]
12 488 ms 495 ms 480 ms amazon.buneth1.br02.hkg12.pccwbtn.net [63.217.254.74]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 510 ms 510 ms 510 ms 203.83.223.79
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 519 ms 523 ms 529 ms ec2-13-250-0-253.ap-southeast-1.compute.amazonaws.com [13.250.0.253]

Trace complete.

530ms for Singapore haha ��



Tracing route to ec2-79-125-120-9.eu-west-1.compute.amazonaws.com [79.125.120.9]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 <1 ms <1 ms <1 ms 192.168.10.1
3 31 ms 22 ms 24 ms 182.187.0.1
4 28 ms 22 ms 22 ms 10.0.7.58
5 22 ms 22 ms 22 ms 182.176.139.181
6 41 ms 41 ms 41 ms 10.2.1.10
7 44 ms 43 ms 47 ms khi275.c2.nxa.ptcl.com.pk [221.120.248.12]
8 45 ms 47 ms 47 ms khi494.nxa.2c.ptcl.com.pk [221.120.248.5]
9 170 ms 172 ms 176 ms te0-0-0-1.ccr21.mrs01.atlas.cogentco.com [149.14.125.209]
10 180 ms 183 ms 182 ms be3092.ccr41.par01.atlas.cogentco.com [130.117.49.153]
11 168 ms 167 ms 165 ms be3684.ccr51.lhr01.atlas.cogentco.com [154.54.60.170]
12 192 ms 193 ms 198 ms be3671.agr21.lhr01.atlas.cogentco.com [130.117.48.138]
13 162 ms 162 ms 162 ms a100-row.demarc.cogentco.com [149.14.196.218]
14 165 ms 165 ms 166 ms 52.95.61.106
15 158 ms 158 ms 158 ms 52.95.61.161
16 * * * Request timed out.
17 171 ms 171 ms 171 ms 54.239.41.122
18 * * * Request timed out.
19 177 ms 176 ms 177 ms 52.93.6.154
20 167 ms 167 ms 167 ms 52.93.101.41
21 170 ms 171 ms 170 ms 52.93.101.32
22 176 ms 173 ms 174 ms 52.93.7.137
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 171 ms 171 ms 171 ms ec2-79-125-120-9.eu-west-1.compute.amazonaws.com [79.125.120.9]

 
Last edited by a moderator:
Status
Not open for further replies.
General chit-chat
Help Users
IMPORTANT: Please Change Your Passwords to avoid being botted. | Click for Discord
  • No one is chatting at the moment.
  • GloriousChicken GloriousChicken:
    Everyone, please change your passwords.
    Link
  • Necrokiller Necrokiller:
    The only valid thing from his pov he said in the video is AC dead since Black Flag. According to woke police that game was woke too. Welsh man in West Indies. So atleast he's consistent I guess lol
    Link
  • Link
  • XPremiuM XPremiuM:
    Necrokiller said:
    It's based on an actual real life person so I don't think the woke police have a valid case here.
    Nope. They have a very valid case. The above video explains it all.
    Link
  • Necrokiller Necrokiller:
    It's based on an actual real life person so I don't think the woke police have a valid case here.
    • Like
    Reactions: SolitarySoldier
    Link
  • XPremiuM XPremiuM:
    Meanwhile Ghost of Tsushima PC version is out now. Looks 100 times better than ASS Creed already.
    Link
  • XPremiuM XPremiuM:
    Did y'all see the new Assassin's Creed trailer? They finally made a AC set in Japan & then they put a negro as the male protagonist. Ubisoft is taking cues from Disney, and it isn't gonna end well for them, just like Disney. Go woke, go broke!
    Link
  • Necrokiller Necrokiller:
    First Fallout 4 update and now this 🤡
    Link
  • Necrokiller Necrokiller:
    MS and Bethesda continuing their streak of massive Ls 😬
    Link
  • Link
  • funky funky:
    Hello
    Link
  • NaNoW NaNoW:
    by closing down good studios
    Link
  • NaNoW NaNoW:
    well he is breaking barriers
    • Like
    Reactions: KetchupBiryani
    Link
  • iampasha iampasha:
    SolitarySoldier said:
    Phil keeps talking about breaking barriers to gaming, making it accessible on all platforms yada yada, while killing competition and creativity at the same time. the fact that i actually believed him for a second lol
    guys the biggest yapper in the Industry right now. All he do is yap
    Link
  • Necrokiller Necrokiller:
    Phil should be held responsible for this shitfest too, just like Sarah, but it's highly likely that these decisions are coming from Satya. And this isn't even the end of it. More closures are coming.
    Link
  • SolitarySoldier SolitarySoldier:
    if we are moving towards more and more popular trash across platforms that make billions for companies, I'm happy with all the barriers and exclusivity because at least that brings some pressure to create good stuff.
    Link
  • SolitarySoldier SolitarySoldier:
    Phil keeps talking about breaking barriers to gaming, making it accessible on all platforms yada yada, while killing competition and creativity at the same time. the fact that i actually believed him for a second lol
    Link
  • SolitarySoldier SolitarySoldier:
    "These changes are not a reflection of the creativity and skill of the talented individuals at these teams or the risks they took to try new things" ... seems to me that's exactly what it is
    Link
  • SolitarySoldier SolitarySoldier:
    why make good games when u can just buy everyone and shut them down lol
    Link
  • XPremiuM XPremiuM:
    I'm gonna say one last time, F*** Microsoft to infinity!
    Link
  • XPremiuM XPremiuM:
    Microsoft deserves all the hate they can get. Seriously i can't explain how much i want to curse them out.
    Link
  • XPremiuM XPremiuM:
    They could've sold the studios instead of closing them, but the nazi bastards just didn't want competition down the road.
    Link
  • Link
  • XPremiuM XPremiuM:
    F*** Microsoft, and F*** their fanboys.
    Link
  • XPremiuM XPremiuM:
    What's the f*** is wrong with them? I mean really? Have they completely lost it? F***ing retards.
    Link
    GloriousChicken GloriousChicken: Everyone, please change your passwords.