Aces High Bulletin Board
Help and Support Forums => Technical Support => Topic started by: Rolex on June 17, 2005, 06:43:33 AM
-
I started having some dramatic warping that has made gameplay almost impossible - the first I've experienced. I did some pingplots and found a change in the usual routing I have to the MA. The strange twist is that every plot shows a different route starting from entry into the Savvis network at Seattle.
Here a just a few samples:
(http://tech-rep.org/ping4.gif)
(http://tech-rep.org/ping3.gif)
(http://tech-rep.org/ping6.gif)
The hops run all over the place. I reduced the interval of pings down to 1 sec. and found even at that small interval, the route is changing with each iteration. Since 1 sec. is the lowest interval I can set, I don't really know how many times the route has changed during that 1 sec. interval.
Just thought I'd pass this along. I'm not a 'network guy', but I've never noticed routing being dynamically changed at such a rate. I hope it isn't permanent.
-
fyi same here. I get a new route with savis every second.
can't be good.
-
I have plotted many pings over the months and SAVVIS is the problem. I have even pinged at .5 (2 per second) and lose about 4% packets in the Seattle hub. I live in Lynnwood (about 12 miles North of Seattle) and have a 4MEG connection through Comcast and go through 11 hops BEFORE getting to the SAVVIS hub in Seattle. Then, I lose anywhere from 10% to 50% or more packet loss in the Chicago hub of SAVVIS that routes me through another THREE hubs IN CHICAGO! And, this is on a good day.
Two nights ago I was flying with a 67ms connection with 93% packet loss! What good is a fast connection that loses the information being sent, or received?
Skuzzy...E-mail me if you want my pingplots.
-
Maybe HT should move the server to europe and use GMT time, at least we have decent routing here :lol
I'm playing from france I used to have 120 ping, now I'm around 180.....HT cutting credits ? :confused:
-
Originally posted by Patches1
I have plotted many pings over the months and SAVVIS is the problem. I have even pinged at .5 (2 per second) and lose about 4% packets in the Seattle hub. I live in Lynnwood (about 12 miles North of Seattle) and have a 4MEG connection through Comcast and go through 11 hops BEFORE getting to the SAVVIS hub in Seattle. Then, I lose anywhere from 10% to 50% or more packet loss in the Chicago hub of SAVVIS that routes me through another THREE hubs IN CHICAGO! And, this is on a good day.
I live on the NW tip of Washington, and I've had problems with savvis ONCE. I still have no idea why everyone else is getting it. And by the way, Comcast bites big wind.
-
I don't get any problems at all with Savvis.
Well, actually I spoke to soon. It's a little problem, I never notice any lag though.
(http://www.r0013636.hostultra.com/images/ping.png)
-
savis pings are terrible today..... I had felt like playing AH (something i havnt been feeling lately) but instead im forced to watch disco after disco, and now im flying a 737-400 out of gatwick instead.......sigh :(
1 <1 ms <1 ms <1 ms 192.168.0.1
2 12 ms 12 ms 12 ms 82.152.176.1
3 13 ms 12 ms 12 ms 81.5.191.217
4 12 ms 11 ms 13 ms ge-1-1.metro2-londencyh00.London1.Level3.net [21
2.187.151.157]
5 12 ms 15 ms 12 ms so-1-3-0.gar1.London1.Level3.net [212.113.3.25]
6 14 ms 13 ms 12 ms ge-1-1.core2.London1.Level3.net [212.187.131.134
]
7 13 ms 13 ms 12 ms bcr1-so-4-0-0.Londonlnx.savvis.net [206.24.169.2
9]
8 13 ms 13 ms 13 ms bcs1-so-1-1-0.Londonlnx.savvis.net [204.70.193.1
14]
9 82 ms 82 ms 81 ms bcs2-so-0-0-0.NewYork.savvis.net [204.70.192.121
]
10 105 ms 101 ms 100 ms dcr1-so-1-2-0.Chicago.savvis.net [204.70.192.105
]
11 * * * Request timed out.
12 108 ms 108 ms 109 ms scr1-at-1-2-0-960.stls1.savvis.net [208.172.1.20
2]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * ^C
gave up.....
-
Rolex I cant believe you are blaming the great PACIFIC NORTWEST:)