Connect Communications :: A Smart Future

mhasan92

Knight Rider
Jun 5, 2011
500
0
21
Karachi
2500 ?? Your Area ?? My dealer is charging 3500 for brown yr 😡 [MENTION=14725]assasin42o[/MENTION]

Sent from my SM-G930U using Tapatalk
 
Oct 10, 2016
19
0
1
Hyderabad
bhai 2mb ki actuall price 600 hai, maine zyada se zyada 900 suni hai areas me but ye 1600 fr 2mb toh aap ne boht zyada bol di.
1700 toh mai 5mb red k de raha and i know ye bhi zyada hi de raha
tou bhai esaa nahi hosakta ke mein dusre area ke dealer se recharge card khareedun kam price mein ?? wo kaam karega mere net par?

Sent from my BLN-L21 using Tapatalk
 

assasin42o

Don Vito Corléone
Moderator
Aug 9, 2009
3,952
12
43
KHI ✈ ISL
So everyone's facing speed issues? My connection getting 1/3 of the total speed for the past 4 days

Sent from my Moto X Pure
 

skthegr8

Intermediate
Nov 29, 2014
170
0
21
Karachi
So everyone's facing speed issues? My connection getting 1/3 of the total speed for the past 4 days

Sent from my Moto X Pure
Written on their website:
"Connect Customers may face service degradation in peak hours due to service interruption at our upstream provider."
They also posted on Facebook about the issue.
Actually ptcl is their main upstream provider and it is facing problems due to that useless submarine cable.

Sent from my LGLS990 using Tapatalk
 

Pleasant

Expert
Jul 19, 2008
15,304
13
44
Dubai, UAE
2500 ?? Your Area ?? My dealer is charging 3500 for brown yr �� [MENTION=14725]assasin42o[/MENTION]

Sent from my SM-G930U using Tapatalk
Can someone provide me the connect dialer the all in one dialer and blue dialer and upload it somewhere i cannot down load it from there website
 

Revil

Newbie
Oct 30, 2015
20
0
1
Hey, could anyone here that is using Connect kindly share their pings/latency to Counter-Strike: Global Offensive's middle east, SEA and European servers.

Also what is their uptime like? Are there any issues these days with packet loss and insufficient speeds or do you get the full download and upload speeds that you pay for? Considering having this installed in replacement for PTCL in malir cantt.

Would appreciate any feedback!
 

FuriousNinja

Intermediate
Jul 27, 2015
153
0
11
Karachi
Hey, could anyone here that is using Connect kindly share their pings/latency to Counter-Strike: Global Offensive's middle east, SEA and European servers.

Also what is their uptime like? Are there any issues these days with packet loss and insufficient speeds or do you get the full download and upload speeds that you pay for? Considering having this installed in replacement for PTCL in malir cantt.

Would appreciate any feedback!
Uptime depends on your dealer honestly. If problems arise in your local area and dealer is reliable then the issues resolve pretty quickly.

Major downtimes only occured when there were faults in PTCL's submarine cables.

The speed is as advertised except on torrents which they usually now throttle. The best I get on Orange (3mb) package is 170kb/sec on torrents. Direct downloads are in the range of 400-450kb/sec easily and uploads are also around 250kb/sec or more.

Packet losses only occur if their upstream provider which is PTCL is having cable issues but changing IPs usually resolve this MOST of the time.

To be honest, this whole Connect experience actually depends on your area. Some people are experiencing horrendous speeds and pings whereas in my area I'm very satisfied with it considering that PTCL is the only other provider here.

As for your first query, I would be happy to provide you ping statistics if you can give specific servers (IPs?) to ping to. I usually get 130ish ms to EU West servers.
 

Revil

Newbie
Oct 30, 2015
20
0
1
Uptime depends on your dealer honestly. If problems arise in your local area and dealer is reliable then the issues resolve pretty quickly.

Major downtimes only occured when there were faults in PTCL's submarine cables.

The speed is as advertised except on torrents which they usually now throttle. The best I get on Orange (3mb) package is 170kb/sec on torrents. Direct downloads are in the range of 400-450kb/sec easily and uploads are also around 250kb/sec or more.

Packet losses only occur if their upstream provider which is PTCL is having cable issues but changing IPs usually resolve this MOST of the time.

To be honest, this whole Connect experience actually depends on your area. Some people are experiencing horrendous speeds and pings whereas in my area I'm very satisfied with it considering that PTCL is the only other provider here.

As for your first query, I would be happy to provide you ping statistics if you can give specific servers (IPs?) to ping to. I usually get 130ish ms to EU West servers.
130 to Eu servers is just incredible as I currently get about 160 or more to them on EU. What games are you playing online? I often only play CSGO or Overwatch.

Here's a list of some of valve's IP ranged for csgo. http://pastebin.com/raw/be4eZRKr
185.25.183.0-185.25.183.255 for Dubai

103.28.54.0-103.28.54.255 for SEA and

146.66.155.0-146.66.155.255 for EU

146.66.152.0-146.66.152.255
 

FuriousNinja

Intermediate
Jul 27, 2015
153
0
11
Karachi
130 to Eu servers is just incredible as I currently get about 160 or more to them on EU. What games are you playing online? I often only play CSGO or Overwatch.

Here's a list of some of valve's IP ranged for csgo. http://pastebin.com/raw/be4eZRKr
185.25.183.0-185.25.183.255 for Dubai

103.28.54.0-103.28.54.255 for SEA and

146.66.155.0-146.66.155.255 for EU

146.66.152.0-146.66.152.255
I mostly play Warface now. Used to play Paladins, BF1 and Warframe but got bored :p

Here are the stats:

*For Dubai:
Spoiler: show
Code:
Pinging 185.25.183.5 with 32 bytes of data:
Reply from 185.25.183.5: bytes=32 time=37ms TTL=52
Reply from 185.25.183.5: bytes=32 time=29ms TTL=52
Reply from 185.25.183.5: bytes=32 time=36ms TTL=52
Reply from 185.25.183.5: bytes=32 time=34ms TTL=52

Ping statistics for 185.25.183.5:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 29ms, Maximum = 37ms, Average = 34ms

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 

Pinging 185.25.183.50 with 32 bytes of data:
Reply from 185.25.183.50: bytes=32 time=30ms TTL=52
Reply from 185.25.183.50: bytes=32 time=35ms TTL=52
Reply from 185.25.183.50: bytes=32 time=35ms TTL=52
Reply from 185.25.183.50: bytes=32 time=31ms TTL=52

Ping statistics for 185.25.183.50:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 30ms, Maximum = 35ms, Average = 32ms
*For SEA:
Spoiler: show
Code:
Pinging 103.28.54.20 with 32 bytes of data:
Reply from 103.28.54.20: bytes=32 time=80ms TTL=52
Reply from 103.28.54.20: bytes=32 time=77ms TTL=52
Reply from 103.28.54.20: bytes=32 time=83ms TTL=52
Reply from 103.28.54.20: bytes=32 time=77ms TTL=52

Ping statistics for 103.28.54.20:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 77ms, Maximum = 83ms, Average = 79ms

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 

Pinging 103.28.54.65 with 32 bytes of data:
Reply from 103.28.54.65: bytes=32 time=77ms TTL=52
Reply from 103.28.54.65: bytes=32 time=77ms TTL=52
Reply from 103.28.54.65: bytes=32 time=78ms TTL=52
Reply from 103.28.54.65: bytes=32 time=83ms TTL=52

Ping statistics for 103.28.54.65:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 77ms, Maximum = 83ms, Average = 78ms
*For EU:
Spoiler: show
Code:
Pinging 146.66.155.6 with 32 bytes of data:
Reply from 146.66.155.6: bytes=32 time=144ms TTL=113
Reply from 146.66.155.6: bytes=32 time=143ms TTL=113
Reply from 146.66.155.6: bytes=32 time=142ms TTL=113
Reply from 146.66.155.6: bytes=32 time=145ms TTL=113

Ping statistics for 146.66.155.6:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 142ms, Maximum = 145ms, Average = 143ms
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 

Pinging 146.66.155.11 with 32 bytes of data:
Reply from 146.66.155.11: bytes=32 time=142ms TTL=113
Reply from 146.66.155.11: bytes=32 time=147ms TTL=113
Reply from 146.66.155.11: bytes=32 time=146ms TTL=113
Reply from 146.66.155.11: bytes=32 time=142ms TTL=113

Ping statistics for 146.66.155.11:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 142ms, Maximum = 147ms, Average = 144ms

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Pinging 146.66.152.50 with 32 bytes of data:
Reply from 146.66.152.50: bytes=32 time=135ms TTL=51
Reply from 146.66.152.50: bytes=32 time=137ms TTL=51
Reply from 146.66.152.50: bytes=32 time=136ms TTL=51
Reply from 146.66.152.50: bytes=32 time=135ms TTL=51

Ping statistics for 146.66.152.50:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 135ms, Maximum = 137ms, Average = 135ms

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Pinging 146.66.152.100 with 32 bytes of data:
Reply from 146.66.152.100: bytes=32 time=139ms TTL=51
Reply from 146.66.152.100: bytes=32 time=135ms TTL=51
Reply from 146.66.152.100: bytes=32 time=136ms TTL=51
Reply from 146.66.152.100: bytes=32 time=138ms TTL=51

Ping statistics for 146.66.152.100:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 135ms, Maximum = 139ms, Average = 137ms
 

Revil

Newbie
Oct 30, 2015
20
0
1
I mostly play Warface now. Used to play Paladins, BF1 and Warframe but got bored :p

Here are the stats:

*For Dubai:
Spoiler: show
Code:
Pinging 185.25.183.5 with 32 bytes of data:
Reply from 185.25.183.5: bytes=32 time=37ms TTL=52
Reply from 185.25.183.5: bytes=32 time=29ms TTL=52
Reply from 185.25.183.5: bytes=32 time=36ms TTL=52
Reply from 185.25.183.5: bytes=32 time=34ms TTL=52

Ping statistics for 185.25.183.5:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 29ms, Maximum = 37ms, Average = 34ms

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 

Pinging 185.25.183.50 with 32 bytes of data:
Reply from 185.25.183.50: bytes=32 time=30ms TTL=52
Reply from 185.25.183.50: bytes=32 time=35ms TTL=52
Reply from 185.25.183.50: bytes=32 time=35ms TTL=52
Reply from 185.25.183.50: bytes=32 time=31ms TTL=52

Ping statistics for 185.25.183.50:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 30ms, Maximum = 35ms, Average = 32ms
*For SEA:
Spoiler: show
Code:
Pinging 103.28.54.20 with 32 bytes of data:
Reply from 103.28.54.20: bytes=32 time=80ms TTL=52
Reply from 103.28.54.20: bytes=32 time=77ms TTL=52
Reply from 103.28.54.20: bytes=32 time=83ms TTL=52
Reply from 103.28.54.20: bytes=32 time=77ms TTL=52

Ping statistics for 103.28.54.20:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 77ms, Maximum = 83ms, Average = 79ms

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 

Pinging 103.28.54.65 with 32 bytes of data:
Reply from 103.28.54.65: bytes=32 time=77ms TTL=52
Reply from 103.28.54.65: bytes=32 time=77ms TTL=52
Reply from 103.28.54.65: bytes=32 time=78ms TTL=52
Reply from 103.28.54.65: bytes=32 time=83ms TTL=52

Ping statistics for 103.28.54.65:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 77ms, Maximum = 83ms, Average = 78ms
*For EU:
Spoiler: show
Code:
Pinging 146.66.155.6 with 32 bytes of data:
Reply from 146.66.155.6: bytes=32 time=144ms TTL=113
Reply from 146.66.155.6: bytes=32 time=143ms TTL=113
Reply from 146.66.155.6: bytes=32 time=142ms TTL=113
Reply from 146.66.155.6: bytes=32 time=145ms TTL=113

Ping statistics for 146.66.155.6:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 142ms, Maximum = 145ms, Average = 143ms
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 

Pinging 146.66.155.11 with 32 bytes of data:
Reply from 146.66.155.11: bytes=32 time=142ms TTL=113
Reply from 146.66.155.11: bytes=32 time=147ms TTL=113
Reply from 146.66.155.11: bytes=32 time=146ms TTL=113
Reply from 146.66.155.11: bytes=32 time=142ms TTL=113

Ping statistics for 146.66.155.11:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 142ms, Maximum = 147ms, Average = 144ms

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Pinging 146.66.152.50 with 32 bytes of data:
Reply from 146.66.152.50: bytes=32 time=135ms TTL=51
Reply from 146.66.152.50: bytes=32 time=137ms TTL=51
Reply from 146.66.152.50: bytes=32 time=136ms TTL=51
Reply from 146.66.152.50: bytes=32 time=135ms TTL=51

Ping statistics for 146.66.152.50:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 135ms, Maximum = 137ms, Average = 135ms

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Pinging 146.66.152.100 with 32 bytes of data:
Reply from 146.66.152.100: bytes=32 time=139ms TTL=51
Reply from 146.66.152.100: bytes=32 time=135ms TTL=51
Reply from 146.66.152.100: bytes=32 time=136ms TTL=51
Reply from 146.66.152.100: bytes=32 time=138ms TTL=51

Ping statistics for 146.66.152.100:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 135ms, Maximum = 139ms, Average = 137ms
Hey thanks a lot man. That is very impressive gonna call them up in the morning and have this installed at my place.
 

FuriousNinja

Intermediate
Jul 27, 2015
153
0
11
Karachi
Hey thanks a lot man. That is very impressive gonna call them up in the morning and have this installed at my place.
No problemo ^^

A word of caution though, if you can check pings at their office then do so because as I said before, it heavily depends on your dealer and the infrastructure they have in place. It is working like a wonder for some while others face high pings etc.
 

Revil

Newbie
Oct 30, 2015
20
0
1
No problemo ^^

A word of caution though, if you can check pings at their office then do so because as I said before, it heavily depends on your dealer and the infrastructure they have in place. It is working like a wonder for some while others face high pings etc.
Well I spoke to these guys about having a new connection installed a couple days ago and the dealer kept saying he will send a guy the next day for 3 straight days. If that's the quality of service im gonna get for even getting this connection installed id rather just avoid it.

In the future if im to face any issues with this service its gonna be far more annoying. Guess I'm stuck with PTCL. Gonna give them a call today and find out whether they have the new transformed packages in my location at malir cantt yet and just have that installed.
 

FuriousNinja

Intermediate
Jul 27, 2015
153
0
11
Karachi
Well I spoke to these guys about having a new connection installed a couple days ago and the dealer kept saying he will send a guy the next day for 3 straight days. If that's the quality of service im gonna get for even getting this connection installed id rather just avoid it.

In the future if im to face any issues with this service its gonna be far more annoying. Guess I'm stuck with PTCL. Gonna give them a call today and find out whether they have the new transformed packages in my location at malir cantt yet and just have that installed.
Yep as I said earlier, the reliability and technical expertise depend on your area dealer. Fortunately the one in our area is a good guy and no issues like you mentioned have ever occurred. This is the dilemma we Karachiites face. It is so effing big that not every ISP can cover it lol or else I would have opted for FTTH service like SF or FL.

What problems are/were you facing with PTCL?
 
General chit-chat
Help Users
We have disabled traderscore and are working on a fix. There was a bug with the plugin | Click for Discord
  • No one is chatting at the moment.
    C cattoboee: yo