trace route is this good or bad

[Mugz.Ds]

traceroute to 66.165.90.2 (66.165.90.2), 30 hops max, 40 byte packets
 1  66.230.207.57 (66.230.207.57)  0.287 ms  0.270 ms  0.259 ms
 2  e17-ss1.dr6.as30217.net (84.40.24.133)  0.637 ms  0.897 ms  1.163 ms
 3  e3-1.co2.as30217.net (84.40.24.81)  0.451 ms  0.460 ms  0.570 ms
 4  te-1-4.car4.Tampa1.Level3.net (4.71.2.13)  0.573 ms  0.636 ms  0.705 ms
 5  ae-14-14.car1.Tampa1.Level3.net (4.69.133.57)  18.666 ms  18.729 ms  18.812 ms
 6  ae-2-5.bar1.Tampa1.Level3.net (4.69.133.50)  0.698 ms  0.623 ms  0.715 ms
 7  ae-6-6.ebr2.Atlanta2.Level3.net (4.69.137.114)  29.526 ms  29.642 ms  29.633 ms
 8  ae-3.ebr2.Chicago1.Level3.net (4.69.132.73)  37.898 ms  38.008 ms  37.339 ms
 9  ae-4-4.car2.StLouis1.Level3.net (4.69.132.189)  43.732 ms  43.305 ms  43.697 ms
10  Level3GigE.cybercon.com (63.208.32.186)  53.609 ms  53.406 ms  51.576 ms
11   (66.165.90.2)  97.285 ms  97.262 ms  97.235 ms

[reaper]

you didn't drop any packets, that's good. try a different server. that one is pretty far away.  or maybe another isp will be faster.

sometimes traceroutes add more time, than what the game would see.  because the router processor has to work with the packet, because the time-to-live was expired, instead of just being sent through router hardware very quickly, to the destination.  but i'm guessing the game is the same, 90ms on that server.  so maybe later it will be better, sometimes the packet gets stuck in a queue, which adds delay.

[QwazyWabbit]

11 hops is pretty good. I am 15 hops away from my favorite server.

I don't know where Reaper gets the idea you didn't drop any packets, the traceroute doesn't include that information.
If you get * * * it doesn't mean you lost frames, it means the router at that hop doesn't process traceroute frames of that type or the host is unreachable with that protocol. Many ISPs block ICMP ECHO frames at their borders to prevent abuse. Linux traceroute uses UDP packets IIRC, it doesn't use ICMP ping frames so the profile will be similar with the UDP frames in game. Client frames are frequent and small, server downlink frames are larger, probably 20 or 40 bytes vs 200 or 400 depending on the game action.

The ping profile is fairly flat, your ping is under 1 ms until you get into level3.net but they are a major backbone carrier and the ping will vary with time of day. Notice Tampa1 had a low ping at that time.

Remember, the return frame from a ping is under no obligation to follow the exact reverse path back to you as the outbound frame.

Those intermediate hops are excellent for your ISP. I wouldn't change a thing.

The best indicator of the path between you and the server is the netgraph in the game. If it's low, green and flat with minimal spikes, you are getting good performance.

[Mugz.Ds]

thanks guys.... I keep getting phone jacked during the middle of the games on a regular basis now. It never use to happen b4. When I leave the game I do a speed test and I'm getting my full 10mb. And since I'm a pc nub It's confusing.   

[QwazyWabbit]

If anything, with the 45ms jump in ping between hops 10 and 11 I would suspect an oversubscribed server or conjestion in their network.

[reaper]

the traceroute displayed delay for each hop, everytime, that means you didn't drop a packet in the traceroute.  during problems these would be the first packet to drop, but a couple packets isn't a good indication of what's going on, when you can sends thousands a second.


the phone jack is bad, it means you dropped packets, when there is an issue, or networks are to heavily oversubscribed, you can drop packets, which is obviously bad.  by nature the internet is packet switched, anyone can talk to anyone for the most part, big pipes can send traffic to smaller pipes, so delay can be added, or packets can be dropped when things get to backed up.

anyways, try a different server see if the netgraph is any better there.

[Shovel.Ds]

traceroute to 66.165.90.2 (66.165.90.2), 30 hops max, 40 byte packets
 1  66.230.207.57 (66.230.207.57)  0.287 ms  0.270 ms  0.259 ms
 2  e17-ss1.dr6.as30217.net (84.40.24.133)  0.637 ms  0.897 ms  1.163 ms
 3  e3-1.co2.as30217.net (84.40.24.81)  0.451 ms  0.460 ms  0.570 ms
 4  te-1-4.car4.Tampa1.Level3.net (4.71.2.13)  0.573 ms  0.636 ms  0.705 ms
 5  ae-14-14.car1.Tampa1.Level3.net (4.69.133.57)  18.666 ms  18.729 ms  18.812 ms
 6  ae-2-5.bar1.Tampa1.Level3.net (4.69.133.50)  0.698 ms  0.623 ms  0.715 ms
 7  ae-6-6.ebr2.Atlanta2.Level3.net (4.69.137.114)  29.526 ms  29.642 ms  29.633 ms
 8  ae-3.ebr2.Chicago1.Level3.net (4.69.132.73)  37.898 ms  38.008 ms  37.339 ms
 9  ae-4-4.car2.StLouis1.Level3.net (4.69.132.189)  43.732 ms  43.305 ms  43.697 ms
10  Level3GigE.cybercon.com (63.208.32.186)  53.609 ms  53.406 ms  51.576 ms
11   (66.165.90.2)  97.285 ms  97.262 ms  97.235 ms

Mugz that routing is terrible seeing that you live in St. Louis and the server is in St. Louis. They are routing you to Tampa then Atlanta then Chicago then back to St. Louis. 

I will contact the data center and see if they can get you a better route but you may have to contact your isp with this tracert and tell them this is unacceptable. But lemme talk to the data center first, I'll let you know.

[Shovel.Ds]

Ok Mugz, I had the data center reverse the tracert back to your ip.
This was there response......

Below are your ticket details:
RE:66.165.90.2
by AoWC_DeadHeart 6/19/2008 1:51:33 PM
According to the reverse tracert we are seeing a solid 23 ping, and never leaving STL. There is nothing we can do about this tracert currently.


So I guess you should contact your isp and tell them this route is unacceptable.
11 hops to go a few miles in the same city is bullshit.
They can fix this if you make a stink. They do this shit to save money so they route you the cheapest way they can.
Like I said I had the same problem a couple of months ago. I went from NH to Michigan to Boston then Atlanta then Chi then STL. It was about 32 hops, they were able to fix from the data center but I guess this isnt the case for you...good luck bro and lemme know how you make out.
 

[reaper]

your're going from an Autonomous System owned by Desync, AS 30217, to level3, AS 3356, to cybercon AS 7393.  This is your route to the server. 

Desync picked this route because it has the fewest hops - hops being AS's.  if Desync peered directly with cybercon, you would go right there.  They probably do have a better route for you, through another provider besides level3, but the level3 route is being chosen because it's only 2 AS's away.  They can change that to another provider they peer with, based on high latency for the level3 route.

Level3 could also choose to increase their peering arrangements with cybercon, to provide better service.  Is it a money thing, it could be, but I doubt it, Level3 is really really big, they have a lot of leverage with other providers, and providers pay to use them as transit.  Probably desync peers with a few ISP's, and you can just use another route.  i guess you'll see how friendly they are to gamers.


Looks like your ISP also peers with Time Warner Telecom , AS 4323, maybe they can choose their TWTC route, and the route has less latency.  Where Qwest goes through Level3 to get to your ISP.

(TWTC route)
BGP routing table entry for 66.230.192.0/19, version 11179571
Paths: (2 available, best #1, table Default-IP-Routing-Table)
  Not advertised to any peer
  4323 30217, (aggregated by 30217 84.40.24.241)
    x.x.x.x x.x.x.x
      Origin incomplete, localpref 100, weight 303, valid, external, best
      Community: 283312179 283312629 283313176 283314630 283317129 283337248 4266460184 4266524675 4266590210 4266655945
  3356 30217, (aggregated by 30217 84.40.24.242)
    x.x.x.x from x.x..x
      Origin IGP, metric 0, localpref 100, weight 300, valid, external
xx-xx#show ip bgp 66.165.90.2
BGP routing table entry for 66.165.64.0/18, version 13047805
Paths: (1 available, best #1, table Default-IP-Routing-Table)
  Not advertised to any peer
  3356 7393
    x.x.x.x from x.x.x.x)
      Origin IGP, metric 0, localpref 100, weight 300, valid, external, best


sh ip bgp 66.230.207.57
BGP routing table entry for 66.230.192.0/19, version 666562796
Paths: (2 available, best #1, table Default-IP-Routing-Table)
  Not advertised to any peer
  3356 30217, (aggregated by 30217 84.40.24.242)
    205.171.0.216 (metric 2282) from 205.171.0.187 (205.171.0.187)
      Origin IGP, metric 10000, localpref 80, valid, internal, best
      Community: 209:888
      Originator: 205.171.0.216, Cluster list: 205.171.0.187, 205.171.0.219
  3356 30217, (aggregated by 30217 84.40.24.242)
    205.171.0.216 (metric 2282) from 205.171.0.188 (205.171.0.188)
      Origin IGP, metric 10000, localpref 80, valid, internal
      Community: 209:888
      Originator: 205.171.0.216, Cluster list: 205.171.0.187, 205.171.0.219

[Mugz.Ds]

Mugz that routing is terrible seeing that you live in St. Louis and the server is in St. Louis. They are routing you to Tampa then Atlanta then Chicago then back to St. Louis. 

I will contact the data center and see if they can get you a better route but you may have to contact your isp with this tracert and tell them this is unacceptable. But lemme talk to the data center first, I'll let you know.

 
 
Thanks Shovel and Reaper... I will call Charter I love to bitch to them anyway!!

[Mugz.Ds]

When I do a tracert from cmd to Mutant 74.54.186.226 all I get is over maximum 30 hops then everything times out.

[Mugz.Ds]

Just got off the phone w/ charter bastards said they can't do anything.   
all they care is that I'm getting my full 10mb speed that can't do anything about the routing.