Hops to game servers:

#1

anyone else notice the hops to the game servers takes the long way around now? I was wondering why my ping changed and I did a tracert and found out it takes 25 hops now instead of 12, the hops go to sasktel then back to vancouver then seattle, san jose, denver then to chicago where most rpg game servers are

#2

Yeah, I noticed this too. I get about 200 Ping average in any game online.

compared to Pings in 2004/2005 when I got about 80 Ping.

amazing

#3

yeah me too, going from dial up to dsl lite, I never noticed any change in speed, I personally felt at time dial was faster, then moving up to standard I thought things were looking up now i’m back down to feeling a little left out when I see others posts on their speeds and mine are slowly going back to the lower speeds again.

#4

my speeds are some what ok…

#5

scenic route to rpg servers in Chicago

1  <10 ms    14 ms    13 ms  69.176.176.1
2    14 ms  <10 ms    14 ms  71conn9.rupert.net [69.176.191.9]
3    14 ms    14 ms    14 ms  71conn6.rupert.net [69.176.191.6]
4    41 ms    28 ms    27 ms  1  <10 ms    14 ms    13 ms  69.176.176.1
2    14 ms  <10 ms    14 ms  71conn9.rupert.net [69.176.191.9]
3    14 ms    14 ms    14 ms  71conn6.rupert.net [69.176.191.6]
4    41 ms    28 ms    27 ms  142.165.3.245
5    27 ms    28 ms    27 ms  142.165.60.18
6    55 ms    41 ms    55 ms  po-2-0.regn01d59gw3.core.sasktel.net [142.165.2.1]
7    41 ms    55 ms    55 ms  67.69.244.254
8    41 ms    55 ms    55 ms  core3-regina_POS0-0-0.net.bell.ca [64.230.174.16]
9  192 ms  138 ms    96 ms  core2-vancouver_pos_9_0.net.bell.ca [64.230.144.]
10    69 ms    69 ms    82 ms  bx2-vancouver_POS1-0.net.bell.ca [64.230.248.58]
11    55 ms    55 ms    55 ms  if-3-0.core2.VCW-Vancouver.teleglobe.net [64.86.15.13]
12    55 ms    55 ms    55 ms  if-8-0.core2.SEP-Seattle.teleglobe.net [66.110.6.17]
13    55 ms    96 ms    55 ms  if-6-0.core1.SEP-Seattle.Teleglobe.net [207.45.16.38]
14  124 ms    96 ms  123 ms  if-12-0.core1.SQN-SanJose.teleglobe.net [66.198.7.21]
15    82 ms    69 ms    69 ms  if-5-0-1.core4.SQN-SanJose.teleglobe.net [66.19897.38]
16    83 ms    96 ms    82 ms  if-5-0-0.mcore4.LAA-LosAngeles.teleglobe.net [21.6.85.33]
17  178 ms  179 ms  178 ms  if-9-0.core2.LAA-LosAngeles.teleglobe.net [216.685.14]
18  206 ms  206 ms  206 ms  ix-2-0.core2.LAA-LosAngeles.teleglobe.net [66.19.112.14]
19  233 ms  234 ms  247 ms  12.127.3.214
20  234 ms  233 ms  247 ms  tbr2.sl9mo.ip.att.net [12.122.10.13]
21  234 ms  233 ms  233 ms  cr2.sl9mo.ip.att.net [12.122.18.109]
22  234 ms  247 ms  233 ms  cr2.cgcil.ip.att.net [12.122.2.21]
23  233 ms  234 ms  233 ms  tbr1.cgcil.ip.att.net [12.122.17.158]
24  233 ms  234 ms  234 ms  gar1.chail.ip.att.net [12.123.4.69]
25    *        *        *    Request timed out.
26  219 ms  220 ms  234 ms  69.28.220.185

race complete.

#6

as i said in the thread on December’s Citywest Speeds,

our internet craps out after Vancouver.

and it Didn’t before.

#7

Interesting thing is it looks like none of this traffic is going through Telus.  The Sasktel bit is Navigata who were the original carrier of CityWest internet traffic.  Then Sasktel hands off to Bell … wonder if this has anything to do with the cellular changes … maybe the deal includes using Bell as an internet carrier as well …

#8

Another note - a tracert to the same server from my Telus connection in Terrace is just 10 hops.

#9

1    6 ms    6 ms    7 ms  69.176.176.1
2    7 ms    7 ms    7 ms  71conn9.rupert.net [69.176.191.9]
3    10 ms    9 ms    10 ms  71conn6.rupert.net [69.176.191.6]
4    28 ms    30 ms    27 ms  142.165.3.245
5    28 ms    27 ms    27 ms  navigata-van-gw.peer1.net [216.187.82.17]
6    88 ms    88 ms    88 ms  oc48-po0-0.tor-151f7-cor-2.peer1.net [216.187.1
.138]
7    89 ms    89 ms    88 ms  oc48-po4-0.tor-151f-cor-1.peer1.net [216.187.11
193]
8    89 ms    88 ms    89 ms  oc48-po6-0.tor-1yg-cor-1.peer1.net [216.187.114
33]
9    *        *        *    Request timed out.
10    99 ms    99 ms  100 ms  69.28.220.185

This is a good example of internet routing and how it can change from day to day or even minute to minute.

I’m on what appears to be the same DSL equipment that Jabber is and today the path takes a completely different route to the same server and is only 10 hops.

Obviously Navigata had some peering/routing that was not very good the other day, but now the peering has changed is pretty good now.

Also in Jabbers trace, the first 4 hops are dups…took me a minute to see that.

#10