Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I'm looking at the latency from my machine to a world of warcraft server.

Every hop while I am in Comcast's network is sub 15ms.

Then it hits ATT and goes to 60-70MS for the rest.

Why would it suddenly jump from 15 to 60 considering it's still in the same city?

Is there anything I can do about it?

G-Man

share|improve this question

migrated from serverfault.com Apr 18 '10 at 7:30

This question came from our site for professional system and network administrators.

add comment

3 Answers

up vote 2 down vote accepted

Congested connection = long packet queue = latency
There's usually no way to avoid this besides switching your connection; even then other ISPs might use the same Upstream ISP.

share|improve this answer
add comment

The inter-network link is slow. Not a damn thing you can do about it, short of switch ISPs.

share|improve this answer
    
Unless Comcast is hiddlenly throttling traffic again. –  geek Apr 18 '10 at 13:42
add comment

Remember that MPLS tagged networks report the ping time as the RTT for the virtual circuit. ICMP is also low priority, and, on a busy router can be dropped or delayed. Also, some routers enforce rate limiting and when ICMP gets over a certain threshhold, it'll drop/delay those packets as well.

Additionally, you could be experiencing an asymmetric route. Traffic that goes to that one router may return through a different route which may have more hops or congestion somewhere other than the path you see. So, when you hit that one AT&T router, their internal policies, or Comcast's route announcements may prefer a different ingress than the router the packet just exited.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.