LebGeeks
You are not logged in.
- Topics: Active • Unanswered
Pages: 1
Topic closed
#1 June 24 2005
- recon1025
- Member
High latency in WorldofWarcraft thanks to crappy routes
Greetings,
I'm not satisfied with the latency readout from terranet, It's affecting World of Warcraft gameplay. Getting an average of 800-1000ms which is not acceptable for games that require a very low latency. Anyway, I was wondering if you good folks would be nice enough to tracert or traceroute(on linux) to us.logon.worldofwarcraft.com and paste your results, here's mine:
traceroute to us.logon.worldofwarcraft.com (12.129.232.112), 30 hops max, 38 byte packets
1 172.16.206.1 (172.16.206.1) 45.599 ms 51.390 ms 60.702 ms
2 192.168.108.30 (192.168.108.30) 69.671 ms 60.425 ms 56.191 ms
3 ssg.terra.net.lb (212.98.136.18) 44.316 ms 49.282 ms 69.071 ms
4 core-2.terra.net.lb (212.98.136.55) 63.689 ms 37.789 ms 60.080 ms
5 rev-212-98-146-34.terra.net.lb (212.98.146.34) 89.911 ms 52.702 ms 52.557 ms
6 66-178-4-9.reverse.newskies.net (66.178.4.9) 682.453 ms 687.291 ms 670.456 ms
7 rtr-cor01-vlan2.man.newskies.net (66.178.0.81) 665.929 ms 681.548 ms 714.665 ms
8 500.POS4-3.GW3.DCA8.ALTER.NET (157.130.47.117) 671.180 ms 631.074 ms 631.463 ms
9 0.so-4-0-0.XL2.DCA8.ALTER.NET (152.63.37.34) 707.919 ms 680.672 ms 743.271 ms
10 0.so-6-0-0.XL2.DCA5.ALTER.NET (152.63.38.150) 664.444 ms 652.698 ms 706.546 ms
11 0.so-7-0-0.BR1.DCA5.ALTER.NET (152.63.43.177) 645.707 ms 663.558 ms 644.829 ms
12 204.255.169.2 (204.255.169.2) 655.574 ms 652.189 ms 697.425 ms
13 tbr1-p011701.wswdc.ip.att.net (12.123.9.114) 755.655 ms 734.010 ms 721.912 ms
MPLS Label=32418 CoS=5 TTL=1 S=0
14 tbr1-cl4.sl9mo.ip.att.net (12.122.10.30) 718.650 ms 723.653 ms 738.635 ms MPLS Label=32429 CoS=5 TTL=1 S=0
15 tbr1-cl2.sffca.ip.att.net (12.122.10.42) 721.526 ms 805.620 ms 702.793 ms MPLS Label=32358 CoS=5 TTL=1 S=0
16 gar3-p370.sffca.ip.att.net (12.123.13.161) 719.404 ms 708.652 ms 767.259 ms
17 mdf1-gsr12-2-pos-7-0.lax1.attens.net (12.122.255.254) 720.787 ms 801.720 ms *
18 mdf1-bi8k-1-eth-2-1.lax1.attens.net (12.129.192.250) 741.516 ms 754.034 ms 742.519 msI'm pretty confident once the ISPs in lebanon start realising that their customers are also very concerned about their latency and not just the bandwidth, they'll start improving their routes.
Just a quick rundown of the hops, hop 1 and 2 are GDS they are the middle man, they link you the customer to the ISP whichever one of the three you decide (terra, cyberia, idm) 3, 4 and 5 are all terranet as the names imply. 6 is what im concerned about thats what terranet gets its internet from at least for its residential customers, they do have better providers than newskies which give much lower latency because they use fiberoptics unlike new crappy skies which is a satellite link , satellites are really bad for latency if u want low latency u need fiberoptics and thats exactly what terranet doesnt give to its residential broadband customers, unless u got $500-$2000 to shed a month then you'll enjoy their fiberoptics with your dedicated line. I feel this is completly unacceptable, they limit your sessions to 20 concurrent, they always have downtime and problems, and they charge 200/month for a useless 512 and on top of that through a satellite connection!? I'd really love to see what IDM and Cyberia residential customers(on shared connections) are getting from traceroute us.logon.worldofwarcraft.com
P.S: I didnt post the remainder of the traceroute because all the remaining hops were firewalled, once it hits us.logon.worldofwarcraft.com it reaches 1000-1300 depending on time of the day, that's a second of lag because latency is measured in ms(millisecond)
Thanks for reading this lengthy post.
#2 June 24 2005
- mahdoum
- Member
Re: High latency in WorldofWarcraft thanks to crappy routes
interesting, why not inform terranet about it (not the customer service), someone high up
#3 June 24 2005
- recon1025
- Member
Re: High latency in WorldofWarcraft thanks to crappy routes
interesting, why not inform terranet about it (not the customer service), someone high up
If I had a penny for everytime I've talked to people in charge and not customer service at terranet i'd be one rich mofo!
#4 June 24 2005
- rolf
- Member
Re: High latency in WorldofWarcraft thanks to crappy routes
[root@summer root]# traceroute us.logon.worldofwarcraft.com
traceroute: Warning: us.logon.worldofwarcraft.com has multiple addresses; using 12.129.232.115
traceroute to us.logon.worldofwarcraft.com (12.129.232.115), 30 hops max, 38 byte packets
1 172.16.206.1 (172.16.206.1) 32.615 ms 36.149 ms 34.442 ms
2 192.168.108.30 (192.168.108.30) 32.983 ms 36.324 ms 34.481 ms
3 hsi.idm.net.lb (194.126.16.163) 56.940 ms 39.151 ms 44.202 ms
4 cisco6.idm.net.lb (193.227.162.193) 39.741 ms 38.417 ms 32.939 ms
5 Cisco8.idm.net.lb (193.227.162.225) 40.456 ms 72.156 ms 54.762 ms
6 cisco.idm.net.lb (194.126.16.106) 41.169 ms 44.899 ms 56.238 ms
7 63.218.109.61 (63.218.109.61) 200.207 ms 63.218.109.45 (63.218.109.45) 194.624 ms 63.218.109.29 (63.218.109.29) 175.872 ms
8 bpr1-so-7-3-0.VirginiaEquinix.savvis.net (208.173.50.245) 179.621 ms 188.918 ms 194.219 ms
9 cpr2-pos-4-0.VirginiaEquinix.savvis.net (206.24.227.61) 190.428 ms 206.975 ms cpr1-pos-4-0.VirginiaEquinix.savvis.net (206.24.227.57) 186.717 ms
10 dcr2-so-3-2-0.Washington.savvis.net (206.24.238.217) 183.766 ms dcr1-so-4-2-0.Washington.savvis.net (206.24.238.97) 187.292 ms 187.320 ms
11 bcs2-so-1-0-0-500.Washington.savvis.net (204.70.192.182) 211.539 ms bcs1-so-5-0-0-500.Washington.savvis.net (204.70.192.170) 190.947 ms bcs2-so-1-3-0-500.Washington.savvis.net (204.70.192.166) 221.544 ms
MPLS Label=112640 CoS=3 TTL=1 S=0
12 dcr1-so-3-0-0.Atlanta.savvis.net (204.70.192.53) 196.216 ms dcr2-so-7-2-0.Atlanta.savvis.net (204.70.192.57) 256.173 ms dcr1-so-3-0-0.Atlanta.savvis.net (204.70.192.53) 205.565 ms
13 dcr1-as0-0.Atlanta.savvis.net (204.70.192.41) 199.547 ms tbr1-cl1.dlstx.ip.att.net (12.122.2.89) 259.266 ms dcr1-as0-0.Atlanta.savvis.net (204.70.192.41) 216.920 ms
14 tbr1-cl2.la2ca.ip.att.net (12.122.10.50) 256.206 ms cw-gw.attga.ip.att.net (192.205.32.117) 199.195 ms tbr1-cl1.dlstx.ip.att.net (12.122.2.89) 248.933 ms
MPLS Label=32227 CoS=3 TTL=1 S=0
15 tbr2-p013702.attga.ip.att.net (12.123.20.254) 249.185 ms gbr6-p100.la2ca.ip.att.net (12.122.11.142) 255.933 ms tbr2-p013702.attga.ip.att.net (12.123.20.254) 253.950 ms
MPLS Label=32514 CoS=3 TTL=1 S=0
16 tbr1-cl1.dlstx.ip.att.net (12.122.2.89) 254.556 ms gbr6-p100.la2ca.ip.att.net (12.122.11.142) 239.706 ms gar3-p370.la2ca.ip.att.net (12.123.28.198) 262.479 ms
17 tbr1-cl2.la2ca.ip.att.net (12.122.10.50) 249.774 ms gar3-p370.la2ca.ip.att.net (12.123.28.198) 262.116 ms tbr1-cl2.la2ca.ip.att.net (12.122.10.50) 255.129 ms
MPLS Label=32317 CoS=3 TTL=1 S=0
18 gbr6-p100.la2ca.ip.att.net (12.122.11.142) 250.252 ms mdf1-bi8k-2-eth-2-2.lax1.attens.net (12.129.192.114) 284.319 ms gbr6-p100.la2ca.ip.att.net (12.122.11.142) 250.273 ms
MPLS Label=738 CoS=3 TTL=1 S=0
19 * mdf1-bi8k-2-eth-2-2.lax1.attens.net (12.129.192.114) 268.742 ms gar3-p370.la2ca.ip.att.net (12.123.28.198) 259.656 ms
20 * mdf1-gsr12-1-pos-7-0.lax1.attens.net (12.122.255.250) 240.430 ms 239.178 ms
21 * * mdf1-bi8k-2-eth-2-2.lax1.attens.net (12.129.192.114) 266.693 ms
22 * * *
23 * * *
24 *
-----------
I already told you guys, get IDM!
I have to add that I did not try an online game with IDM yet.
#5 June 24 2005
- rolf
- Member
Re: High latency in WorldofWarcraft thanks to crappy routes
interesting, why not inform terranet about it (not the customer service), someone high up
Terranet use a satellite backbone (check newskies.com), because of that you cant get no latency under 500ms for any site outside lebanon.
#6 June 25 2005
- darkstar
- Member
Re: High latency in WorldofWarcraft thanks to crappy routes
[root@summer root]# traceroute us.logon.worldofwarcraft.com
traceroute: Warning: us.logon.worldofwarcraft.com has multiple addresses; using 12.129.232.115
traceroute to us.logon.worldofwarcraft.com (12.129.232.115), 30 hops max, 38 byte packets
1 172.16.206.1 (172.16.206.1) 32.615 ms 36.149 ms 34.442 ms
2 192.168.108.30 (192.168.108.30) 32.983 ms 36.324 ms 34.481 ms
3 hsi.idm.net.lb (194.126.16.163) 56.940 ms 39.151 ms 44.202 ms
4 cisco6.idm.net.lb (193.227.162.193) 39.741 ms 38.417 ms 32.939 ms
5 Cisco8.idm.net.lb (193.227.162.225) 40.456 ms 72.156 ms 54.762 ms
6 cisco.idm.net.lb (194.126.16.106) 41.169 ms 44.899 ms 56.238 ms
7 63.218.109.61 (63.218.109.61) 200.207 ms 63.218.109.45 (63.218.109.45) 194.624 ms 63.218.109.29 (63.218.109.29) 175.872 ms
8 bpr1-so-7-3-0.VirginiaEquinix.savvis.net (208.173.50.245) 179.621 ms 188.918 ms 194.219 ms
9 cpr2-pos-4-0.VirginiaEquinix.savvis.net (206.24.227.61) 190.428 ms 206.975 ms cpr1-pos-4-0.VirginiaEquinix.savvis.net (206.24.227.57) 186.717 ms
10 dcr2-so-3-2-0.Washington.savvis.net (206.24.238.217) 183.766 ms dcr1-so-4-2-0.Washington.savvis.net (206.24.238.97) 187.292 ms 187.320 ms
11 bcs2-so-1-0-0-500.Washington.savvis.net (204.70.192.182) 211.539 ms bcs1-so-5-0-0-500.Washington.savvis.net (204.70.192.170) 190.947 ms bcs2-so-1-3-0-500.Washington.savvis.net (204.70.192.166) 221.544 ms
MPLS Label=112640 CoS=3 TTL=1 S=0
12 dcr1-so-3-0-0.Atlanta.savvis.net (204.70.192.53) 196.216 ms dcr2-so-7-2-0.Atlanta.savvis.net (204.70.192.57) 256.173 ms dcr1-so-3-0-0.Atlanta.savvis.net (204.70.192.53) 205.565 ms
13 dcr1-as0-0.Atlanta.savvis.net (204.70.192.41) 199.547 ms tbr1-cl1.dlstx.ip.att.net (12.122.2.89) 259.266 ms dcr1-as0-0.Atlanta.savvis.net (204.70.192.41) 216.920 ms
14 tbr1-cl2.la2ca.ip.att.net (12.122.10.50) 256.206 ms cw-gw.attga.ip.att.net (192.205.32.117) 199.195 ms tbr1-cl1.dlstx.ip.att.net (12.122.2.89) 248.933 ms
MPLS Label=32227 CoS=3 TTL=1 S=0
15 tbr2-p013702.attga.ip.att.net (12.123.20.254) 249.185 ms gbr6-p100.la2ca.ip.att.net (12.122.11.142) 255.933 ms tbr2-p013702.attga.ip.att.net (12.123.20.254) 253.950 ms
MPLS Label=32514 CoS=3 TTL=1 S=0
16 tbr1-cl1.dlstx.ip.att.net (12.122.2.89) 254.556 ms gbr6-p100.la2ca.ip.att.net (12.122.11.142) 239.706 ms gar3-p370.la2ca.ip.att.net (12.123.28.198) 262.479 ms
17 tbr1-cl2.la2ca.ip.att.net (12.122.10.50) 249.774 ms gar3-p370.la2ca.ip.att.net (12.123.28.198) 262.116 ms tbr1-cl2.la2ca.ip.att.net (12.122.10.50) 255.129 ms
MPLS Label=32317 CoS=3 TTL=1 S=0
18 gbr6-p100.la2ca.ip.att.net (12.122.11.142) 250.252 ms mdf1-bi8k-2-eth-2-2.lax1.attens.net (12.129.192.114) 284.319 ms gbr6-p100.la2ca.ip.att.net (12.122.11.142) 250.273 ms
MPLS Label=738 CoS=3 TTL=1 S=0
19 * mdf1-bi8k-2-eth-2-2.lax1.attens.net (12.129.192.114) 268.742 ms gar3-p370.la2ca.ip.att.net (12.123.28.198) 259.656 ms
20 * mdf1-gsr12-1-pos-7-0.lax1.attens.net (12.122.255.250) 240.430 ms 239.178 ms
21 * * mdf1-bi8k-2-eth-2-2.lax1.attens.net (12.129.192.114) 266.693 ms
22 * * *
23 * * *
24 *
-----------I already told you guys, get IDM!
I have to add that I did not try an online game with IDM yet.
Wow look at the difference in latency between terra and idm.
#7 June 25 2005
- rolf
- Member
Re: High latency in WorldofWarcraft thanks to crappy routes
recon you can switch from terra to IDM for free. That's what I did. Just talk to the guy who did the installation for you ("your dealer"). If you dont have his number maybe phone GDS and ask what is to be done, or maybe IDM can help you too.
#8 June 29 2005
- recon1025
- Member
Re: High latency in WorldofWarcraft thanks to crappy routes
Yo rolf, your traceroute feedback is greatly appreciated. It's amazing how low the latency with IDM is, btw terranet only puts its residential broadband customers on the newskies satellite link, i noticed late at night they route the broadband customers to their fiber optic (for load balancing) links but the lowest latency ive seen where in the 500s and thats once in a bluemoon, IDM definatly has more than im asking for, i mean 200ms is still high for first person shooter games but for games like wow its gonna be kickass, thanks a lot rolf!
Pages: 1
Topic closed