Aces High Bulletin Board
General Forums => Aces High General Discussion => Topic started by: VWE on July 15, 2005, 07:24:39 PM
-
I'm on a T-1 and I'm getting a 900 ping to the server, what gives guys?
-
Savvis anyone?
-
When are we starting the switch to AT&T servers?
-
Landing kills discoed. Starting to get agrivated...
-
Misnomer. The server does not control your ping time. The hops (routers) on the Internet do. The last mile (i.e. your initial connection to the Internet) is not much of a factor in the overall scheme of how data gets from one point to another and back again.
We are actively working towards getting the servers moved from thier current location. It takes time as we must minimize the downtime. A lot of planning, shipping, reconfiguration and so on are required.
I should add, a relocation to another ISP does not neccesarily mean there will be improvements. If your local ISP's routers are swamped, there is nothing that will be cured by moving the servers.
-
I couldnt agree more. I know that when I was on dial up and trying different ISP's locally I only found two that made a dramatic improvement over the rest of the field. I found upon closer investigation that the 3 major ISP's in my area all used the same hub for communication and only when I switched to a small locally owned ISP did I notice any kind of decrease in ping and disco's. This is just part of what we all have to deal with at times. :(
Originally posted by Skuzzy
Misnomer. The server does not control your ping time. The hops (routers) on the Internet do. The last mile (i.e. your initial connection to the Internet) is not much of a factor in the overall scheme of how data gets from one point to another and back again.
We are actively working towards getting the servers moved from thier current location. It takes time as we must minimize the downtime. A lot of planning, shipping, reconfiguration and so on are required.
I should add, a relocation to another ISP does not neccesarily mean there will be improvements. If your local ISP's routers are swamped, there is nothing that will be cured by moving the servers.
:(
-
So is there no specific time for the switch Skuzzy?
-
I heard two weeks...
-
never had a higher ping than 63ms, and i'm 1600 miles away on dsl.
been that way for 5 years easy, even with prior server locations.
sure its not your hardware/software or interior/exterior lines ?
-
Amraam,
From what you are saying I don't think you understand networking. No offense intended but you have no way of knowing if you go through the same points as I and the others with problems do. I have had the same problems and each time I run a tracert it comes up as being nodes within the Savvis network being the problem. This is not to say folks do not have other problems as well or other things can get flakey too but Savvis has peering and infrastructure "issues" that are ongoing.
-
Originally posted by nirvana
So is there no specific time for the switch Skuzzy?
It's kinda like Barbecue Nirvana; It's done when it's done.
DmdMax
-
Originally posted by DMax
It's kinda like Barbecue Nirvana; It's done when it's done.
DmdMax
Leave it to you to put it into BBQ terms. :)
-
MMM barbecue.......
Errr I understand, doesn't affect me just wondering for some squaddies.
-
First time today in a couple of years that I had to log due to spikes. Very bad. I know it is not HTC's fault though.
-
amraam, pingtime is only one measure of network performance... others are packet loss and variance. If you have no complaints we're all happy for you, but you seem to be the exception rather than the rule.
-
"you have no way of knowing if you go through the same points as I and the others with problems do."
Each of us may take different on ramps and freeways to get to Texas but we would ALL take the same off ramp to end up at the same destination.
If it were the Savvis router handing off traffic to HTC or the game server itself causing the problems then ALL Players would be experiencing them.
-
Originally posted by Westy
"you have no way of knowing if you go through the same points as I and the others with problems do."
Each of us may take different on ramps and freeways to get to Texas but we would ALL take the same off ramp to end up at the same destination.
If it were the Savvis router handing off traffic to HTC or the game server itself causing the problems then ALL Players would be experiencing them.
Westy,
I'm not sure if you are grasping this but Savvis does not make routers, they are a hosting provider and part of the backbone. In my case it is the hop from seatle to Denver that seems to mess up the most. It is quite likely that you don't go through that same router to arrive at the co location datacenter. Providers need to be able to provide good peering points and bandwidth or they will end up with erratic performance like Savvis.
-
Of course they do not make the router.
When I (or just about anyone else) use the words "Savvis router" it is in the context that it is a router, in use by Savvis, within thier network, to route IP traffic. And used it in the oldest and most simplistic analogy which compares traveling on the internet to driving on a highway.
" In my case it is the hop from seatle to Denver that seems to mess up the most. It is quite likely that you don't go through that same router to arrive at the co location datacenter. "
Exactamundo. However many people do not understand that and they will ignorantly insist that a company at the destination point (in this case HTC) take full responsibility for all thier connection problems.
The fact is HTC cannot possibly fix IP problems in an ISP's network between, for example, Seattle and Denver.
-
They can however, get off a bad network provider and on to a good one like they are doing now. There is a reason why they are dumping Savvis. The problem being the provider they use is the issue far more times than it should be. Both the Seattle and Denver hops I'm talking about are within the Savvis network.