[BC] High intermittent latency on telus

Author	All Replies
Waffler @telus.net	[BC] High intermittent latency on telus I live in Richmond and since 3 days ago have been getting intermittent latency spikes causing all connections to spike up to 1500 ms and typically resting between 300-1000 for up to hours at a time. It's completely random and I'm not really sure how to do anything about it. Is it possible it's telus? Entire household experiences the spike. I'm on an ethernet connection but I've ran pings on laptop right beside the router on wifi as well and it also experiences the high latency spikes. I've isolated my own desktop on the network and the spikes still happen. I've turned off the wifi and it still happens? Anyone able to help?
	to forum · permalink · 2013-04-05 23:25:24 ·

nss_tech join:2007-07-29 Edmonton AB	What router / gateway are you using? Is the latency affecting everything?
	to forum · permalink · 2013-04-06 01:09:41 ·
Tornado15550 Hello DSLR join:2012-12-16 Calgary, AB	reply to Waffler Everything's fine here, in Calgary. On Wireless:
	to forum · permalink · 2013-04-06 02:32:25 ·
Waffler @telus.net	reply to nss_tech VSG1432 Zyxel and if by gateway you mean ip then 192.168.1.254
	to forum · permalink · 2013-04-06 06:52:03 ·
Waffler @telus.net	reply to Tornado15550 Reply from 74.125.129.94: bytes=32 time=33ms TTL=50 Reply from 74.125.129.94: bytes=32 time=31ms TTL=50 Reply from 74.125.129.94: bytes=32 time=30ms TTL=50 Reply from 74.125.129.94: bytes=32 time=31ms TTL=50 Reply from 74.125.129.94: bytes=32 time=30ms TTL=50 Reply from 74.125.129.94: bytes=32 time=31ms TTL=50 Reply from 74.125.129.94: bytes=32 time=32ms TTL=50 Reply from 74.125.129.94: bytes=32 time=31ms TTL=50 Reply from 74.125.129.94: bytes=32 time=42ms TTL=50 Reply from 74.125.129.94: bytes=32 time=65ms TTL=50 Reply from 74.125.129.94: bytes=32 time=33ms TTL=50 Reply from 74.125.129.94: bytes=32 time=44ms TTL=50 Reply from 74.125.129.94: bytes=32 time=30ms TTL=50 Reply from 74.125.129.94: bytes=32 time=41ms TTL=50 Reply from 74.125.129.94: bytes=32 time=99ms TTL=50 Reply from 74.125.129.94: bytes=32 time=76ms TTL=50 Reply from 74.125.129.94: bytes=32 time=180ms TTL=50 Reply from 74.125.129.94: bytes=32 time=283ms TTL=50 Reply from 74.125.129.94: bytes=32 time=513ms TTL=50 Reply from 74.125.129.94: bytes=32 time=30ms TTL=50 Reply from 74.125.129.94: bytes=32 time=1903ms TTL=50 Reply from 74.125.129.94: bytes=32 time=443ms TTL=50 Reply from 74.125.129.94: bytes=32 time=31ms TTL=50 Reply from 74.125.129.94: bytes=32 time=34ms TTL=50 Reply from 74.125.129.94: bytes=32 time=33ms TTL=50 Reply from 74.125.129.94: bytes=32 time=37ms TTL=50 Reply from 74.125.129.94: bytes=32 time=30ms TTL=50 Reply from 74.125.129.94: bytes=32 time=30ms TTL=50 Reply from 74.125.129.94: bytes=32 time=35ms TTL=50 Reply from 74.125.129.94: bytes=32 time=34ms TTL=50 Reply from 74.125.129.94: bytes=32 time=48ms TTL=50 Reply from 74.125.129.94: bytes=32 time=30ms TTL=50 Reply from 74.125.129.94: bytes=32 time=35ms TTL=50 Reply from 74.125.129.94: bytes=32 time=30ms TTL=50 Reply from 74.125.129.94: bytes=32 time=30ms TTL=50 Reply from 74.125.129.94: bytes=32 time=30ms TTL=50 Reply from 74.125.129.94: bytes=32 time=30ms TTL=50 Reply from 74.125.129.94: bytes=32 time=37ms TTL=50 Reply from 74.125.129.94: bytes=32 time=46ms TTL=50 Reply from 74.125.129.94: bytes=32 time=30ms TTL=50 Reply from 74.125.129.94: bytes=32 time=34ms TTL=50 Reply from 74.125.129.94: bytes=32 time=29ms TTL=50 Reply from 74.125.129.94: bytes=32 time=31ms TTL=50 Reply from 74.125.129.94: bytes=32 time=38ms TTL=50 Reply from 74.125.129.94: bytes=32 time=31ms TTL=50 Reply from 74.125.129.94: bytes=32 time=30ms TTL=50 Reply from 74.125.129.94: bytes=32 time=39ms TTL=50 Reply from 74.125.129.94: bytes=32 time=43ms TTL=50 Ping statistics for 74.125.129.94: Packets: Sent = 203, Received = 203, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 29ms, Maximum = 1903ms, Average = 264ms Control-C ^C C:\Users\i72600k>tracert europa.eu Tracing route to europa.eu [147.67.136.2] over a maximum of 30 hops: 1 ping google.co.uk Pinging google.co.uk [74.125.129.94] with 32 bytes of data: Reply from 74.125.129.94: bytes=32 time=30ms TTL=50 Reply from 74.125.129.94: bytes=32 time=30ms TTL=50 Reply from 74.125.129.94: bytes=32 time=29ms TTL=50 Reply from 74.125.129.94: bytes=32 time=37ms TTL=50 Ping statistics for 74.125.129.94: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 29ms, Maximum = 37ms, Average = 31ms C:\Users\i72600k>tracert google.co.uk Tracing route to google.co.uk [74.125.129.94] over a maximum of 30 hops: 1 ping euw.leagueoflegends.com Pinging euw.leagueoflegends.com.cdn.cloudflare.net [190.93.246.13] with 32 bytes of data: Reply from 190.93.246.13: bytes=32 time=31ms TTL=57 Reply from 190.93.246.13: bytes=32 time=29ms TTL=57 Reply from 190.93.246.13: bytes=32 time=38ms TTL=57 Reply from 190.93.246.13: bytes=32 time=31ms TTL=57 Ping statistics for 190.93.246.13: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 29ms, Maximum = 38ms, Average = 32ms C:\Users\i72600k>ping leagueoflegends.co.kr Pinging leagueoflegends.co.kr [110.45.191.26] with 32 bytes of data: Request timed out. Request timed out. Request timed out. Ping statistics for 110.45.191.26: Packets: Sent = 3, Received = 0, Lost = 3 (100% loss), Control-C ^C C:\Users\i72600k>tracert euw.leagueoflegends.com Tracing route to euw.leagueoflegends.com.cdn.cloudflare.net [190.93.246.13] over a maximum of 30 hops: 1 tracert 206.116.74.41 Tracing route to d206-116-74-41.bchsia.telus.net [206.116.74.41] over a maximum of 30 hops: 1 1 ms 1 ms tracert 192.168.1.254 Tracing route to 192.168.1.254 over a maximum of 30 hops 1 C:\Users\i72600k>tracert 10.31.184.1 Tracing route to 10.31.184.1 over a maximum of 30 hops 1 tracert 70.79.228.87 Tracing route to S0106001d7e70a416.vc.shawcable.net [70.79.228.87] over a maximum of 30 hops: 1 11 ms tracert 182.211.169.65 Tracing route to 182.211.169.65 over a maximum of 30 hops 1 ping 182.211.169.65 Pinging 182.211.169.65 with 32 bytes of data: Reply from 182.211.169.65: bytes=32 time=195ms TTL=51 Reply from 182.211.169.65: bytes=32 time=180ms TTL=51 Reply from 182.211.169.65: bytes=32 time=196ms TTL=51 Reply from 182.211.169.65: bytes=32 time=184ms TTL=51 Ping statistics for 182.211.169.65: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 180ms, Maximum = 196ms, Average = 188ms C:\Users\i72600k>ping google.ca Pinging google.ca [74.125.129.94] with 32 bytes of data: Reply from 74.125.129.94: bytes=32 time=32ms TTL=50 Reply from 74.125.129.94: bytes=32 time=34ms TTL=50 Reply from 74.125.129.94: bytes=32 time=30ms TTL=50 Reply from 74.125.129.94: bytes=32 time=30ms TTL=50 Ping statistics for 74.125.129.94: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 30ms, Maximum = 34ms, Average = 31ms C:\Users\i72600k>ping google.ca Pinging google.ca [74.125.129.94] with 32 bytes of data: Reply from 74.125.129.94: bytes=32 time=46ms TTL=50 Reply from 74.125.129.94: bytes=32 time=30ms TTL=50 Reply from 74.125.129.94: bytes=32 time=60ms TTL=50 Reply from 74.125.129.94: bytes=32 time=51ms TTL=50 Ping statistics for 74.125.129.94: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 30ms, Maximum = 60ms, Average = 46ms C:\Users\i72600k>ping google.ca Pinging google.ca [74.125.129.94] with 32 bytes of data: Reply from 74.125.129.94: bytes=32 time=100ms TTL=50 Reply from 74.125.129.94: bytes=32 time=63ms TTL=50 Reply from 74.125.129.94: bytes=32 time=94ms TTL=50 Reply from 74.125.129.94: bytes=32 time=120ms TTL=50 Ping statistics for 74.125.129.94: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 63ms, Maximum = 120ms, Average = 94ms C:\Users\i72600k>ping google.ca Pinging google.ca [74.125.129.94] with 32 bytes of data: Reply from 74.125.129.94: bytes=32 time=103ms TTL=50 Reply from 74.125.129.94: bytes=32 time=47ms TTL=50 Reply from 74.125.129.94: bytes=32 time=33ms TTL=50 Reply from 74.125.129.94: bytes=32 time=31ms TTL=50 Ping statistics for 74.125.129.94: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 31ms, Maximum = 103ms, Average = 53ms C:\Users\i72600k>ping google.ca Pinging google.ca [74.125.129.94] with 32 bytes of data: Reply from 74.125.129.94: bytes=32 time=30ms TTL=50 Reply from 74.125.129.94: bytes=32 time=30ms TTL=50 Reply from 74.125.129.94: bytes=32 time=31ms TTL=50 Reply from 74.125.129.94: bytes=32 time=34ms TTL=50 Ping statistics for 74.125.129.94: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 30ms, Maximum = 34ms, Average = 31ms Thats some of the pings I did to google.ca
	to forum · permalink · 2013-04-06 06:52:11 ·
nss_tech join:2007-07-29 Edmonton AB	Well any IP halfway around the world could have any number of things causing spikes due to an increased number of devices in between. Google would be less likely if you are using the .ca server versus the .co.uk one. Ping tests don't tell the whole story though. Try doing a traceroute between you and the target IP a few times, to see if you can identify which device between you and the target is responsible.
	to forum · permalink · 2013-04-06 19:59:08 ·
pfak Premium join:2002-12-29 Vancouver, BC	reply to Waffler Sounds like you're saturating your internet connection, which is causing the high latency. Either due to P2P, downloading, or a virus. It's also possible that someone is using your WiFi. -- The more I C, the less I see.
	to forum · permalink · 2013-04-06 22:45:52 ·
Tornado15550 Hello DSLR join:2012-12-16 Calgary, AB	reply to nss_tech said by nss_tech: Well any IP halfway around the world could have any number of things causing spikes due to an increased number of devices in between. Google would be less likely if you are using the .ca server versus the .co.uk one. Ping tests don't tell the whole story though. Try doing a traceroute between you and the target IP a few times, to see if you can identify which device between you and the target is responsible. Exactly that^. Use a local domain for any site that you visit (if it has one), and you will get better performance.
	to forum · permalink · 2013-04-07 02:43:39 ·

O Canada! > Canadian > Telus > [BC] High intermittent latency on telus