Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Please review my trace routes


  • Please log in to reply
2 replies to this topic

#1 Wizho

Wizho

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:03:44 PM

Posted 16 May 2010 - 04:06 PM

Hi, recently I've been testing my connection very carefuly, it's cable internet at 6 Mbits down and 2 Mbits up. Most part of the day I play Worls of Warcraft, CS and Half-Life without any lag issue, actually my average latency in WoW is 130ms, and Xbox Live runs great, but something else bothers me.

In every trace route I do there's always a node that seems to be causing trouble, you will see that in the tracert logs I'll post next.
I live in Mexico, my ISP's carrier is Cogentco. Cogentco was very well known in the past for it's bad quality and high latency peaks in rush hours, at least tht's what I've heard.

Is this an issue? Should I worry about it?

Trace 1:
C:\Documents and Settings\>tracert www.google.com

Traza a la dirección www.l.google.com [66.102.7.104]
sobre un máximo de 30 saltos:

1 9 ms 11 ms 11 ms 201-167-56-1-cable.cybercable.net.mx [201.167.56.1]
2 8 ms 8 ms 11 ms 192.168.125.240
3 11 ms 11 ms 15 ms 201-167-126-10-cable.cybercable.net.mx [201.167.126.10]
4 24 ms 35 ms 27 ms 201-167-126-105-cable.cybercable.net.mx [201.167.126.105]
5 187 ms 200 ms 201 ms te3-2.ccr01.lrd01.atlas.cogentco.com [38.104.220.9]
6 82 ms 209 ms 207 ms te4-4.ccr01.sat01.atlas.cogentco.com [154.54.6.217]
7 60 ms 59 ms 59 ms te9-7.mpd02.lax01.atlas.cogentco.com [154.54.29.25]
8 56 ms 61 ms 60 ms te3-4.mpd01.lax05.atlas.cogentco.com [154.54.3.142]
9 59 ms 59 ms 60 ms google.lax05.atlas.cogentco.com [154.54.13.106]
10 64 ms 69 ms 58 ms 216.239.46.180
11 60 ms 60 ms 60 ms 72.14.239.246
12 60 ms 71 ms 59 ms lax04s01-in-f104.1e100.net [66.102.7.104]


Trace 2:
C:\Documents and Settings\>tracert www.yahoo.com

Traza a la dirección any-fp.wa1.b.yahoo.com [209.191.122.70]
sobre un máximo de 30 saltos:

1 22 ms 19 ms 17 ms 201-167-56-1-cable.cybercable.net.mx [201.167.56.1]
2 18 ms 22 ms 7 ms 192.168.125.240
3 12 ms 11 ms 12 ms 201-167-126-10-cable.cybercable.net.mx [201.167.126.10]
4 26 ms 23 ms 24 ms 201-167-126-105-cable.cybercable.net.mx [201.167.126.105]
5 25 ms 47 ms 23 ms te3-2.ccr01.lrd01.atlas.cogentco.com [38.104.220.9]
6 27 ms 51 ms 28 ms te4-4.ccr01.sat01.atlas.cogentco.com [154.54.6.217]
7 286 ms 280 ms 253 ms te7-4.mpd02.iah01.atlas.cogentco.com [154.54.29.37]
8 73 ms 226 ms 238 ms te9-3.mpd01.dfw01.atlas.cogentco.com [154.54.25.97]
9 121 ms 241 ms 224 ms te2-8.mpd01.dfw03.atlas.cogentco.com [154.54.7.38]
10 40 ms 59 ms 41 ms yahoo.dfw03.atlas.cogentco.com [154.54.10.138]
11 40 ms 40 ms 39 ms ae1-p111.msr2.mud.yahoo.com [216.115.104.103]
12 40 ms 40 ms 40 ms te-7-1.fab1-a-gdc.mud.yahoo.com [209.191.78.131]
13 38 ms 42 ms 38 ms te-8-1.bas-c2.mud.yahoo.com [68.142.193.7]
14 38 ms 39 ms 40 ms ir1.fp.vip.mud.yahoo.com [209.191.122.70]


Trace 3:
C:\Documents and Settings\>tracert www.bing.com

Traza a la dirección a134.g.akamai.net [72.246.54.27]
sobre un máximo de 30 saltos:

1 13 ms 10 ms 10 ms 201-167-56-1-cable.cybercable.net.mx [201.167.56.1]
2 9 ms 8 ms 7 ms 201-167-126-10-cable.cybercable.net.mx [201.167.126.10]
3 23 ms 23 ms 24 ms 201-167-126-105-cable.cybercable.net.mx [201.167.126.105]
4 37 ms 36 ms 25 ms te3-2.ccr01.lrd01.atlas.cogentco.com [38.104.220.9]
5 28 ms 40 ms 27 ms te4-4.ccr01.sat01.atlas.cogentco.com [154.54.6.217]
6 135 ms 234 ms 232 ms te7-4.mpd02.iah01.atlas.cogentco.com [154.54.29.37]
7 237 ms 238 ms 235 ms te9-3.mpd01.dfw01.atlas.cogentco.com [154.54.25.97]
8 239 ms 214 ms 214 ms te2-8.mpd01.dfw03.atlas.cogentco.com [154.54.7.38]
9 38 ms 40 ms 38 ms xo.dfw03.atlas.cogentco.com [154.54.12.46]
10 43 ms 44 ms 84 ms te1-0-0d0.cir1.dallas2-tx.us.xo.net [207.88.15.45]
11 42 ms 44 ms 42 ms ip65-47-204-46.z204-47-65.customer.algx.net [65.47.204.46]
12 42 ms 44 ms 43 ms a72-246-54-27.deploy.akamaitechnologies.com [72.246.54.27]


As you can see, no matter wich server I trace, thare's always "high" latency in at least 1 Cogentco node, this doesn't happen always, but it does most part of the times I do a tracert.
As I said before, WoW runs great, so does Xbox Live, VoIP, Ventrilo and downloads are flawless (actually I'm getting 30% more speed than I'm paying).
Do you guys think this is normal?
Thanks

Edited by Wizho, 16 May 2010 - 04:07 PM.


BC AdBot (Login to Remove)

 


#2 MrBruce1959

MrBruce1959

    My cat Oreo


  • BC Advisor
  • 6,377 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Norwich, Connecticut. in the USA
  • Local time:04:44 PM

Posted 17 May 2010 - 02:18 AM

It could be caused by high usage of the server you are connected to at different times of the day.

In otherwords the server is responding at a slower rate because it has a higher volume of users logged on at that particular time of the day.
Welcome to Bleeping Computer! :welcome:
New Members: Please click here for the Bleeping Computer Forum Board Rules
 
My Career Involves 37 Years as an Electronics Repair Technician, to Which I am Currently Retired From.

I Am Currently Using Windows 10 Home Edition.

As a Volunteer Staff Member of Bleeping Computer, the Help That I Proudly Provide Here To Our BC Forum Board Membership is Free of Charge. :wink:

#3 NpaMA

NpaMA

  • Members
  • 635 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Memphis, TN
  • Local time:04:44 PM

Posted 17 May 2010 - 09:06 AM

Although it could be due to congestion on that hop, it may be(and most likely is) just where that hop passes packets along instead of replying to them. Causing it to only reply to them when it "has time".

If that hop really was getting 200ms+ to pass the packets along, you wouldn't have any hops below that with less then 200ms. You getting to some sites in under 40ms, is pretty much proof about that. My ISP has one hop on their network that responds weird at times - sometimes over 300ms or timing out, but the connection is always good and 30ms or so. Some Cablevision(OOL) tracerts i've seen have like 5 "Request Timed Out."'s but still return low pings to the actual site.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users