Use this forum if you have a relatively general question or comment about a game, Ventrilo, TeamSpeak, or Murmur/Mumble server with us. If you have a server-specific question that might not help out the community, please directly contact us through your control panel instead.
Hi i really want to get a server from u guys but the cheaper servers are just horrid ping to me these days , i get a 20 ping to your internap servers and over 100 to the other 2 providers. Is this definately a shaw cable problem ? I read somewhere that the problem is from shaw to the internap which i dont see . Just wondering if you guys have heard anything about a fix or when it will be fixed, since I cant afford a internap server Id like to use one of the other 2 . Oh i see where the problem "hop" is from a tracert i did :
9 27 ms 29 ms 29 ms 0.so-1-0-0.XL2.SEA1.ALTER.NET [152.63.2.133]
10 31 ms 30 ms 29 ms POS7-0.BR1.SEA1.ALTER.NET [152.63.105.21]
11 105 ms 84ms 83 ms so-6-3.hsa2.Seattle1.Level3.net [209.0.227.153]
as you can see the jump from hop 10 to 11 is just brutal
Your traffic to level3 is going through Seattle? This might be a temporary thing, since that is very odd. I'd have to see the whole tracert and know your IP address and location to be able to pin down where the problem is.
OK im at work now and I have DSL by telus and the ping is much better minus some intermittant spiking which im guessing is from hop13 in the upcoming tracert but it is waaaay better then my home shaw cable like by half the latency so it must be a shaw or shaw partner routing problem.Heres the dsl trace and i will post the shaw trace tonight when i get home Thanks for your quick replies!!
1 <10 ms <10 ms <10 ms 192.168.123.254
2 * 10 ms * 209.53.1.225
3 10 ms 20 ms 10 ms 209.53.142.70
4 10 ms 10 ms 10 ms vancbc01gr01.bb.telus.com [154.11.4.65]
5 10 ms 20 ms 10 ms vancbc01br01.bb.telus.com [154.11.10.49]
6 10 ms 10 ms 20 ms sttlwa01gr01.bb.telus.com [209.53.75.166]
7 10 ms 20 ms 10 ms so-5-0-0-0.gar2.Seattle1.Level3.net [65.5
8 10 ms 10 ms 20 ms so-0-0-0.gar1.Seattle1.Level3.net [209.24
9 10 ms 20 ms 10 ms so-7-0-0.mp1.Seattle1.Level3.net [64.159.
10 30 ms 40 ms 40 ms so-0-0-0.bbr2.LosAngeles1.Level3.net [209
11 30 ms 40 ms 40 ms unknown.Level3.net [209.247.9.154]
12 50 ms 50 ms 40 ms ge-6-1.ipcolo2.LosAngeles1.Level3.net [20
13 80 ms 90 ms 81 ms unknown.Level3.net [63.209.70.158]
14 30 ms 40 ms 40 ms 125.88.54.66.in-addr.arpa [66.54.88.125]
K heres my home one, my ip = 24.81.8.222 location Vancouver
1 24 ms 23 ms 23 ms 24.81.8.1
2 26 ms 23 ms 23 ms rd1bb-ge3-1.vc.shawcable.net [64.59.152.130]
3 25 ms 23 ms 23 ms rd1wh-pos13-0.vc.shawcable.net [66.163.69.74]
4 24 ms 23 ms 24 ms rc1wh-pos15-0.vc.shawcable.net [66.163.69.34]
5 28 ms 23 ms 23 ms POS5-0.GW3.VAN1.ALTER.NET [205.150.222.125]
6 26 ms 23 ms 23 ms 0.so-1-0-0.XL2.VAN1.ALTER.NET [152.63.137.134]
7 25 ms 23 ms 23 ms 0.so-7-0-0.TL2.VAN1.ALTER.NET [152.63.138.90]
8 27 ms 29 ms 29 ms 0.so-0-0-0.TL2.SEA1.ALTER.NET [152.63.2.146]
9 31 ms 29 ms 29 ms 0.so-1-0-0.XL2.SEA1.ALTER.NET [152.63.2.133]
10 26 ms 29 ms 29 ms POS7-0.BR1.SEA1.ALTER.NET [152.63.105.21]
11 85 ms 83 ms 83 ms so-6-3.hsa2.Seattle1.Level3.net [209.0.227.153]
12 83 ms 83 ms 83 ms ge-4-0-1.mp1.Seattle1.Level3.net [209.247.9.61]
13 52 ms 53 ms 53 ms so-1-0-0.bbr1.LosAngeles1.Level3.net [209.247.9.113]
14 56 ms 53 ms 53 ms unknown.Level3.net [209.247.9.150]
15 92 ms 89 ms 89 ms ge-6-0.ipcolo2.LosAngeles1.Level3.net [209.244.10.46]
16 57 ms 53 ms 53 ms unknown.Level3.net [63.209.70.158]
17 91 ms 88 ms 89 ms 125.88.54.66.in-addr.arpa [66.54.88.125]
C:\Documents and Settings\Administrator>tracert 24.81.8.222
Tracing route to h24-81-8-222.vc.shawcable.net [24.81.8.222]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 1.92.54.66.in-addr.arpa [66.54.92.1]
2 <1 ms <1 ms <1 ms ge-5-1-12.ipcolo2.LosAngeles1.Level3.net [63.209.70.157]
3 <1 ms <1 ms <1 ms unknown.Level3.net [209.244.10.249]
4 <1 ms <1 ms <1 ms p16-1-1-3.r21.lsanca01.us.bb.verio.net [129.250.9.33]
5 8 ms 9 ms 8 ms p16-1-1-0.r21.snjsca04.us.bb.verio.net [129.250.2.187]
6 8 ms 9 ms 8 ms xe-0-2-0.r20.snjsca04.us.bb.verio.net [129.250.2.72]
7 9 ms 9 ms 9 ms p64-0-0-0.r20.plalca01.us.bb.verio.net [129.250.2.70]
8 9 ms 9 ms 9 ms xe-0-2-0.r21.plalca01.us.bb.verio.net [129.250.4.231]
9 67 ms 67 ms 66 ms p16-0-1-1.r20.sttlwa01.us.bb.verio.net [129.250.5.82]
10 66 ms 66 ms 66 ms p16-2-0-0.r04.sttlwa01.us.bb.verio.net [129.250.2.169]
11 27 ms 27 ms 27 ms ge-1.bigpipe.sttlwa01.us.bb.verio.net [129.250.10.158]
12 31 ms 31 ms 31 ms rc1wh-pos11-0.vc.shawcable.net [66.163.76.38]
13 31 ms 31 ms 31 ms rd1wh-pos15-0.vc.shawcable.net [66.163.69.33]
14 32 ms 31 ms 31 ms 24.81.8.1
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
From looking at the two traces, it appears that Shaw is not routing correctly around an overloaded UUnet-Level3 peering point (or router problem) in Seattle -- but on the trace back, it goes right to the correct place. You might need to call them about it. It looks like they are routing correctly to some Level3 IPs, just not all of them. Hard to say, though.
