Check out AT&T's Valentine's Day Gift Guide for ideas & deals on the new Samsung Galaxy S23!
tkremin's profile

Tutor

 • 

8 Messages

Sunday, March 25th, 2018 5:55 PM

Why does server 192.205.32.210 constantly drop between 50% and 80% of packets?

I always get routed through this server hub, and it is a constant issue of having it drop 50-80% of packets sent through.
What is AT&T doing to fix this issue?

 

packet loss.jpg

 

1 Attachment

ATTHelp

Community Support

 • 

207.7K Messages

5 years ago

Hello @tkremin,


I certainly understand your desire to troubleshoot your router and would be more than happy to assist you with this.

We have our wonderful self-assisting troubleshoot and resolve tool which gives you step-by-step instructions on how attempt to resolve your router issues. You can access this by selecting the hyper link above. Select Find and fix Internet issues.


I hope you find this helpful have a wonderful day!


James, AT&T Community Specialist

Tutor

 • 

8 Messages

5 years ago

Except it isn't **MY ROUTER** it is YOUR server. These auto replies really miss the mark sometimes. And no - you support tool DOES NOT address this issue. A tool that looks in the wrong places doesn't find the answer.

The attached graphic clearly shows where the problem is - and it is one of your servers, between two of your other servers. SO how you think that some how makes the problem my router is beyond me - why I HOPE that your reply was an auto reply, if it was a real person, just wow...

Tutor

 • 

3 Messages

5 years ago

Hello,

Did you ever get a resolution to this? I'm seeing 80% of packets loss at 192.205.32.210 as well.

 

  3.|-- 76-246-8-1.lightspeed.snm  0.0%    10    3.4  41.0   2.7 140.4  51.4

  4.|-- 71.148.184.37              0.0%    10    2.2   2.3   2.0   2.6   0.2

  5.|-- 71.145.1.52                0.0%    10    2.8   2.8   2.4   4.2   0.5

  6.|-- 12.83.39.209               0.0%    10    2.8   4.7   2.8   6.2   1.3

  7.|-- 12.122.114.5               0.0%    10    6.7   6.5   4.9   8.1   1.1

  8.|-- 192.205.32.210            80.0%    10    5.7   5.7   5.6   5.7   0.1

 

JefferMC

ACE - Expert

 • 

31K Messages

5 years ago

There is not necessarily anything wrong with 192.205.32.210  just because it didn't send back an error when the ICMP packet reached it with an expired TTL.  As long as any further hop responds at 100%, then it passed 100% of the packets through to it for it to have responded.

 

Tutor

 • 

8 Messages

5 years ago

So then why does it cause it all the jitter, timewarping and lag when actually playing games? Or is that you are throttling back certain traffic intentionally? Other wise - why aren't THE OTHERS doing the same thing? If it common, then all of them should be doing it, or else it is something either faulty or intentional on this particular hop.

Tutor

 • 

8 Messages

5 years ago

No real replies, Just "Oh, your local modem needs updated" or "Run the local troubleshooter", or the latest excuse of how it isn't really doing anything wrong...

I think the reality of it is they are throttling service to World of Tanks intentionally to save bandwidth for other uses.

JefferMC

ACE - Expert

 • 

31K Messages

5 years ago


@tkremin wrote:

...I think the reality of it is they are throttling service to World of Tanks intentionally to save bandwidth for other uses.


Do you have any idea how little bandwidth World of Tanks uses compared to streaming videos?  World of Tanks seems to do some  geographic based routing which seems to cause problems occasionally as packets that should go to, say, Canada, are routed to, for example, Spain, due to errors with the World of Tanks' network routing information.

 

JefferMC

ACE - Expert

 • 

31K Messages

5 years ago


@tkremin wrote:

So then why does it cause it all the jitter, timewarping and lag when actually playing games? ...


It does not.  Have you heard the term "coincidence?"  Or "correlation does not imply causation?"

 

Traceroute sends out packets that deliberately cause error conditions at remote routers and processes the error returns.  Error returns are not processed as swiftly or as easily as normal forwarding and the rate of them that a busy network router responds to with the error report is often limited (per RFC), especially on a busy router.  The fact that a router does not respond to a timed-out ICMP message does not necessarily mean that it is not healthy, or is doing anything wrong.  In combination with other information, it may indicate an issue.  However, since your traceroute showed responses from later hops, how do you think those later hops got the packets to respond to?  How do you think the responses got back to you?  

 

You decided it is causing the "jitter" and "timewarping."  But I don't think you have enough information to make that determination.  And your game vendor doesn't have the interest in finding out the real reason if they can get you off the phone by simply blaming your ISP.

 

 

Tutor

 • 

8 Messages

5 years ago

Yes, later hops are getting packets - ABOUT 20-30% of them - It isn't suddenly going back to no packet loss. It isn't dropping 100%. Did you even look at the graphic, or are you just doing "auto-excuses"?  You seem smart, but sure don't pick up details you don't want to see (or really explain) very well, do you?

ANd no, correlation isn't causation, but to an educated mind that actually WANTS to fix problems, it is one heck of a place to start looking. And when performance is continuously and directly correlated (as in the packet loss varies, and so does game performance in a direct relationship - game performance is good when only dropping 30-50% or less (only early morning weekdays, and then as performance degrades, Amazingly "coincidentally" does the drop packet rate ALWAYS AT THAT LOCATION.).  SO you are really going to go back to the same lame excuse that the tobacco industry used to say smoking isn't hazardous to health in humans? After all, all there is CORRELATORY evidence, no causal experimentation has ever been done. (I teach statistics and research methods, so make sure you REALLY want to go down that route of lame excuses...)

Tutor

 • 

8 Messages

5 years ago

Oh, and the vendor actually spends an incredible amount of time looking and trying to help. SO again, don't pass the buck.

The packet loss is NOT at my equipment or my router, and it is NOT at THEIR server. And amazingly, the community answers all point to AT&T as a major issue with users of OTHER ISP having far less issues.

SO what you are really saying is that you want all WoT players to drop you as an ISP? One of the largest on line games around? MAybe you are right and it is time to drop you as a my ISP.

Not finding what you're looking for?
New to AT&T Community?
New to the AT&T Community? Start by visiting the Community How-To.
New to the AT&T Community?
Visit the Community How-To.