Never the less I am still experencing 7-800 pings in WoW which makes it unplayable (prehaps that traffic is being groomed as JetPrez stated in another post.
here is a tracert to WoW's login server (a few hops from the actual server which isnt pingable)
Tracing route to us.logon.worldofwarcraft.com [12.129.224.117] over a maximum of 30 hops:
1 19 ms 26 ms 23 ms 10.5.128.1 2 28 ms * 21 ms 10.5.2.31 3 18 ms 18 ms 15 ms 10.5.1.2 4 53 ms 59 ms 49 ms 192.168.168.9 5 49 ms 41 ms 47 ms s66-76-195-41.chtnwv.ab.sta.suddenlink.net [66.7 6.195.41] 6 89 ms 69 ms 66 ms s66-76-168-9.bssr.suddenlink.net [66.76.168.9] 7 94 ms * 70 ms ge-6-22.car4.Washington1.Level3.net [4.79.170.89 ] 8 70 ms 69 ms 71 ms ae-3-89.edge1.Washington3.Level3.net [4.68.17.13 9] 9 70 ms 70 ms 71 ms att-level3-oc192.Washington1.Level3.net [209.244 .219.142] 10 136 ms 155 ms 167 ms tbr1.wswdc.ip.att.net [12.123.8.98] 11 132 ms 146 ms 147 ms tbr1.sl9mo.ip.att.net [12.122.10.30] 12 145 ms 146 ms 142 ms tbr2.sl9mo.ip.att.net [12.122.9.142] 13 147 ms 130 ms 151 ms tbr2.la2ca.ip.att.net [12.122.10.14] 14 135 ms 142 ms 131 ms 12.127.3.189 15 144 ms 147 ms 131 ms 12.122.255.74 16 152 ms 215 ms 196 ms mdf001c7613r0003-gig-10-1.lax1.attens.net [12.12 9.193.242]
Jay, I am also in Lebanon. I don't play WoW, but my wife does and she has the same problem as you regarding latency. Also, she is unable to patch the game now using Blizzard's P2P patcher (was working fine before), so we wonder if JetBroadband is blocking that as well.
Could be....we thought we had it bad with Charter, then Suddenlink. I wish BVU would take this franchise over. They already have fiber layed and internet service installed at all of the local schools...
Tracing route to us.logon.worldofwarcraft.com [12.129.224.117] over a maximum of 30 hops:
1 21 ms 9 ms 13 ms 10.5.128.1 2 14 ms 11 ms 10 ms 10.5.2.31 3 9 ms 17 ms 13 ms 10.5.1.2 4 51 ms 43 ms 47 ms 192.168.168.9 5 * 41 ms 39 ms s66-76-195-41.chtnwv.ab.sta.suddenlink.net [66.7 6.195.41] 6 64 ms 66 ms 63 ms s66-76-168-9.bssr.suddenlink.net [66.76.168.9] 7 66 ms 67 ms 66 ms ge-6-22.car4.Washington1.Level3.net [4.79.170.89 ] 8 * 68 ms 70 ms ae-3-89.edge1.Washington3.Level3.net [4.68.17.13 9] 9 75 ms 66 ms 89 ms att-level3-oc192.Washington1.Level3.net [4.68.12 7.154] 10 * * 129 ms tbr1.wswdc.ip.att.net [12.123.8.98] 11 130 ms 134 ms 130 ms tbr1.sl9mo.ip.att.net [12.122.10.30] 12 139 ms 148 ms 134 ms tbr2.sl9mo.ip.att.net [12.122.9.142] 13 * 130 ms 136 ms tbr2.la2ca.ip.att.net [12.122.10.14] 14 135 ms 135 ms 131 ms 12.127.3.189 15 130 ms 139 ms 134 ms 12.122.255.74 16 131 ms 134 ms 137 ms mdf001c7613r0003-gig-10-1.lax1.attens.net [12.12 9.193.242]
