dslreports logo
 
    All Forums Hot Topics Gallery
spc
Search similar:


uniqs
1910

Waffler
@telus.net

Waffler

Anon

[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?

nss_tech
join:2007-07-29
Edmonton AB

nss_tech

Member

What router / gateway are you using? Is the latency affecting everything?

Tornado15550
join:2012-12-16
Canada

Tornado15550 to Waffler

Member

to Waffler
Everything's fine here, in Calgary. On Wireless:


Waffler
@telus.net

Waffler to nss_tech

Anon

to nss_tech
VSG1432 Zyxel and if by gateway you mean ip then 192.168.1.254
Waffler

Waffler to Tornado15550

Anon

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

nss_tech
join:2007-07-29
Edmonton AB

nss_tech

Member

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.

pfak
Premium Member
join:2002-12-29
Vancouver, BC

pfak to Waffler

Premium Member

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.

Tornado15550
join:2012-12-16
Canada

Tornado15550 to nss_tech

Member

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.

asa
@telus.net

asa to Waffler

Anon

to Waffler
I've also been having intermittently high latency. I'm located in Vancouver, and set up a short program to regularly ping google.com. I set it to run when my entire house is asleep, and therefore not using the internet (I checked for torrents). The highest ping observed was 1777, and the pink spiked above 1690 no less than four times in one night (8hrs). In addition, the internet speed slows to almost a complete stop at times, usually taking more than a minute to rise back to acceptable speeds ("acceptable" defined as "small text files taking less than five seconds to load," so still not necessarily that good).

This is getting extremely frustrating, and latency spikes to a continuous 200-300 ping, which wreaks havoc with my gaming. I hope this added information may assist in at least drawing further attention to this problem.

nss_tech
join:2007-07-29
Edmonton AB

nss_tech

Member

@asa - No further information was provided. As I mentioned before, show the traceroute to the destination. Pinging means very little by itself. If your download speed is affected that dramatically you may have a very different issue than OP. Have you called into tech support yet?

Cdoster
@telus.net

Cdoster to Waffler

Anon

to Waffler
Hello;

I also live in Vancouver (downtown), and have been experienced huge latency spikes as well. I just switch to Telus 25 a month ago, and have the ALU Cellpipe modem (with modded firmware). Everything has been normal for a while (pings around 10-13 for speedtest.com). However recently (maybe 3 or 5 days ago), I been having crazy latency spikes (goes to around 300->800ms on speedtest.com). I thought it'd just go away after a while, but it's been like a week now. I thought maybe it was my ALU modem causing problems? Below are some 'tracert google.ca', which show it's random, and not a specific node in the route... All the tracert were done back to back.
It's not consistent, sometimes it goes back to 12ms ping, and stays like that for a few hours. Then back to crazy ping, and stays like that for a few hours. Does this mean it's my ALU modem? or something on telus's side?

C:\Users\Cody>ping google.ca -t
 
Pinging google.ca [74.125.141.94] with 32 bytes of data:
Reply from 74.125.141.94: bytes=32 time=17ms TTL=50
Reply from 74.125.141.94: bytes=32 time=144ms TTL=50
Reply from 74.125.141.94: bytes=32 time=155ms TTL=50
Reply from 74.125.141.94: bytes=32 time=17ms TTL=50
Reply from 74.125.141.94: bytes=32 time=169ms TTL=50
Reply from 74.125.141.94: bytes=32 time=190ms TTL=50
Reply from 74.125.141.94: bytes=32 time=18ms TTL=50
Reply from 74.125.141.94: bytes=32 time=17ms TTL=50
Reply from 74.125.141.94: bytes=32 time=157ms TTL=50
Reply from 74.125.141.94: bytes=32 time=17ms TTL=50
Reply from 74.125.141.94: bytes=32 time=17ms TTL=50
Reply from 74.125.141.94: bytes=32 time=29ms TTL=50
Reply from 74.125.141.94: bytes=32 time=157ms TTL=50
Reply from 74.125.141.94: bytes=32 time=29ms TTL=50
Reply from 74.125.141.94: bytes=32 time=41ms TTL=50
Reply from 74.125.141.94: bytes=32 time=69ms TTL=50
Reply from 74.125.141.94: bytes=32 time=100ms TTL=50
Reply from 74.125.141.94: bytes=32 time=130ms TTL=50
Reply from 74.125.141.94: bytes=32 time=41ms TTL=50
Reply from 74.125.141.94: bytes=32 time=17ms TTL=50
Reply from 74.125.141.94: bytes=32 time=122ms TTL=50
Reply from 74.125.141.94: bytes=32 time=17ms TTL=50
Reply from 74.125.141.94: bytes=32 time=17ms TTL=50
Reply from 74.125.141.94: bytes=32 time=115ms TTL=50
Reply from 74.125.141.94: bytes=32 time=118ms TTL=50
Reply from 74.125.141.94: bytes=32 time=17ms TTL=50
Reply from 74.125.141.94: bytes=32 time=17ms TTL=50
Reply from 74.125.141.94: bytes=32 time=375ms TTL=50
Reply from 74.125.141.94: bytes=32 time=17ms TTL=50
 
Ping statistics for 74.125.141.94:
    Packets: Sent = 29, Received = 29, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 17ms, Maximum = 375ms, Average = 80ms
 
C:\Users\Cody>tracert google.ca
 
Tracing route to google.ca [74.125.141.94]
over a maximum of 30 hops:
 
  1    10 ms    10 ms     9 ms  d207-81-112-254.bchsia.telus.net [207.81.112.254]
  2    18 ms     6 ms     7 ms  173.182.197.34
  3     9 ms     9 ms     9 ms  MTLXPQVVBR02.core.tac.net [204.225.245.137]
  4    10 ms    10 ms     9 ms  96.1.252.131
  5   291 ms   247 ms   129 ms  209.85.249.34
  6    10 ms     9 ms    10 ms  66.249.94.197
  7    17 ms    17 ms    34 ms  216.239.46.208
  8    17 ms    17 ms    17 ms  64.233.174.127
  9     *        *        *     Request timed out.
 10    98 ms   119 ms    30 ms  da-in-f94.1e100.net [74.125.141.94]
 
Trace complete.
 
C:\Users\Cody>tracert google.ca
 
Tracing route to google.ca [74.125.141.94]
over a maximum of 30 hops:
 
  1     7 ms     7 ms    28 ms  d207-81-112-254.bchsia.telus.net [207.81.112.254]
  2   122 ms   134 ms   131 ms  173.182.197.34
  3    51 ms    10 ms    10 ms  MTLXPQVVBR02.core.tac.net [204.225.245.137]
  4   276 ms   148 ms   280 ms  96.1.252.131
  5    10 ms    35 ms    10 ms  209.85.249.34
  6    32 ms    10 ms    57 ms  66.249.94.201
  7    19 ms    29 ms    21 ms  216.239.46.208
  8    17 ms    17 ms    19 ms  64.233.174.125
  9     *        *        *     Request timed out.
 10   187 ms   207 ms   157 ms  da-in-f94.1e100.net [74.125.141.94]
 
Trace complete.
 
C:\Users\Cody>tracert google.ca
 
Tracing route to google.ca [74.125.141.94]
over a maximum of 30 hops:
 
  1   111 ms    84 ms    80 ms  d207-81-112-254.bchsia.telus.net [207.81.112.254]
  2   130 ms   122 ms    91 ms  173.182.197.34
  3   499 ms   353 ms   474 ms  MTLXPQVVBR02.core.tac.net [204.225.245.137]
  4   254 ms   242 ms   216 ms  96.1.252.131
  5   461 ms   457 ms   428 ms  209.85.249.34
  6   286 ms   259 ms   288 ms  66.249.94.197
  7   407 ms   498 ms   410 ms  216.239.46.200
  8   553 ms   522 ms   582 ms  64.233.174.127
  9     *        *        *     Request timed out.
 10   691 ms   360 ms   533 ms  da-in-f94.1e100.net [74.125.141.94]
 
Trace complete.
 
C:\Users\Cody>tracert google.ca
 
Tracing route to google.ca [74.125.141.94]
over a maximum of 30 hops:
 
  1   431 ms   429 ms   434 ms  d207-81-112-254.bchsia.telus.net [207.81.112.254]
  2   411 ms   831 ms   808 ms  173.182.197.34
  3   816 ms   853 ms   527 ms  MTLXPQVVBR02.core.tac.net [204.225.245.137]
  4   534 ms   349 ms   236 ms  96.1.252.131
  5    42 ms    10 ms    10 ms  209.85.249.34
  6   243 ms   252 ms   354 ms  66.249.94.201
  7   243 ms   348 ms   450 ms  216.239.46.200
  8   194 ms   184 ms   221 ms  64.233.174.127
  9     *        *        *     Request timed out.
 10   818 ms   824 ms   808 ms  da-in-f94.1e100.net [74.125.141.94]
 
Trace complete.
 
C:\Users\Cody>tracert google.ca
 
Tracing route to google.ca [74.125.141.94]
over a maximum of 30 hops:
 
  1   699 ms   666 ms   683 ms  d207-81-112-254.bchsia.telus.net [207.81.112.254]
  2   705 ms   695 ms   808 ms  173.182.197.34
  3   704 ms   732 ms   733 ms  MTLXPQVVBR02.core.tac.net [204.225.245.137]
  4   766 ms   775 ms   749 ms  96.1.252.131
  5   704 ms   611 ms   987 ms  209.85.249.34
  6   883 ms   754 ms   892 ms  66.249.94.197
  7   801 ms   828 ms   819 ms  216.239.46.200
  8   892 ms  1080 ms  1253 ms  64.233.174.97
  9     *        *        *     Request timed out.
 10  1233 ms  1287 ms  1337 ms  da-in-f94.1e100.net [74.125.141.94]
 
Trace complete.
 
couttsj
join:2010-07-29
Vernon, BC

couttsj to Waffler

Member

to Waffler
A ping (or for that matter a tracert because it is based on a ping) is not a very good tool to use to check for latency. The reason is that routers place a low priority on ICMP (Internet Control Message Protocol) packets, meaning that they can easily be delayed. Having said that, they can however be useful if you understand the limitations and choose your target carefully. For example, if you suspect that some packets are being retransmitted on the DSL or WiFi part of the network, increase the packet size and ping a reliable server on the Telus network:
C:\>ping -n 20 -l 256 smtp.telus.net
Pinging smtp.svc.telus.net [199.185.220.249] with 256 bytes of data:
Ping statistics for 199.185.220.249:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 56ms, Maximum = 58ms, Average = 56ms

There should be zero dropped packets, and the difference between min & max should be no more than 4 ms.

nss_tech
join:2007-07-29
Edmonton AB

nss_tech to Cdoster

Member

to Cdoster
@Cdoster: The last couple traceroutes you did almost make it look like either something with your modem or the connection itself. Call in and have them run some tests. If you have lots of errors on the connection you could possibly result with this. Are you directly connected to the ALU or do you have a router? What speed is your connection supposed to be? 6mpbs? 15mbps?

The other thing I'm trying to figure out is why your traceroutes go through Montreal (hop 3) then Telus Mobility (Hop 4) before heading to Google. My traceroutes are quite different as I'm on Optik so I take a different path to Google without hitting Montreal.

Waffler
@telus.net

Waffler

Anon

It's been solved. A tech came over and apparently closed off unused phone jacks as well as replaced the router. I don't know why my traceroutes go to different places but it's been working better than it has so far this past week so I feel like maybe it's finally gone. Thanks for all trying to help.