Loosing host

[DCCBOSS]

Starting last night I was loosing my UDP and getting booted from the game multiple times at different length's of time on game it seemed very random, this almost never happens to my system, I have been in constant contact with Comcast and Savvis, my packet losses over that past 4 days have been top to bottom in my 20 hops but seem to bounce up and down in the Comcast and Att net hubs but always their are losses at Savvis hubs, I know HTC is working it from their end but what else can we do to get them to pay attention to us, they feed us the text book lines and say they will escalate it but nothing happens. One response I did get back was from Savvis and in his Email he said the packet losses are only cosmetic    but he did admit that there was a problem in their system which they are working on to resolve that issue. So today I will begin the feudal effort of calling them again. If anybody has any other suggestions I'm all ears.

DCCBOSS 

[Skuzzy]

See this thread.  It is an ongoing issue with Comcast.  In particular check the last post by me.

[Dustoff2]

Starting last night I was loosing my UDP and getting booted from the game multiple times at different length's of time on game it seemed very random, this almost never happens to my system, I have been in constant contact with Comcast and Savvis, my packet losses over that past 4 days have been top to bottom in my 20 hops but seem to bounce up and down in the Comcast and Att net hubs but always their are losses at Savvis hubs, I know HTC is working it from their end but what else can we do to get them to pay attention to us, they feed us the text book lines and say they will escalate it but nothing happens. One response I did get back was from Savvis and in his Email he said the packet losses are only cosmetic    but he did admit that there was a problem in their system which they are working on to resolve that issue. So today I will begin the feudal effort of calling them again. If anybody has any other suggestions I'm all ears.

DCCBOSS 

perhaps sending your cousin joey no neck   


A question to Skuzzy.  What is or would be considered too high of a number for latency? All of the numbers I have seen lately on the thread you locked, have been going from 20 ms on the comcast backbone to around 80-90 on the savvis network. Which looks ok compared to what I was getting back in Dec. 21.08 which was going from 18ms to 323 ms which is obviously an issue back then.

Is there a magic number in which we would start seeing issues? I think 80 ms seems average.

another question, was it always savvis or is that recent? because I don't see that name in my Dec. ping plot.

Dustoff 

[The Fugitive]

I think I saw Skuzzy say anything under 250ms is good, obviously the smaller the better, but its the "quality" of the connection that you need. If your dropping packets and your connection keeps seeming to drop off then come back in you'll get a disconnect and the game will drop you (thats why cable pulling is bogus). So if you have a 200ms ping, as long as its a solid 200ms and doesn't jump all over the place, you should be ok.

[DCCBOSS]

I had just got off the phone with a Savvis Tech and I have been sending my ping plots to (incident@savvis.net), I recommend anybody who has cable internet to do the same, I have seen a constant loss of packets at the Savvis hubs, here is the repair tech phone # at Savvis (888-638-6771), I am also continuing contact with Comcast due to the fact that they and also ATT World Wide Net contracts to Savvis for hosting web distribution hubs. So the only way this going to be resolved quickly is for all members of HTC that are having this issue is to call and Email them your ping plots but do not STOP doing it, that is when you get their attention and the same goes for Comcast. As far as ATT goes my ping plots show packet losses and very high ping rate on thier IP locations all the way to HTC, I think this is also a issue but I do not know how to get to the techs there yet. On a another note about Comcast is that it takes THREE consecutive calls from a client for them to automatically escalate the issue you are complaining about and here is the Email for Comcast that you want to send your ping plots to (testlab6@comcast.net). This what I've done so far, I will keep the pressure on them until a resolution is found I suggest you guys do the same.

DCCBOSS 

[DCCBOSS]

See my reply post above about important information on contacts to help get this resolved.

[Skuzzy]

The problem will all Comcast and Sprint customers is with the return trip through Savvis.  You cannot see the problem on the trip from your computer.

Savvis is routing every packet out of Dallas to Los Angeles, then back to Dallas, regardless if its destination. 

Refer your Comcast and Sprint contacts to this thread.  Do not let them tell you it is an AT&T problem.  Your traces cannot show the problem.  The return traces I have in the thread I linked shows traces in both directions.  It is imperative you do not supply Comcast and Sprint with your own traces.

If you do that, they will respond it is an AT&T problem, when in fact, it is not.

[DCCBOSS]

The problem will all Comcast and Sprint customers is with the return trip through Savvis.  You cannot see the problem on the trip from your computer.

Savvis is routing every packet out of Dallas to Los Angeles, then back to Dallas, regardless if its destination. 

Refer your Comcast and Sprint contacts to thsi thread.  Do not let them tell you it is an AT&T problem.  Your traces cannot show the problem.  The return traces I have in the thread I linked shows traces in both directions.  It is imperative you do not supply Comcast and Sprint with your own traces.

If you do that, they will respond it is an AT&T problem, when in fact, it is not.

Yes I understand that and I had sent you a Email I will talk to you then.

[LEADER38]

Hey Skuzzy for what its worth I use Qwest not Comcast And I've been experiensing the 'HOST CONNECTION LOST' issue that Dccboss and other have lately.   

SESunDvl...Screaming Eagles

[Denholm]

Post up your PingPlotter results, we'll see what's got ya tangled. I do recall, though, that someone else here had some serious issues with Qwest. So you will probably end up calling someone same as the rest of us.