Author Topic: Swell servers guys (Read 994 times)

Westy · « **Reply #15 on:** July 19, 2005, 07:29:57 AM »

"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.

rabbidrabbit · « **Reply #16 on:** July 19, 2005, 08:32:49 AM »

Quote

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.

Westy · « **Reply #17 on:** July 19, 2005, 09:13:47 AM »

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.

rabbidrabbit · « **Reply #18 on:** July 19, 2005, 09:38:06 AM »

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.