anthonee1230
join:2009-04-08
Richmond, BC
3 edits | reply to anthonee1230
Re: Telus high ping between 730 and 1130PM?
[^ It's not you. Don't waste your time waiting around for techs to come in and reboot, replace, check your lines, whatever they plan on doing because it's not you. It's Telus.]
What I'm TRYING to do is show him (them?) evidence that this is a problem on THEIR end, and NOT mine.
Just out of curiosity, is anyone else using Telus TV besides me? Maybe this routing or routing overload issue is only related to those with Telus TV? |
|
netwerk007
join:2009-08-09 | Yes |
|
netwerk007
join:2009-08-09
 ·TekSavvy Solutions..
 ·Shaw
·TELUS
| reply to anthonee1230
Just out of curiosity what do you get when you traceroute www.msn.com ?
traceroute www.msn.com
traceroute to us.port.msn.com.nsatc.net (65.55.17.26), 64 hops max, 52 byte packets
1 10.0.1.1 (10.0.1.1) 2.192 ms 2.164 ms 3.649 ms
2 dxxx.xxx.xxx.xxx.bchsia.telus.net (xxx.xxx.xxx.xxx) 41.682 ms 12.263 ms 14.091 ms
3 154.11.89.129 (154.11.89.129) 17.727 ms 16.341 ms 16.001 ms
4 154.11.10.230 (154.11.10.230) 19.902 ms 19.421 ms 21.787 ms
5 microsoft.sttlwa01gr02.bb.telus.com (154.11.3.54) 19.926 ms 20.080 ms 20.595 ms
6 ge-1-3-0-56.wst-64cb-1a.ntwk.msn.net (207.46.46.37) 18.159 ms 19.440 ms 24.073 ms
7 ge-0-1-0-0.co1-64c-1a.ntwk.msn.net (207.46.43.162) 23.856 ms 22.834 ms 23.199 ms
8 ge-0-0-0-0.co1-64c-1b.ntwk.msn.net (207.46.43.161) 29.491 ms 25.033 ms 24.024 ms |
|
anthonee1230
join:2009-04-08
Richmond, BC
| reply to anthonee1230
Tracing route to us.port.msn.com.nsatc.net [65.55.17.26]
over a maximum of 30 hops:
1 35 ms 34 ms 36 ms 10.239.208.1
2 35 ms 34 ms 36 ms 208.181.242.70
3 35 ms 35 ms 35 ms 209.121.3.66
4 116 ms 117 ms 117 ms 154.11.10.161
5 136 ms 125 ms 124 ms 154.11.10.230
6 126 ms 127 ms 127 ms Microsoft.sttlwa01gr02.bb.telus.com [154.11.3.54
]
7 124 ms 144 ms 124 ms ge-1-3-0-57.wst-64cb-1b.ntwk.msn.net [207.46.46.
39]
8 125 ms 126 ms 126 ms ge-0-0-0-0.wst-64cb-1a.ntwk.msn.net [207.46.47.7
4]
9 125 ms 126 ms 125 ms ge-5-0-0-0.co1-64c-1a.ntwk.msn.net [207.46.43.16
8]
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 *
Trace route is still going, but pretty much everything after the 10th hop is a time out. |
|
Nitroxide
join:2009-06-05
| reply to netwerk007
Yeah I said it earlier in this thread but good luck getting Telus to admit anything. It's like pulling teeth. I hope they fix it soon whatever their problem is. |
|
anthonee1230
join:2009-04-08
Richmond, BC
| reply to anthonee1230
Tracing route to us.port.msn.com.nsatc.net [65.55.17.26]
over a maximum of 30 hops:
1 35 ms 34 ms 34 ms 10.239.208.1
2 35 ms 34 ms 33 ms 208.181.242.70
3 35 ms 34 ms 50 ms 209.121.3.66
4 47 ms 49 ms 47 ms 154.11.10.161
5 45 ms 46 ms 47 ms 154.11.10.230
6 41 ms 41 ms 44 ms Microsoft.sttlwa01gr02.bb.telus.com [154.11.3.54
]
7 42 ms 50 ms 44 ms ge-1-3-0-57.wst-64cb-1b.ntwk.msn.net [207.46.46.
39]
8 45 ms 43 ms 45 ms ge-0-0-0-0.wst-64cb-1a.ntwk.msn.net [207.46.47.7
4]
9 56 ms 57 ms 55 ms ge-5-0-0-0.co1-64c-1a.ntwk.msn.net [207.46.43.16
8]
10 * * * Request timed out.
11 *
This also happens to be around the time when my latency will start going down......
Notice the pings after the third hop.
I sure hope they fix this soon. |
|
roscoojam
join:2007-07-23
| reply to anthonee1230
anthonee1230
im out in ladner (next to richmond) and em having exact same issue as you...even run same tests right after your posts,and get pretty close to your readings....
phoning telus is useless...we can only hope they clear things up...
ps: i don't buy that oct colder thing,or that more people are online thing at all...as can always put in diff dns server numbers and that doesn't help solve are issues... |
|
randomguy
@telus.net
| Who said anything about DNS?
This is my capture from last night from around 7pm. latency in the middle hops gets higher but still the pings to dslreports.com were stable aside from the random loss (none of the hops in between also experienced packetloss at that big red section where there was loss to dslreports.. so that indicates the drops were at the far end)
So yeah.. these results don't give much to go on. but I'm taking the same path as you guys in ladner and richmond. |
|
Nitroxide
join:2009-06-05
1 edit | reply to anthonee1230
All it took was 3 pages and 10 traceroute logs? 
PS problem still happening tonight.. |
|
randomguy
@telus.net
| said by Nitroxide  :All it took was 3 pages and 10 traceroute logs? PS problem still happening tonight.. Not sure what you're getting at?
Tonight to dslreports the ping/trace looks the same. yeah some middle hops have an average response time of 180-200ms but the packets destined for dslreports.com are still near 110ms.
It's the destination response time thats the most important.. the middle hops can all be 400ms response -- as long as the reply from the end device is normal. (EI between 8pm and 11pm in my previous graph.. the 2nd graph where the response time goes up to 180-200ms, but the reponse from dslreports is still the same 100-120ms.) |
|
netwerk007
join:2009-08-09
·TekSavvy Solutions..
·Shaw
·TELUS
1 edit | said by randomguy :said by Nitroxide :All it took was 3 pages and 10 traceroute logs? PS problem still happening tonight.. Not sure what you're getting at? Tonight to dslreports the ping/trace looks the same. yeah some middle hops have an average response time of 180-200ms but the packets destined for dslreports.com are still near 110ms. It's the destination response time thats the most important.. the middle hops can all be 400ms response -- as long as the reply from the end device is normal. (EI between 8pm and 11pm in my previous graph.. the 2nd graph where the response time goes up to 180-200ms, but the reponse from dslreports is still the same 100-120ms.) That doesn't make sense. The destination ping time will be how long it takes to get to the far point and back to you. It will be the longest and biggest ping. If you see a very high ping mid route in a traceroute that is where the problem may be. All pings past this problem spot will be higher. You also have to look at averages as well to pin point the exact spot because the delay will change from traceroute to traceroute.
So if the high ping is in the middle the far end will also be high. |
|
anthonee1230
join:2009-04-08
Richmond, BC
| reply to anthonee1230
Here it is AGAIN....
Tracing route to www.dslreports.com [209.123.109.175]
over a maximum of 30 hops:
1 36 ms 34 ms 36 ms 10.239.208.1
2 34 ms 34 ms 35 ms 208.181.242.66
3 34 ms 35 ms 34 ms 209.121.3.14
4 128 ms 172 ms 130 ms 154.11.10.161
5 170 ms 197 ms 162 ms chcgildtgr00.bb.telus.com [154.11.11.34]
6 170 ms 171 ms 228 ms peer.chcgildtgr00.bb.telus.com [154.11.2.126]
7 205 ms 198 ms 272 ms nyk-bb1-link.telia.net [80.91.249.109]
8 198 ms 203 ms 196 ms nyk-b3-link.telia.net [80.91.250.93]
9 188 ms 223 ms 244 ms netaccess-tic-133837-nyk-b3.c.telia.net [213.248
.99.90]
10 203 ms 199 ms 203 ms 0.e1-1.tbr1.ewr.nac.net [209.123.10.129]
11 201 ms 211 ms 204 ms 0.e1-4.tbr1.oct.nac.net [209.123.10.122]
12 206 ms 198 ms 201 ms vlan804.esd1.oct.nac.net [209.123.10.2]
13 201 ms 199 ms 192 ms www.dslreports.com [209.123.109.175]
How is 34ms to 192ms not an indication of a problem....
Or how about this...
Tracing route to cityweb.telus.net [198.161.157.214]
over a maximum of 30 hops:
1 35 ms 34 ms 61 ms 10.239.208.1
2 49 ms 36 ms 34 ms 208.181.242.70
3 33 ms 34 ms 35 ms 209.121.3.70
4 76 ms 46 ms 45 ms 154.11.10.165
5 149 ms 256 ms 192 ms edtnabxmdr00.bb.telus.com [205.233.111.99]
6 167 ms 184 ms 143 ms host198.77.34.207.in-addr.arpa [207.34.77.198]
7 148 ms 164 ms 146 ms edtort21-v202.agt.net [161.184.255.251]
8 177 ms 191 ms 146 ms cityweb.telus.net [198.161.157.214]
Trace complete.
60ms to 146ms on Telus' own website? |
|
roscoojam
join:2007-07-23 | reply to anthonee1230
do you also notice web page loads not as fast?...i do |
|
anthonee1230
join:2009-04-08
Richmond, BC
| reply to anthonee1230
Spoke to another CSR today that is MUCH more helpful.
Said the first thing tech is going to do is check modem (im pretty sure it's not modem) so the next thing is that he's going to try and move me to a different port.
Will have to see whether that does anything or not. |
|
Knock Knock
@telus.net
| reply to netwerk007
What he's getting at is a commonly know phenomenon where people in the "networking" industry completely ignore the response times for the middle hops in a traceroute.
They do this because (as I think he was trying to say) the only measurement of significance is the end-to-end ping.
The numbers in the middle mean absolutely nothing. Those are the response times of the router, not the response times of traffic traversing it. And it is generally (although apparently not as general as I thought) known that major ISPs rate limit ICMP traffic on their backbone routers so their routers can focus on things like real traffic. Getting 400 ms from hop 4 means nothing if the end device replies in 70 ms. It's not like the numbers are added together...
You guys seemed to be on the right track when you noticed the path to NYC. Traversing the country would be a 100 ms trip. The question is, why? Is is a router failure on the west coast and traffic has been re-routed? Is it the peer of TELUS deciding to only advertise the route in NYC? Who knows, but from experience I can say that nobody working on the TELUS backbone will respond to an ADSL customer email.
So as many have pointed out, you just have to take it on faith that people who spend all day working on this stuff know why the traffic shifted and are either fixing their own broken gear/routing or begging their peer to do the same.
But don't worry, it's not just TELUS who is going to ignore you. There hasn't been an ISP I've dealt with that will take the ping times from Counter Strike as a reason to review their routing or peering configurations. Usually it's a situation where if they fix it great, if they don't you know where the competitor is... |
|
anthonee1230
join:2009-04-08
Richmond, BC | reply to anthonee1230
That's kinda exactly what the CSR I talked to said....basically said that as long as you have internet connection, and a speedtest shows it's running at what you're paying for; they aren't obligated to pay for latency... |
|
kingz
join:2007-08-01 | reply to anthonee1230
Any updates? |
|
anthonee1230
join:2009-04-08
Richmond, BC | reply to anthonee1230
Nope, same problem...modem not the issue though. |
|
roscoojam
join:2007-07-23
| reply to anthonee1230
anthonee1230:
please keep us posted if you hear anything.....right now (monday 8:19pm) using speedtest.net my ping is 120ms to richmond server (from ladner) it normally is around 17ms....that and my web page loads are way slower then normal...
btw: where in richmond are you? im in east ladner...close to tunnel |
|
anthonee1230
join:2009-04-08
Richmond, BC | reply to anthonee1230
No. 2 Rd and Williams. |
|
