dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
6246
share rss forum feed


Cartel
Premium
join:2006-09-13
Chilliwack, BC
kudos:2
Reviews:
·TekSavvy DSL
·Shaw
·TELUS

[BC] My games suck because of high ping, what can I do about it?

My games suck because of high ping, what can I do about it?
I fell I have horrible pings.
Can Telus do something about it?
thanks

5 103 ms 61 ms 61 ms ae0-90g.cr1.pao1.us.nlayer.net [69.22.153.18]
6 62 ms 74 ms 61 ms ae1-70g.cr1.sjc1.us.nlayer.net [69.22.143.165]
7 66 ms 64 ms 65 ms ae1-40g.ar2.sjc1.us.nlayer.net [69.22.143.118]
8 70 ms 71 ms 71 ms 69.174.121.141
9 62 ms 68 ms 71 ms 69.174.120.178
10 62 ms 71 ms 71 ms 69.174.120.185
11 66 ms 74 ms 63 ms 72.37.232.234
12 62 ms 62 ms 62 ms 69.147.236.82.rdns.ubiquityservers.com [69.147.2
36.82]

Trace complete.

C:\Windows\system32>tracert www.dslreports.com

Tracing route to www.dslreports.com [209.123.109.175]
over a maximum of 30 hops:

1 39 ms 37 ms 39 ms d207-216-16-254.bchsia.telus.net [207.216.16.254
]
2 40 ms 40 ms 44 ms 173.182.196.34
3 61 ms 61 ms 61 ms 75.154.217.78
4 * * * Request timed out.
5 62 ms 62 ms 61 ms ae0-90g.cr1.pao1.us.nlayer.net [69.22.153.18]
6 61 ms 61 ms 61 ms ae1-70g.cr1.sjc1.us.nlayer.net [69.22.143.165]
7 119 ms 119 ms 119 ms xe-1-2-1.cr1.ewr1.us.nlayer.net [69.22.142.138]

8 125 ms 125 ms 128 ms ae1-70g.ar2.ewr1.us.nlayer.net [69.31.94.118]
9 129 ms 127 ms 125 ms as8001.xe-3-0-6.ar2.ewr1.us.nlayer.net [69.31.95
.130]
10 119 ms 120 ms 120 ms 0.e1-4.tbr1.oct.nac.net [209.123.10.122]
11 125 ms 125 ms 124 ms vlan804.esd1.oct.nac.net [209.123.10.2]
12 124 ms 125 ms 125 ms www.dslreports.com [209.123.109.175]

Trace complete.

C:\Windows\system32>tracert 209.250.128.25

Tracing route to 209.250.128.25 over a maximum of 30 hops

1 38 ms 38 ms 38 ms d207-216-16-254.bchsia.telus.net [207.216.16.254
]
2 41 ms 40 ms 40 ms 173.182.196.33
3 43 ms 44 ms 43 ms 204.225.243.22
4 186 ms 208 ms 203 ms te7-4.ccr02.sea02.atlas.cogentco.com [154.54.10.
45]
5 43 ms 44 ms 43 ms te4-8.ccr02.sea01.atlas.cogentco.com [154.54.81.
113]
6 65 ms 64 ms 65 ms te0-7-0-10.ccr21.slc01.atlas.cogentco.com [154.5
4.81.61]
7 99 ms 95 ms * te7-2.ccr02.den01.atlas.cogentco.com [154.54.45.
46]
8 107 ms 106 ms 107 ms te0-4-0-3.ccr21.mci01.atlas.cogentco.com [154.54
.7.129]
9 101 ms 94 ms 94 ms te0-5-0-4.ccr22.ord01.atlas.cogentco.com [154.54
.45.150]
10 121 ms 121 ms 115 ms te0-3-0-6.ccr21.yyz02.atlas.cogentco.com [154.54
.28.2]
11 120 ms 121 ms 120 ms te4-1.mag02.yyz02.atlas.cogentco.com [154.54.40.
138]
12 116 ms 115 ms 117 ms 38.108.65.35
13 106 ms 105 ms 106 ms 68-68-0-81.applecreek.pathcom.com [68.68.0.81]
14 104 ms 106 ms 105 ms 209.250.128.25

Trace complete.

C:\Windows\system32>tracert 209.250.128.25

Tracing route to 209.250.128.25 over a maximum of 30 hops

1 38 ms 39 ms 39 ms d207-216-16-254.bchsia.telus.net [207.216.16.254
]
2 39 ms 41 ms 40 ms 173.182.196.33
3 43 ms 42 ms 43 ms 204.225.243.22
4 63 ms 371 ms 330 ms te7-4.ccr02.sea02.atlas.cogentco.com [154.54.10.
45]
5 178 ms 218 ms 220 ms te4-8.ccr02.sea01.atlas.cogentco.com [154.54.81.
113]
6 65 ms 64 ms 69 ms te0-7-0-10.ccr21.slc01.atlas.cogentco.com [154.5
4.81.61]
7 93 ms 95 ms 99 ms te8-1.ccr01.den01.atlas.cogentco.com [154.54.82.
218]
8 106 ms 106 ms 106 ms te0-4-0-2.ccr22.mci01.atlas.cogentco.com [154.54
.45.54]
9 100 ms 100 ms 94 ms te0-5-0-4.ccr22.ord01.atlas.cogentco.com [154.54
.45.150]
10 121 ms 117 ms 120 ms te0-2-0-2.ccr22.yyz02.atlas.cogentco.com [154.54
.27.254]
11 120 ms 122 ms 121 ms te7-1.mag02.yyz02.atlas.cogentco.com [154.54.40.
166]
12 116 ms 115 ms 115 ms 38.108.65.35
13 106 ms 107 ms 106 ms 68-68-0-81.applecreek.pathcom.com [68.68.0.81]
14 106 ms 105 ms 106 ms 209.250.128.25

Trace complete.

C:\Windows\system32>tracert dslreports.com

Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:

1 38 ms 39 ms 39 ms d207-216-16-254.bchsia.telus.net [207.216.16.254
]
2 41 ms 39 ms 39 ms 173.182.196.34
3 61 ms 61 ms 61 ms 75.154.217.78
4 * * * Request timed out.
5 62 ms 62 ms 61 ms ae0-90g.cr1.pao1.us.nlayer.net [69.22.153.18]
6 61 ms 61 ms 118 ms ae1-70g.cr1.sjc1.us.nlayer.net [69.22.143.165]
7 120 ms 119 ms 119 ms xe-1-2-1.cr1.ewr1.us.nlayer.net [69.22.142.138]

8 126 ms 124 ms 125 ms ae1-70g.ar2.ewr1.us.nlayer.net [69.31.94.118]
9 126 ms 126 ms 125 ms as8001.xe-3-0-6.ar2.ewr1.us.nlayer.net [69.31.95
.130]
10 120 ms 121 ms 120 ms 0.e1-4.tbr1.oct.nac.net [209.123.10.122]
11 125 ms 125 ms 132 ms vlan804.esd1.oct.nac.net [209.123.10.2]
12 124 ms 125 ms 124 ms www.dslreports.com [209.123.109.175]

Trace complete.

C:\Windows\system32>tracert 69.12.104.204

Tracing route to 69.12.104.204 over a maximum of 30 hops

1 39 ms 39 ms 37 ms d207-216-16-254.bchsia.telus.net [207.216.16.254
]
2 39 ms 40 ms 40 ms 173.182.197.33
3 42 ms 42 ms 42 ms 204.225.243.18
4 130 ms 128 ms 132 ms sea-b1-link.telia.net [80.239.128.217]
5 61 ms 61 ms 61 ms level3-ic-151366-sea-b1.c.telia.net [80.239.128.
198]
6 66 ms 61 ms 63 ms ae-31-51.ebr1.Seattle1.Level3.net [4.69.147.150]

7 61 ms 60 ms 61 ms ae-7-7.ebr2.SanJose1.Level3.net [4.69.132.49]
8 60 ms 65 ms 61 ms ae-72-72.csw2.SanJose1.Level3.net [4.69.153.22]

9 62 ms 61 ms 61 ms ae-22-70.car2.SanJose1.Level3.net [4.69.152.68]

10 60 ms 61 ms 61 ms ge2-2.bbsr1.sjc.megapath.net [63.209.21.234]
11 86 ms 85 ms 85 ms ge-0-1-3-0.snvacaid-mxc2.bb.megapath.net [155.22
9.57.198]
12 61 ms 61 ms 61 ms ae0-0.snvacaid-mxc1.bb.megapath.net [155.229.57.
13]
13 85 ms 85 ms 84 ms ae2-0.sttlwawb-mxc1.bb.megapath.net [155.229.101
.93]
14 87 ms 85 ms 85 ms ge3-0-0.m10.stl.bb.megapath.net [155.229.101.189
]
15 85 ms 85 ms 87 ms 155.229.120.186
16 63 ms 63 ms 63 ms ve191.ge0-1-0.core1.lax.megapath.net [66.80.133.
18]
17 63 ms 64 ms 64 ms 69.12.104.204

Trace complete.

C:\Windows\system32>
C:\Windows\system32>tracert 69.12.104.204

Tracing route to 69.12.104.204 over a maximum of 30 hops

1 39 ms 39 ms 39 ms d207-216-16-254.bchsia.telus.net [207.216.16.254
]
2 39 ms 40 ms 40 ms 173.182.197.33
3 43 ms 43 ms 42 ms VANCBC01GR01.bb.telus.com [154.11.10.10]
4 116 ms 178 ms 118 ms sea-b1-link.telia.net [80.239.128.217]
5 60 ms 62 ms 60 ms level3-ic-151366-sea-b1.c.telia.net [80.239.128.
198]
6 64 ms 60 ms 63 ms ae-31-51.ebr1.Seattle1.Level3.net [4.69.147.150]

7 69 ms 61 ms 62 ms ae-7-7.ebr2.SanJose1.Level3.net [4.69.132.49]
8 66 ms 60 ms 63 ms ae-82-82.csw3.SanJose1.Level3.net [4.69.153.26]

9 64 ms 62 ms 61 ms ae-32-80.car2.SanJose1.Level3.net [4.69.152.132]

10 61 ms 61 ms 61 ms ge2-2.bbsr1.sjc.megapath.net [63.209.21.234]
11 85 ms 88 ms 85 ms ge-0-1-3-0.snvacaid-mxc2.bb.megapath.net [155.22
9.57.198]
12 61 ms 61 ms 61 ms ae0-0.snvacaid-mxc1.bb.megapath.net [155.229.57.
13]
13 86 ms 86 ms 85 ms ae2-0.sttlwawb-mxc1.bb.megapath.net [155.229.101
.93]
14 85 ms 99 ms 102 ms ge3-0-0.m10.stl.bb.megapath.net [155.229.101.189
]
15 85 ms 85 ms 86 ms 155.229.120.186
16 63 ms 63 ms 64 ms ve191.ge0-1-0.core1.lax.megapath.net [66.80.133.
18]
17 63 ms 64 ms 63 ms 69.12.104.204

Trace complete.

C:\Windows\system32>tracert google.com

Tracing route to google.com [74.125.225.70]
over a maximum of 30 hops:

1 39 ms 39 ms 38 ms d207-216-16-254.bchsia.telus.net [207.216.16.254
]
2 51 ms 39 ms 44 ms 173.182.197.34
3 43 ms 43 ms 42 ms 75.154.216.254
4 * * * Request timed out.
5 43 ms 44 ms 43 ms 209.85.249.32
6 43 ms 43 ms 43 ms 66.249.94.199
7 90 ms 91 ms 91 ms 216.239.46.158
8 104 ms 103 ms 103 ms 216.239.46.55
9 103 ms 103 ms 103 ms 72.14.232.140
10 91 ms 90 ms 91 ms 72.14.237.111
11 91 ms 91 ms 91 ms 209.85.250.30
12 103 ms 103 ms 103 ms ord08s07-in-f6.1e100.net [74.125.225.70]

Trace complete.

C:\Windows\system32>tracert 74.125.127.147

Tracing route to pz-in-f147.1e100.net [74.125.127.147]
over a maximum of 30 hops:

1 39 ms 41 ms 37 ms d207-216-16-254.bchsia.telus.net [207.216.16.254
]
2 40 ms 41 ms 39 ms 173.182.196.34
3 43 ms 43 ms 42 ms 75.154.216.254
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
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 * * * 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 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

C:\Windows\system32>tracert 74.125.127.147

Tracing route to pz-in-f147.1e100.net [74.125.127.147]
over a maximum of 30 hops:

1 38 ms 38 ms 39 ms d207-216-16-254.bchsia.telus.net [207.216.16.254
]
2 47 ms 40 ms 40 ms 173.182.196.34
3 43 ms 67 ms 42 ms 75.154.216.254
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * ^C
C:\Windows\system32>tracert 74.125.127.147

Tracing route to pz-in-f147.1e100.net [74.125.127.147]
over a maximum of 30 hops:

1 38 ms 39 ms 39 ms d207-216-16-254.bchsia.telus.net [207.216.16.254
]
2 41 ms 40 ms 40 ms 173.182.196.34
3 43 ms 42 ms 44 ms 75.154.216.254
^C
C:\Windows\system32>tracert yahoo.com

Tracing route to yahoo.com [98.139.183.24]
over a maximum of 30 hops:

1 38 ms 39 ms 38 ms d207-216-16-254.bchsia.telus.net [207.216.16.254
]
2 40 ms 42 ms 40 ms 173.182.197.33
3 43 ms 43 ms 43 ms VANCBC01GR01.bb.telus.com [154.11.10.10]
4 42 ms 43 ms 43 ms 173.182.200.62
5 56 ms 47 ms 48 ms ae-7.pat2.gqb.yahoo.com [216.115.101.109]
6 76 ms 73 ms 79 ms ae-7.pat1.dnx.yahoo.com [216.115.96.205]
7 121 ms 112 ms 113 ms ae-3.pat1.che.yahoo.com [216.115.96.35]
8 118 ms 121 ms 118 ms ge-3-1-8-p191.pat1.nyc.yahoo.com [216.115.96.119
]
9 137 ms 122 ms 184 ms ge-1-0-0.pat2.bfz.yahoo.com [216.115.97.207]
10 127 ms 121 ms 121 ms ae-4.msr2.bf1.yahoo.com [216.115.100.73]
11 119 ms 118 ms 163 ms xe-4-0-0.clr2-a-gdc.bf1.yahoo.com [98.139.232.83
]
12 124 ms 118 ms 127 ms et-18-25.fab3-1-gdc.bf1.yahoo.com [98.139.128.57
]
13 137 ms 138 ms 119 ms po-11.bas1-7-prd.bf1.yahoo.com [98.139.129.177]

14 146 ms 152 ms 138 ms ir2.fp.vip.bf1.yahoo.com [98.139.183.24]

Trace complete.

C:\Windows\system32>


TierX

join:2009-01-20
Canada
kudos:8

Re: [BC] My games suck because of high ping, what can I do about

said by Cartel:

My games suck because of high ping, what can I do about it?
I fell I have horrible pings.
Can Telus do something about it?
thanks

Call the help desk and have them engage Tier 2, there are sets of profiles intended for low latency, while still providing at least INP=2. If they give you the run around, private message me your number, and I can put you on these profiles.

Mike_C

join:2007-07-19
Vancouver, BC
reply to Cartel

Well if you are in Chilliwack so that's one strike against you there. Worse if you're in Yarrow. I'm surprised you haven't bothered to read any of the dozens of other topics about pings / routing.

Post the IPs to the game servers and the city the server is in and what ping you get while PLAYING ON THEM specifically. Traceroute / Pinging to them isn't the best way to gauge the response times. Also pinging websites (google, DSLR, yahoo) isn't even accurate as you can get a random IP (google for sure) depending on the number of servers they have or if they are cloud based. DSLR is slow regardless.

Out of the IPs you listed I only identified one as a game server. 69.12.104.204 is supposed to be Seattle yet it the traceroute hits Seattle then Los Angeles and San Jose, CA before back to Seattle and that server. That is megapath and they are one of the worst. If any of your traceroutes that have megapath listed, don't complain about because those cannot be fixed.

74.125.127.147: That's Google in California. Not a game server.

Oh and if you are still using that Dlink 300G, call to get it replaced with a Speedtouch then try playing your games again.



Cartel
Premium
join:2006-09-13
Chilliwack, BC
kudos:2
Reviews:
·TekSavvy DSL
·Shaw
·TELUS
reply to Cartel

Click for full size
I'm running the 516V6 so TierX can profile it for me.

Here's what I got on the screenshot

Mike_C

join:2007-07-19
Vancouver, BC

I'm not familiar with the Speedtouch having a 192.168.1.254 IP address.


TierX

join:2009-01-20
Canada
kudos:8
reply to Mike_C

said by Mike_C:

Well if you are in Chilliwack so that's one strike against you there. Worse if you're in Yarrow. I'm surprised you haven't bothered to read any of the dozens of other topics about pings / routing.

Given the latency to the first hop, he's clearly on a profile with high interleaving delay (likely INP=2 w/ 16ms up+down), and not using a modem capable of physical layer retransmission. The Speedtouch 516v6 will only be marginally better than a 300G, and only if he installs the 7.x firmware (adds ADSL2+ Amendment 3 support, which adds additional interleaver memory).

TheMG
Premium
join:2007-09-04
Canada
kudos:3
Reviews:
·NorthWest Tel
reply to Mike_C

said by Mike_C:

I'm not familiar with the Speedtouch having a 192.168.1.254 IP address.

The SpeedTouch 516 has two default IP addresses:

192.168.1.254
10.0.0.138


Cartel
Premium
join:2006-09-13
Chilliwack, BC
kudos:2
reply to Cartel

OK I'm on the V1000H, is that better?
It is set to multi mode and is on ADSL2+ right now.



Cartel
Premium
join:2006-09-13
Chilliwack, BC
kudos:2
Reviews:
·TekSavvy DSL
·Shaw
·TELUS
reply to Cartel

Click for full size
Here's how it looks on the v1000h


Cartel
Premium
join:2006-09-13
Chilliwack, BC
kudos:2
Reviews:
·TekSavvy DSL
·Shaw
·TELUS
reply to Cartel




Cartel
Premium
join:2006-09-13
Chilliwack, BC
kudos:2
reply to Cartel

still no change



DKS
Damn Kidney Stones
Premium,ExMod 2002
join:2001-03-22
Owen Sound, ON
kudos:2

said by Cartel:

still no change

Not sure why you think these are high pings. Gaming is possible at less that 80ms and even 150ms. What causes you to make that conclusion?
--
Need-based health care not greed-based health care.


Cartel
Premium
join:2006-09-13
Chilliwack, BC
kudos:2
reply to Cartel

I could throw a popsicle stick in the river and it would float to Burnaby faster than that!

...no seriously, I think the ping is high.



nss_tech

join:2007-07-29
Edmonton AB

Can you post some screenshots from your games that show your ping while playing?



DKS
Damn Kidney Stones
Premium,ExMod 2002
join:2001-03-22
Owen Sound, ON
kudos:2
reply to Cartel

said by Cartel:

I could throw a popsicle stick in the river and it would float to Burnaby faster than that!

...no seriously, I think the ping is high.

Any ping under 100-150ms is fine for gaming. Your problem is elsewhere. Look at the peering at Cogentco in Seattle. Several of those routings, but not all you posted, hit 300ms at that point, which isn't bad, but may be what you are seeing.

quote:
4 63 ms 371 ms 330 ms te7-4.ccr02.sea02.atlas.cogentco.com
That means to the problem is probably out of your hands and there is absolutely nothing you can do about it on your end.
--
Need-based health care not greed-based health care.


siberx4
Bandwidth hog

join:2004-10-19
West Vancouver, BC
reply to Cartel

Switching your interleaving profile will definitely help some as TierX mentioned (37ms+ is pretty high for first-hop, 7-12ms is very achievable in most cases), but you'll need to make sure your hardware supports the latest profiles . Speedtouch with old firmware definitely does not (you can try 7.4.3.2 or 7.4.4.7, the latter of which can be a bit finnicky with configuration settings due to its european source though), v1000h is probably better but I don't have any experience with it myself, especially on an ADSL2+ line.

For the rest, your pings are decent, but not excellent - if you can find a good VPN provider located *very* near you (same city if possible) you may find you can get lower pings by tunneling through them if their peering is better (telus makes no guarantees about their peering arrangements, and they're notoriously poor). You won't know for sure until you try though, so don't sign up for a 2 year subscription before you've tested it.
--
We are not retreating.
We are merely advancing in another direction.
-Douglas MacArthur



Cartel
Premium
join:2006-09-13
Chilliwack, BC
kudos:2

I bridged the v1000h and I'm waiting for some new profile.
I guess tierx is pretty busy.
I still have the 516 updated to 7.4.4.7.


Listening74

join:2012-10-18
v6e-1k2
reply to Cartel

I have TELUS Optik package and online games such as Halo Reach and halo 4 are a hit and miss caused by high ping times. My minimum ping to my first hop is no less than 69ms and as high as 200ms. I live in Vancouver downtown and when I try to do video calls to UBC also a hit miss caused by high ping times. I do a trace route to UBC and get no less than 29 hops and hop times as high as 380ms. I would not recommend TELUS to anyone who likes online gaming or talking to friends using video messaging. According to TELUS as long as you have a connection that's all that matters to them, they don't care about latency problems. That is what they told me.



DKS
Damn Kidney Stones
Premium,ExMod 2002
join:2001-03-22
Owen Sound, ON
kudos:2

said by Listening74:

I have TELUS Optik package and online games such as Halo Reach and halo 4 are a hit and miss caused by high ping times. My minimum ping to my first hop is no less than 69ms and as high as 200ms. I live in Vancouver downtown and when I try to do video calls to UBC also a hit miss caused by high ping times. I do a trace route to UBC and get no less than 29 hops and hop times as high as 380ms. I would not recommend TELUS to anyone who likes online gaming or talking to friends using video messaging. According to TELUS as long as you have a connection that's all that matters to them, they don't care about latency problems. That is what they told me.

That is always how ISP's have responded to questions of high ping. It was that way a dozen years ago. Nothing has changed. Part of the problem is the customer's refusal to recognize that their ISP has no control of the network once it leaves their system. If the routing is bad at a peering node or down the line, there is absolutely nothing that the ISP can do about it, much less the individual consumer. For any ISP is indeed all about the connection. Anything more is completely beyond their control.
--
Need-based health care not greed-based health care.

Listening74

join:2012-10-18
v6e-1k2

What a load of rubbish...With TELUS it is the technology they use, (Interleaved). Before moving to TELUS we had Shaw and online gaming was far better so was Video messenger to Britain, Australia, etc. Moved to TELUS because we were told by TELUS reps that their lower latency, ping times would be even better for online gaming and such. But only after the fact do we find out that TELUS uses Interleaved error correction technology which greatly increases latency making it not so good for online gaming.



DKS
Damn Kidney Stones
Premium,ExMod 2002
join:2001-03-22
Owen Sound, ON
kudos:2

said by Listening74:

What a load of rubbish...With TELUS it is the technology they use, (Interleaved). Before moving to TELUS we had Shaw and online gaming was far better so was Video messenger to Britain, Australia, etc. Moved to TELUS because we were told by TELUS reps that their lower latency, ping times would be even better for online gaming and such. But only after the fact do we find out that TELUS uses Interleaved error correction technology which greatly increases latency making it not so good for online gaming.

Interleaved has always been slower for gaming. And ISPs are loathe to change it.
--
Need-based health care not greed-based health care.


pfak
Premium
join:2002-12-29
Vancouver, BC
reply to Listening74

said by Listening74:

What a load of rubbish...With TELUS it is the technology they use, (Interleaved).

There's no such thing as Interleaved vs. Fastpath on TELUS's new footprint, and TELUS has always supported both modes. There's various levels of impulse noise protection that reflect a latency increase.

There is technology deployed that tries to give you a balance between latency and speed now on TELUS's network. Most users don't care about latency if it's <40ms. The people on this board, and gamers are a very small portion of TELUS subscribers.

Most people would like stable Internet, and not lose sync especially when they have TELUS TV.
--
The more I C, the less I see.


spock

join:2012-07-08
Reviews:
·TekSavvy DSL
reply to Cartel

Interleave doesn't suck if you have a low delay. I had the same low pings on telus too. I had to call in a few times to get it changed mind you. It really depends who you get for tech support. I used to ping 40ms to my first hop. Tech support told me it was ok. It wasn't ok with me. Shaw isn't much better. Shaw is terrible if you are a serious gamer. Pings were are all over the place when I had them.

Tracing route to vancouver.speedtest.telus.com [207.102.78.141]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.30.1
2 9 ms 9 ms 9 ms erx01.van.teksavvy.com [76.10.191.6]
3 9 ms 8 ms 9 ms 76-10-191-28.dsl.teksavvy.com [76.10.191.28]
4 9 ms 9 ms 9 ms provinceofbc-van-gw.peer1.net [64.69.85.73]
5 10 ms 9 ms 9 ms 204.239.129.214
6 23 ms 20 ms 14 ms 173.182.212.147
7 14 ms 13 ms 14 ms 207.102.78.141



Cartel
Premium
join:2006-09-13
Chilliwack, BC
kudos:2
Reviews:
·TekSavvy DSL
·Shaw
·TELUS

Tracing route to vancouver.speedtest.telus.com [207.102.78.141]
over a maximum of 30 hops:

1 25 ms 25 ms 24 ms d207-216-16-254.bchsia.telus.net [207.216.16.254]
2 26 ms 26 ms 26 ms 173.182.196.33
3 29 ms 28 ms 28 ms 173.182.212.147
4 27 ms 26 ms 27 ms 207.102.78.141

Trace complete.



DKS
Damn Kidney Stones
Premium,ExMod 2002
join:2001-03-22
Owen Sound, ON
kudos:2

said by Cartel:

Tracing route to vancouver.speedtest.telus.com [207.102.78.141]
over a maximum of 30 hops:

1 25 ms 25 ms 24 ms d207-216-16-254.bchsia.telus.net [207.216.16.254]
2 26 ms 26 ms 26 ms 173.182.196.33
3 29 ms 28 ms 28 ms 173.182.212.147
4 27 ms 26 ms 27 ms 207.102.78.141

Trace complete.

Internal to telus.net and not bad. You will get increased latency (higher ping) when you move out into the real world. In the real world of gaming, latency of less than 100 ms isn't going to hurt you. Lag can be introduced at any point between you and the host, causing problems.
--
Need-based health care not greed-based health care.


spock

join:2012-07-08
Reviews:
·TekSavvy DSL

TierX said you are on a higher delay profile. Those pings would support his assumption.

Just to put things into context

"A millisecond is one thousandth of a second. Light can travel about 300km in a millisecond. Blinking usually takes between 300 and 400 milliseconds."

»wiki.answers.com/Q/How_long_is_1_millisecond



Cartel
Premium
join:2006-09-13
Chilliwack, BC
kudos:2
reply to Cartel

still waiting for this profile



Cartel
Premium
join:2006-09-13
Chilliwack, BC
kudos:2

3 edits

I have a pots splitter in the wall here would that make a difference?

Maybe it should be mounted in the utility room?

Maybe I need a seperate line for the DSL?

I'm also only 450M from the phone building



Anonymud

@shawcable.net

Thanks for the update! Let me know when you get to week 4~



Cartel
Premium
join:2006-09-13
Chilliwack, BC
kudos:2
Reviews:
·TekSavvy DSL
·Shaw
·TELUS
reply to Cartel

Let this be a waring for someone considering Telus.
People want me to post screen-shots of my ping in games?

Just fix it already.

People on here asking for your telephone number to help but do nothing and I wonder if they are even real employees.