| [BC] routing path through Chicago The Telus routing path through Chicago as problems.
Typical “good” trace during the day, from Calgary, (before 8.30pm MT):
Tracing route to chicago.voip.ms [64.120.22.242]
1 2 ms 1 ms 1 ms home.Home [192.168.1.254]
2 28 ms 26 ms 26 ms 199.126.12.1
3 26 ms 26 ms 26 ms 173.182.202.129
4 64 ms 54 ms 55 ms CHCGILDTGR01.bb.telus.com [154.11.11.142]
5 55 ms 77 ms 56 ms 173.182.200.66
6 59 ms 59 ms 56 ms ae3.ar1.ord1.us.nlayer.net [69.31.111.243]
7 60 ms 67 ms 55 ms edge1.chi2.ubiquityservers.com [69.31.111.66]
8 54 ms 55 ms 56 ms 64.120.22.242.ubiquityservers.com [64.120.22.242]
Typical “bad” trace after 9pm -Ping times get progressively worse from 8.30 pm MT and, at 10pm to 11.30pm MT it is “bad”. Note the large increase in the hop #5. This increase in ping time has a very adverse effect on my VOIP quality:
Tracing route to chicago.voip.ms [64.120.22.242]
1 5 ms 9 ms 3 ms home.Home [192.168.1.254]
2 26 ms 25 ms 34 ms 199.126.12.1
3 26 ms 25 ms 28 ms 173.182.202.129
4 54 ms 59 ms 55 ms CHCGILDTGR01.bb.telus.com [154.11.11.142]
5 123 ms 122 ms 127 ms 173.182.200.66
6 124 ms 126 ms 126 ms ae3.ar1.ord1.us.nlayer.net [69.31.111.243]
7 124 ms 121 ms 124 ms edge1.chi2.ubiquityservers.com [69.31.111.66]
8 116 ms 125 ms 125 ms 64.120.22.242.ubiquityservers.com [64.120.22.242]
Interestingly, this path has improved but still it was reported some two years ago:
»/forum/r250z24···g-Issues
This seems too late in the evening to be having congestion. Is there anything Telus can do about hop#5 - 173.182.200.66. |
|
| Try the search function here. The answer is NO there is absolutely nothing that can be done about routing. I never have an issue connecting to gaming servers in Chicago and I haven't had a ping above 45ms when playing on them all night either. |
|
| reply to titicaca
I have the same problem. it HAS to be fixed. i play competitively CS and play past 9 all the time. I'm up in Cold lake Alberta. |
|
| reply to titicaca
Try Shaw is you need a little better routing. Shaw seems to be a bit better as far as peers than Telus, but every ISP has issues from time to time. Nothing you can do about routing, even with fiber circuits. |
|
|
|
| reply to onzzz
Has to be fixed? If you learn more about the peering process, you'll realize it's not remotely as simple as you think it is.
When I test my connection to that voip.ms server, I go through 2 more hops than you as your hop 5 is my #7 and I'm in Edmonton but have Optik TV. My response times over the last couple days to that IP show no sign at all of the delays you see during peak times.
...
5 edtnabxmca01.bb.telus.com (154.11.94.226) 7.485 ms 8.976 ms 7.527 ms
6 chcgildtgr01.bb.telus.com (154.11.13.186) 36.931 ms 51.939 ms 44.607 ms
7 173.182.200.66 (173.182.200.66) 39.693 ms 38.299 ms 46.468 ms
Considering Telus' naming convention for devices, I strongly suspect both CHCGILDTGR01.bb.telus.com and 173.182.200.66 are both in the USA. The first being CHiCaGo ILinios. All hops after that are identical for me as what you get to that server ending with:
10 64.120.22.242.ubiquityservers.com (64.120.22.242) 37.696 ms 45.584 ms 37.933 ms |
|
 pfakPremium
join:2002-12-29
Vancouver, BC | said by nss_tech:Has to be fixed? If you learn more about the peering process, you'll realize it's not remotely as simple as you think it is. It's not simple because TELUS sucks as a peering partner. They're incredibly difficult to deal with and want everyone to pay them. This is what "has" to be fixed.
--
The more I C, the less I see. |
|
| Difficult to deal with? So you're a business that offers peering services to ISPs? Or are you just spouting off random baseless claims? |
|
| I'm not saying either way for sure, but based on personal experience I GENERALLY get better routing with my Shaw than Telus. Even Shaw has it's issues at times, but Telus seems to be a continual issue. Not one thing, it's always another. Atleast I'm getting descent speeds on the Telus at one client here in RD. Used to be terrible, but this is reasonable for now.
 |
|
pfakPremium
join:2002-12-29
Vancouver, BC | reply to nss_tech
said by nss_tech:Or are you just spouting off random baseless claims?
My claims are never baseless, I just can't always quote my sources 
--
The more I C, the less I see. |
|
| reply to titicaca
just got a 25mb line installed and the routing to illinois/chicago is driving me crazy, i need to play matches on these servers and its 100+ ping... on calgary telus it was only 60-70.
when i use my shitty school shaw wifi i get 60 ping to illinois, is there anything i can do besides switch to shaw? i just signed up with telus?
maybe complain and ask for a low latency profile??
hit me on facebook if there's any advice u can offer me, or just post here, im sure ill be back
facebook.com/adv1k |
|
| I'm guessing you didn't read the whole thread...
There is still absolutely nothing that can be done about routing issues. |
|
| reply to lloydzd
I'm still getting 40ms pings to Chicago consistently on a 15mbps connection. The odd time it goes up a little bit depending on the server. |
|
1 edit | reply to titicaca
Good here.
1 1 ms  |
|
| That is because you used the Calgary server instead of the Chicago one. How did you get an 8mbps upload speed?
Most of the speedtest servers in Chicago are a little slow (65ms). The one in Aurora IL next to Chicago was a little quicker.
|
|
| reply to titicaca
Whoops, my bad. Habit to select Edmonton or Calgary. Bonded T1's, suppost to 10Mb, but it's Telus so I'll never see it.
 |
|
