For those of you who live in Western Canada, how is shaw cable?
2 of my teammates use shaw and they're routing is absolute trash and I'm trying to find a solution. I've already sent a tracert to nfo to see if anything can be done on their end. Does anyone here use shaw and get good/stable ping to chi/dal servers? If you can do a tracert to our scrim server(big.g.nfoservers.com) and post the results here that would be cool.
2 of my teammates use shaw and they're routing is absolute trash and I'm trying to find a solution. I've already sent a tracert to nfo to see if anything can be done on their end. Does anyone here use shaw and get good/[i]stable[/i] ping to chi/dal servers? If you can do a tracert to our scrim server(big.g.nfoservers.com) and post the results here that would be cool.
My friend from Calgary used Shaw, and his routing was fine.
However, if you're actually west coast Canada (BC area), you shouldn't really expect anything better than 85 ping to Dallas and 70 to Chi.
However, if you're actually west coast Canada (BC area), you shouldn't really expect anything better than 85 ping to Dallas and 70 to Chi.
I use shaw in Vancouver and get pretty much what #2 said. I can put up a trace when I get home this evening.
I'm on Shaw. Gives me better DL/UL speeds than Telus will offer in my area. Routing to Texas is terrible, most other areas are fine. Never had a problem with Chicago. If you have a problem with your internet their support is usually not at all helpful, sometimes downright rude. I wish we had more options available but we don't, so whatever.
TBH, I don't think it's limited to Shaw. I have TWC in Ohio and routing to Dallas NFO (only NFO) is complete trash. I would normally get 50-60 to dallas and I have been getting 100-110 for the last month with any fixes.
My chi routing has been better, but this isn't too bad. Dallas is a hot mess of loss, choke, spikes, and broken hearts.
Tracing route to big.g.nfoservers.com [74.91.125.56]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 14 ms 11 ms 11 ms gw3cv.gv.shawcable.net [64.59.162.146]
4 13 ms 15 ms 15 ms 66.163.72.21
5 15 ms 15 ms 15 ms rc3wt-pos6-0-0.wa.shawcable.net [66.163.77.182]
6 12 ms 33 ms 13 ms ix-1-2-1-0.tcore1.00S-Seattle.as6453.net [64.86.
123.25]
7 17 ms 12 ms 15 ms 64.86.123.70
8 15 ms 15 ms 15 ms vb2000d1.rar3.seattle-wa.us.xo.net [207.88.13.14
2]
9 75 ms 70 ms 70 ms te-4-0-0.rar3.denver-co.us.xo.net [207.88.12.82]
10 103 ms 142 ms 100 ms te-4-1-0.rar3.chicago-il.us.xo.net [207.88.12.21
]
11 76 ms 66 ms 70 ms 207.88.14.6.ptr.us.xo.net [207.88.14.6]
12 66 ms 65 ms 65 ms 207.88.184.146.ptr.us.xo.net [207.88.184.146]
13 64 ms 67 ms 65 ms border5.po1-bbnet1.chg.pnap.net [64.94.32.10]
14 64 ms 64 ms 67 ms c-74-91-125-56.internap-chicago.nfoservers.com [
74.91.125.56]
Trace complete.
[quote]Tracing route to big.g.nfoservers.com [74.91.125.56]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 14 ms 11 ms 11 ms gw3cv.gv.shawcable.net [64.59.162.146]
4 13 ms 15 ms 15 ms 66.163.72.21
5 15 ms 15 ms 15 ms rc3wt-pos6-0-0.wa.shawcable.net [66.163.77.182]
6 12 ms 33 ms 13 ms ix-1-2-1-0.tcore1.00S-Seattle.as6453.net [64.86.
123.25]
7 17 ms 12 ms 15 ms 64.86.123.70
8 15 ms 15 ms 15 ms vb2000d1.rar3.seattle-wa.us.xo.net [207.88.13.14
2]
9 75 ms 70 ms 70 ms te-4-0-0.rar3.denver-co.us.xo.net [207.88.12.82]
10 103 ms 142 ms 100 ms te-4-1-0.rar3.chicago-il.us.xo.net [207.88.12.21
]
11 76 ms 66 ms 70 ms 207.88.14.6.ptr.us.xo.net [207.88.14.6]
12 66 ms 65 ms 65 ms 207.88.184.146.ptr.us.xo.net [207.88.184.146]
13 64 ms 67 ms 65 ms border5.po1-bbnet1.chg.pnap.net [64.94.32.10]
14 64 ms 64 ms 67 ms c-74-91-125-56.internap-chicago.nfoservers.com [
74.91.125.56]
Trace complete.[/quote]
Tracing route to c-74-91-125-56.internap-chicago.nfoservers.com [74.91.125.56]
over a maximum of 30 hops:
1 6 ms 19 ms 7 ms cpe-24-210-56-1.columbus.res.rr.com [24.210.56.1
]
2 15 ms 15 ms 15 ms network-065-025-145-121.midohio.rr.com [65.25.14
5.121]
3 21 ms 24 ms 22 ms network-065-029-001-038.midwest.rr.com [65.29.1.
38]
4 29 ms 31 ms 27 ms ae10-0.cr0.dca20.tbone.rr.com [107.14.19.14]
5 33 ms 27 ms 28 ms 107.14.19.135
6 28 ms 27 ms 30 ms 64.209.111.137
7 34 ms 31 ms 32 ms Internap-Chicago.TenGigabitEthernet2-4.ar5.CHI1.
gblx.net [208.48.24.186]
8 31 ms 30 ms 32 ms border5.po2-bbnet2.chg.pnap.net [64.94.32.74]
9 31 ms 31 ms 31 ms c-74-91-125-56.internap-chicago.nfoservers.com [
74.91.125.56]
Trace complete.
C:\Users\Agent Orange>tracert dallas1.tf2pug.com
Tracing route to dallas1.tf2pug.com [74.91.114.70]
over a maximum of 30 hops:
1 8 ms 7 ms 7 ms cpe-24-210-56-1.columbus.res.rr.com [24.210.56.1
]
2 23 ms 23 ms 15 ms network-065-025-145-121.midohio.rr.com [65.25.14
5.121]
3 19 ms 23 ms 23 ms network-065-029-001-038.midwest.rr.com [65.29.1.
38]
4 28 ms 31 ms 31 ms ae-3-0.cr0.dca20.tbone.rr.com [66.109.6.70]
5 27 ms 30 ms 28 ms 107.14.19.135
6 26 ms 28 ms 25 ms te0-6-0-7.mpd21.iad02.atlas.cogentco.com [154.54
.10.193]
7 30 ms 27 ms 27 ms be2044.mpd21.dca01.atlas.cogentco.com [154.54.24
.97]
8 47 ms 44 ms 46 ms te0-1-0-7.mpd21.atl01.atlas.cogentco.com [154.54
.1.225]
9 96 ms 99 ms 95 ms te0-2-1-3.mpd21.iah01.atlas.cogentco.com [154.54
.42.217]
10 87 ms 91 ms 92 ms te0-2-0-1.ccr21.dfw01.atlas.cogentco.com [154.54
.2.14]
11 92 ms 99 ms 90 ms be2031.ccr21.dfw03.atlas.cogentco.com [154.54.7.
46]
12 52 ms 52 ms 64 ms 38.104.204.74
13 56 ms 51 ms 50 ms border1.pc-1-bbnet1.ext1a.dal.pnap.net [216.52.1
91.24]
14 53 ms 51 ms 50 ms c-74-91-114-70.internap-dallas.nfoservers.com [7
4.91.114.70]
Trace complete.
over a maximum of 30 hops:
1 6 ms 19 ms 7 ms cpe-24-210-56-1.columbus.res.rr.com [24.210.56.1
]
2 15 ms 15 ms 15 ms network-065-025-145-121.midohio.rr.com [65.25.14
5.121]
3 21 ms 24 ms 22 ms network-065-029-001-038.midwest.rr.com [65.29.1.
38]
4 29 ms 31 ms 27 ms ae10-0.cr0.dca20.tbone.rr.com [107.14.19.14]
5 33 ms 27 ms 28 ms 107.14.19.135
6 28 ms 27 ms 30 ms 64.209.111.137
7 34 ms 31 ms 32 ms Internap-Chicago.TenGigabitEthernet2-4.ar5.CHI1.
gblx.net [208.48.24.186]
8 31 ms 30 ms 32 ms border5.po2-bbnet2.chg.pnap.net [64.94.32.74]
9 31 ms 31 ms 31 ms c-74-91-125-56.internap-chicago.nfoservers.com [
74.91.125.56]
Trace complete.
C:\Users\Agent Orange>tracert dallas1.tf2pug.com
Tracing route to dallas1.tf2pug.com [74.91.114.70]
over a maximum of 30 hops:
1 8 ms 7 ms 7 ms cpe-24-210-56-1.columbus.res.rr.com [24.210.56.1
]
2 23 ms 23 ms 15 ms network-065-025-145-121.midohio.rr.com [65.25.14
5.121]
3 19 ms 23 ms 23 ms network-065-029-001-038.midwest.rr.com [65.29.1.
38]
4 28 ms 31 ms 31 ms ae-3-0.cr0.dca20.tbone.rr.com [66.109.6.70]
5 27 ms 30 ms 28 ms 107.14.19.135
6 26 ms 28 ms 25 ms te0-6-0-7.mpd21.iad02.atlas.cogentco.com [154.54
.10.193]
7 30 ms 27 ms 27 ms be2044.mpd21.dca01.atlas.cogentco.com [154.54.24
.97]
8 47 ms 44 ms 46 ms te0-1-0-7.mpd21.atl01.atlas.cogentco.com [154.54
.1.225]
9 96 ms 99 ms 95 ms te0-2-1-3.mpd21.iah01.atlas.cogentco.com [154.54
.42.217]
10 87 ms 91 ms 92 ms te0-2-0-1.ccr21.dfw01.atlas.cogentco.com [154.54
.2.14]
11 92 ms 99 ms 90 ms be2031.ccr21.dfw03.atlas.cogentco.com [154.54.7.
46]
12 52 ms 52 ms 64 ms 38.104.204.74
13 56 ms 51 ms 50 ms border1.pc-1-bbnet1.ext1a.dal.pnap.net [216.52.1
91.24]
14 53 ms 51 ms 50 ms c-74-91-114-70.internap-dallas.nfoservers.com [7
4.91.114.70]
Trace complete.
I'm visiting my fiance + family right now in BC, Shaw is pretty damned awesome. Never had a single issue. Also, compared to what people in eastern Canada have to say about their ISPs, I don't think you can really go wrong with Shaw.
Routing to dallas is trash from BC no matter what ISP you have.
testify
Here's a tracert for you hooli,
C:\Windows\system32>tracert big.g.nfoservers.com
Tracing route to big.g.nfoservers.com [74.91.125.56]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms ...
2 * * * Request timed out.
3 15 ms 15 ms 15 ms ...
4 16 ms 15 ms 15 ms rc2bb-tge0-5-1-0.vc.shawcable.net [66.163.69.85]
5 17 ms 15 ms 15 ms rc3wt-pos0-0-0.wa.shawcable.net [66.163.76.126]
6 14 ms 21 ms 15 ms ix-0-0-2-0.tcore1.00S-Seattle.as6453.net [64.86.
123.29]
7 14 ms 13 ms 13 ms 64.86.123.70
8 18 ms 23 ms 27 ms vb2000d1.rar3.seattle-wa.us.xo.net [207.88.13.14
2]
9 64 ms 67 ms 67 ms te-4-0-0.rar3.denver-co.us.xo.net [207.88.12.82]
10 69 ms 71 ms 71 ms te-4-1-0.rar3.chicago-il.us.xo.net [207.88.12.21
]
11 62 ms 61 ms 61 ms 207.88.14.6.ptr.us.xo.net [207.88.14.6]
12 63 ms 61 ms 62 ms 207.88.184.146.ptr.us.xo.net [207.88.184.146]
13 62 ms 61 ms 62 ms border5.po2-bbnet2.chg.pnap.net [64.94.32.74]
14 61 ms 61 ms 61 ms c-74-91-125-56.internap-chicago.nfoservers.com [
74.91.125.56]
Trace complete.
[quote=testify]
Here's a tracert for you hooli,
C:\Windows\system32>tracert big.g.nfoservers.com
Tracing route to big.g.nfoservers.com [74.91.125.56]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms ...
2 * * * Request timed out.
3 15 ms 15 ms 15 ms ...
4 16 ms 15 ms 15 ms rc2bb-tge0-5-1-0.vc.shawcable.net [66.163.69.85]
5 17 ms 15 ms 15 ms rc3wt-pos0-0-0.wa.shawcable.net [66.163.76.126]
6 14 ms 21 ms 15 ms ix-0-0-2-0.tcore1.00S-Seattle.as6453.net [64.86.
123.29]
7 14 ms 13 ms 13 ms 64.86.123.70
8 18 ms 23 ms 27 ms vb2000d1.rar3.seattle-wa.us.xo.net [207.88.13.14
2]
9 64 ms 67 ms 67 ms te-4-0-0.rar3.denver-co.us.xo.net [207.88.12.82]
10 69 ms 71 ms 71 ms te-4-1-0.rar3.chicago-il.us.xo.net [207.88.12.21
]
11 62 ms 61 ms 61 ms 207.88.14.6.ptr.us.xo.net [207.88.14.6]
12 63 ms 61 ms 62 ms 207.88.184.146.ptr.us.xo.net [207.88.184.146]
13 62 ms 61 ms 62 ms border5.po2-bbnet2.chg.pnap.net [64.94.32.74]
14 61 ms 61 ms 61 ms c-74-91-125-56.internap-chicago.nfoservers.com [
74.91.125.56]
Trace complete.[/quote]
Agreed connection to dallas is p shit, usually avg 98 ping. for chi servers usually 58 +/-.
Shaw is pretty good, upload is meh
Shaw is pretty good, upload is meh
Im in calgary and I have the shaw 50 down 5 up plan. Its pretty much the best internet in calgary. Only problem i have is that ping to dallas is usually in the 100-110 range. Ping to chicago however is usually about 60. It drops to 50 on esea servers.
You get a BETTER ping to ESEA servers?! What kind of sorcery is this?
thrasherYou get a BETTER ping to ESEA servers?! What kind of sorcery is this?
I always have
I always have
Shaw is pretty good, but you have no other alternatives, Telus is really really REALLY bad in terms of pricing.
I live in BC and have Telus, I get about 70-80 ping to Dallas so not much better. Ping to Chicago is about 65. Ping to eastern servers is 90+.
It used to be a lot less before 2008. I used to get 70 ping to New York in 2005. Guess all the texting and twitter updates these days floods then entire internet with its bullshit. It's sad really.
It used to be a lot less before 2008. I used to get 70 ping to New York in 2005. Guess all the texting and twitter updates these days floods then entire internet with its bullshit. It's sad really.
From BC. Shaw seems to be pretty solid as I get about 50-70 ping to Chicago, about 90 to Dallas and the East. Had a problem a little while back but it was more due to the crappy wireless hardware they try and encourage you to use.
TrekkieIm in calgary and I have the shaw 50 down 5 up plan. Its pretty much the best internet in calgary. Only problem i have is that ping to dallas is usually in the 100-110 range. Ping to chicago however is usually about 60. It drops to 50 on esea servers.
fuck you i get 70-120 to dallas esea servers and i live right next to dallas
fuck you i get 70-120 to dallas esea servers and i live right next to dallas
I contacted Shaw once about Internet in Ontario, all they said was "We plan to in the near future.". Damn your early monopolization Rogers and Bell!