My pings to local CS server are really bad?

Posts : 3 Join date : 2009-01-29

Im on bell, why do I ping so bad to the "local" gaming server?
This is a tracert from Edmonton in my home.

Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\>tracert 216.6.233.37

Tracing route to 216.6.233.37.rdns.ubiquityservers.com [216.6.233.37]
over a maximum of 30 hops:

1 2 ms <1 ms <1 ms 192.168.1.1
2 36 ms 35 ms 31 ms bas1-calgaryqa_lo0_SYMP.net.bell.ca [64.230.197.
247]
3 31 ms 31 ms 28 ms dis6-calgary_Vlan150.net.bell.ca [64.230.176.205
]
4 30 ms 31 ms 28 ms core2-calgary_GE2-0.net.bell.ca [206.108.101.149
]
5 46 ms 31 ms 35 ms core4-calgaryqa_POS2-0.net.bell.ca [64.230.176.1
34]
6 74 ms 75 ms 71 ms core4-toronto12_POS2-2.net.bell.ca [64.230.176.1
77]
7 81 ms 79 ms 82 ms core4-toronto63_POS13-0.net.bell.ca [64.230.242.
182]
8 82 ms 71 ms 79 ms bx4-toronto63_so-1-0-0.net.bell.ca [64.230.160.1
26]
9 76 ms 78 ms 75 ms peer_level3_bx4-toronto63.net.bell.ca [67.69.246
.190]
10 93 ms 89 ms 89 ms ae-8-8.ebr1.Chicago1.Level3.net [4.69.140.245]
11 118 ms 96 ms 107 ms ae-6.ebr1.Chicago2.Level3.net [4.69.140.190]
12 111 ms 118 ms 123 ms ae-3.ebr2.Denver1.Level3.net [4.69.132.61]
13 139 ms 147 ms 141 ms ae-2.ebr2.Seattle1.Level3.net [4.69.132.53]
14 138 ms 143 ms 140 ms ae-23-52.car3.Seattle1.Level3.net [4.68.105.36]

15 151 ms 143 ms 143 ms ge1-1.cr01.sea01.mzima.net [4.71.152.2]
16 147 ms 140 ms 147 ms xe0-2.cr01.sea02.mzima.net [216.193.255.234]
17 152 ms 147 ms 165 ms ge0-ubiquity.cust.sea02.mzima.net [72.37.232.166
]
18 151 ms 137 ms 140 ms 216.6.233.37.rdns.ubiquityservers.com [216.6.233
.37]

Trace complete.

it used to be 210 ping. id settle for 98-99.

Posts : 10 Join date : 2009-01-16

if theres a server you play in frequently you can call your ISP and tell them to directly route you to it.

Our server is actually located in Seattle (apparently) and we haven't been able to figure out just why we're pinging so badly. We'll keep you posted if we find out. The ping seems to fluctuate some days.

Posts : 20 Join date : 2008-11-08

i ping 50 - 60

Posts : 1 Join date : 2008-07-03

the reason is evident in your trace route

you are routing through toronto, chicago, then denver before reaching seattle. telus has been doing this to me lately to all western servers. pretty ridiculous but obviously their nodes are being overloaded at some point between edmonton and seattle and they need to redirect the traffic through a much longer route. same thing happened with shaw about a year ago.