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

manobilla · Feb 9, 2019

shaheerk said:
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

dms664 · Feb 9, 2019

murtaza12 said:
Screenshot showing line stats would help.

Here you go

https://imgur.com/a/RSzJPNE

murtaza12 · Feb 9, 2019

dms664 said:
Here you go

https://imgur.com/a/RSzJPNE

No reason for it to be feeling sluggish, your line stats are perfect.

What DNS do you use?

Farrukhkazimi · Feb 9, 2019

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 · Feb 9, 2019

Farrukhkazimi said:
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 · Feb 9, 2019

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.

maazsk97 · Feb 9, 2019

This is basically like the closest thing to a GPON connection now: https://imgur.com/fWlP6mK

Except the upload is a bit low compared to GPON but I am glad that they turned off interleaving and are working on fixing their routing issues.

murtaza12 · Feb 9, 2019

maazsk97 said:
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 · Feb 9, 2019

murtaza12 said:
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

moosvi94 · Feb 9, 2019

maazsk97 said:
This is basically like the closest thing to a GPON connection now: https://imgur.com/fWlP6mK

Except the upload is a bit low compared to GPON but I am glad that they turned off interleaving and are working on fixing their routing issues.

Same here, Happy with Ptcl after a long time

shaheerk · Feb 9, 2019

Farrukhkazimi said:
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).

manobilla said:
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).

murtaza12 said:
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

murtaza12 · Feb 9, 2019

shaheerk said:
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 · Feb 9, 2019

murtaza12 said:
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.

greyfreak19 · Feb 9, 2019

murtaza12 said:
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.

Switching back? why?

murtaza12 · Feb 9, 2019

greyfreak19 said:
Switching back? why?

I'm moving abroad later this year, I don't want my parents to deal with the headache of Transworlds billing every month.

greyfreak19 · Feb 9, 2019

murtaza12 said:
I'm moving abroad later this year, I don't want my parents to deal with the headache of Transworlds billing every month.

I see. Good luck with the PTCL. I bet they'll be thrilled to see ya.

murtaza12 · Feb 9, 2019

greyfreak19 said:
I see. Good luck with the PTCL. I bet they'll be thrilled to see ya.

It's going to be a very awkward visit to the exchange.

manobilla · Feb 10, 2019

murtaza12 said:
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

greyfreak19 · Feb 10, 2019

murtaza12 said:
It's going to be a very awkward visit to the exchange.

"Han bhai, agaye wapis? Transworld bakwas hai na?" followed by Transworld this and Transworld that

DarkRaiden112 · Feb 10, 2019

the 39.50.xx.xx ip pool still has bad pings to europe. not getting less then 280ms

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

Proficient

Intermediate

Global Moderator

Proficient

Proficient

Active member

Active member

Global Moderator

Active member

Active member

Well-known member

Global Moderator

Well-known member

Active member

Global Moderator

Active member

Global Moderator

Proficient

Active member

Beginner