Consolidated latency tracking and reporting

Support Forum Agent
As many people are aware, there have been some reports of in-game latency recently affecting customers on a few different ISPs from many different geo-locales. Tracking these issues can be problematic due to the nature of forums, in general, but having the data spread all over exacerbates the situation.

As such, we have removed the prior two threads from our sticky list and created this one with the hope that we will have a more efficient looking glass into complaints of excessive in-game latency. Interestingly enough, many people reporting problems actually had issues on their home computers or networks that could be resolved by standard troubleshooting and were unaware that the issue wasn't with their route or ISP, but with their own equipment and configuration.

Please follow all the steps outlined below prior to posting your information in this thread. This is very important. We do not want anyone to be posting here when they have an easily rectified situation, as this thread is not for troubleshooting... it is for information gathering purposes. It would be unfortunate to have an issue that could be fixed go overlooked. Tests run on a wireless LAN are automatically invalidated.

1) Bypass any wireless connections (Wireless LAN/WiFi/3G, etc.)
2) Contact your ISP to have them test your connection for stability and to check for any outstanding issues
3) Follow all the steps outlined here (please complete all steps fully): http://us.blizzard.com/support/article.xml?locale=en_US&articleId=21018


While there are many different causes of high ping times (high latency/lag) in-game, almost all of them are unable to be resolved by Blizzard, as the root causes almost always are external to our network. If the pathping/traceroute you run shows high latency or packet loss, the issue most likely lies on your home network, with your ISP, or the peers they lease backbone access through. At times, we can contact our provider to see if they can assist with issues like these, but normally those types of problems are best handled by your ISP's Network Operations Center. We would still like to know about them, if possible.

If you have performed all the troubleshooting listed above and are still experiencing issues, please post the information requested below in this thread. We can attempt to use these reports to isolate and verify specific issues.

To assist us in helping you or addressing your concerns, please quote the area between the lines below and fill them out fully in your reply. Approximate IPs (close enough for our purposes) for your realm can be found here: http://www.wowpedia.org/US_realm_list_by_datacenter
_______________________________________
1) ISP:
2) Location (State/Province):
3) Modem make and model:
4) Router make and model:
5) Approximate date issue was first noted:
6) Approximate time of day latency occurs:
7) Any special factors for consideration:
8) Detailed description of issue:
9) Results of pathping to your realm server:
_______________________________________

NOTE:
Here are the steps to run the Pathping command (Windows XP):

1) Click Start and then Run
2) Type "cmd" and press Enter
3) In the Command window (DOS prompt), type 'pathping xxx.xxx.xxx.xxx > C:\pathping.txt' (without the quotes where xxx.xxx.xxx.xxx is the IP to your realm) and press the Enter key.

Steps to run the Pathping command (Windows Vista/7)

1) Click Start and in the "Start Search" field type "cmd"
2) Right click on the CMD icon and select Run as - Administrator to start the Command window
3) In the Command window, type 'pathping xxx.xxx.xxx.xxx > C:\pathping.txt' (without the quotes where xxx.xxx.xxx.xxx is the IP to your realm) and press the Enter key.
________________________________________________
Account and Technical Services || Tues - Sat 645 - 1545 PST
Not seeing a resolution on the forums? Contact a Support Rep directly! - http://us.blizzard.com/en-us/company/about/contact.html

Experience is simply the name we give our mistakes.
Like the post? Comments or suggestions? Submit a survey here, please - http://www.surveymk.com/s/RMW9Y6X
Edited by BrianI on 1/29/2011 2:02 PM PST
85 Goblin Hunter
2025
Seems like this problem won't be going away for a lot of us Canadian customers anytime soon. I've just been searching and searching looking for as many different complaints and reports of extreme throttling. I myself am on a Cogeco connection mostly and have only experienced unplayable lag during peak times, but this weekend at a friends on Rogers it's been a nightmare. (hopefully I don't get the same random dc's at home but if I go through a Rogers network I just might!) Not only does WoW seem to be affected but other online games as well! This http://torrentfreak.com/rogers-bittorrent-throttling-experiment-goes-horribly-wrong-101213/ is an interesting read giving a bit of insight into one of the reasons these problems are happening.

It's pretty obvious a lot of our internet service providers have instituted systems to throttle anything that could be some sort of p2p traffic. Sadly the CRTC doesn't have any real power to do anything(not like they would anyway) and the Canadian ISPs can pretty much do anything they want as long as they tell us about it eventually and update their network management policy's(which Rogers said it just might end up doing to "fix" the problem on their end).

I have no doubt that Blizzard is trying to actively engage these companies to find a solution(and they probably will for something as big as WoW) but we'll be waiting a while. With the regional monopolies they all have there is no real incentive to make changes to their systems anytime soon. This goes to highlight the big problem we have in Canada us paying some of the highest prices for the worst high speed out there, and the way it is right now it's only going to get worse.
Support Forum Agent
We have been researching the issue in depth, and there are definitely some areas of concern. Blizzard would love to come to a common consensus with all parties involved.
________________________________________________
Account and Technical Services || Tues - Sat 645 - 1545 PST
Not seeing a resolution on the forums? Contact a Support Rep directly! - http://us.blizzard.com/en-us/company/about/contact.html

Experience is simply the name we give our mistakes.
Like the post? Comments or suggestions? Submit a survey here, please - http://www.surveymk.com/s/RMW9Y6X
85 Troll Druid
3960
1) ISP: Bell Aliant
2) Location (State/Province): Nova Scotia
3) Modem make and model: ActionTec [Couldn't find model]
4) Router make and model: [Couldn't find anything on the router]
5) Approximate date issue was first noted: Tuesday, January 25th (Started happening after I downloaded the newest update.
6) Approximate time of day latency occurs: High population times, 5pm est - 10pm est but even before and after those times my ping is still higher then normal.
7) Any special factors for consideration: Nope.
8) Detailed description of issue: When I get on during high population times my ping is over 450 consistently and does not go down, during low population times its in like mid 200's but that is still much higher then normal, by normal I mean under 150, which is what I always had before the new update.
9) Results of pathping to your realm server:


Tracing route to 206.18.148.172 over a maximum of 30 hops

0 Owner-PC [192.168.2.12]
1 . [192.168.2.1]
2 10.255.252.1
3 ge-0-0-0-2.dr01.sydn.ns.aliant.net [142.176.53.1]
4 te-0-6-0-0.cr01.hlfx.ns.aliant.net [142.166.181.93]
5 xe-2-1-0.cr02.stjh.nb.aliant.net [142.166.181.150]
6 so-9-0-0.dr02.fctn.nb.aliant.net [142.166.185.146]
7 204.101.4.177
8 bx2-ashburn_xe2-1-0.net.bell.ca [64.230.185.137]
9 12.86.243.33
10 cr84.wswdc.ip.att.net [12.122.134.126]
11 cr2.wswdc.ip.att.net [12.123.10.249]
12 cr1.cgcil.ip.att.net [12.122.18.21]
13 cr83.cgcil.ip.att.net [12.123.7.109]
14 gar4.cgcil.ip.att.net [12.122.133.205]
15 .attens.net [12.122.254.202]
16 63.240.130.206
17 * * *
Computing statistics for 400 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Owner-PC [192.168.2.12]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% . [192.168.2.1]
0/ 100 = 0% |
2 3ms 0/ 100 = 0% 0/ 100 = 0% 10.255.252.1
0/ 100 = 0% |
3 3ms 0/ 100 = 0% 0/ 100 = 0% ge-0-0-0-2.dr01.sydn.ns.aliant.net [142.176.53.1]
0/ 100 = 0% |
4 11ms 0/ 100 = 0% 0/ 100 = 0% te-0-6-0-0.cr01.hlfx.ns.aliant.net [142.166.181.93]
0/ 100 = 0% |
5 14ms 0/ 100 = 0% 0/ 100 = 0% xe-2-1-0.cr02.stjh.nb.aliant.net [142.166.181.150]
0/ 100 = 0% |
6 17ms 0/ 100 = 0% 0/ 100 = 0% so-9-0-0.dr02.fctn.nb.aliant.net [142.166.185.146]
0/ 100 = 0% |
7 39ms 0/ 100 = 0% 0/ 100 = 0% 204.101.4.177
0/ 100 = 0% |
8 --- 100/ 100 =100% 100/ 100 =100% bx2-ashburn_xe2-1-0.net.bell.ca [64.230.185.137]
0/ 100 = 0% |
9 --- 100/ 100 =100% 100/ 100 =100% 12.86.243.33
0/ 100 = 0% |
10 --- 100/ 100 =100% 100/ 100 =100% cr84.wswdc.ip.att.net [12.122.134.126]
0/ 100 = 0% |
11 --- 100/ 100 =100% 100/ 100 =100% cr2.wswdc.ip.att.net [12.123.10.249]
0/ 100 = 0% |
12 --- 100/ 100 =100% 100/ 100 =100% cr1.cgcil.ip.att.net [12.122.18.21]
0/ 100 = 0% |
13 --- 100/ 100 =100% 100/ 100 =100% cr83.cgcil.ip.att.net [12.123.7.109]
0/ 100 = 0% |
14 --- 100/ 100 =100% 100/ 100 =100% gar4.cgcil.ip.att.net [12.122.133.205]
0/ 100 = 0% |
15 --- 100/ 100 =100% 100/ 100 =100% 12-122-254-202.attens.net [12.122.254.202]
0/ 100 = 0% |
16 67ms 0/ 100 = 0% 0/ 100 = 0% 63.240.130.206

Trace complete.

At the time of the test my ping was around 180 on the server which is playable and not that bad.
Edited by Energyy on 1/29/2011 12:48 PM PST
85 Worgen Death Knight
0
1) Time Warner
2) North Carolina
3) Broadcom 802.11g network adapter
4) Netgear wgr614 v9 wireless g
5) Tuesday 25th after update.
6) Gets bad around 2-3 pm server time (Gorgonnash)
7) Generally intermittent, but I also get long periods of high latency.
8) Latency spiking from ~200 ms to 1000+.
9) Results of pathping to your realm server


Tracing route to 206.18.148.220 over a maximum of 30 hops

1 2 ms 7 ms 2 ms 192.168.1.1
2 15 ms 14 ms 14 ms cpe-075-190-128-001.carolina.res.rr.com [75.190.
128.1]
3 13 ms 11 ms 12 ms cpe-024-074-253-117.carolina.res.rr.com [24.74.2
53.117]
4 18 ms 18 ms 18 ms ge-5-1-0.rlghncpop-rtr1.southeast.rr.com [24.93.
64.26]
5 23 ms 24 ms 35 ms ae-3-0.cr0.dca10.tbone.rr.com [66.109.6.80]
6 28 ms 23 ms 26 ms ae-2-0.pr0.dca10.tbone.rr.com [66.109.6.169]
7 25 ms 25 ms 28 ms ix-5-1-0-0.tcore1.AEQ-Ashburn.as6453.net [66.198
.154.29]
8 34 ms 24 ms 28 ms if-2-2.tcore2.AEQ-Ashburn.as6453.net [216.6.87.1
]
9 70 ms 39 ms 24 ms 192.205.34.249
10 49 ms 49 ms 48 ms cr2.wswdc.ip.att.net [12.122.220.250]
11 48 ms 55 ms * cr1.cgcil.ip.att.net [12.122.18.21]
12 49 ms 59 ms 75 ms cr83.cgcil.ip.att.net [12.123.7.109]
13 47 ms 57 ms 46 ms gar4.cgcil.ip.att.net [12.122.133.205]
14 * * 57 ms 12-122-254-202.attens.net [12.122.254.202]
15 48 ms 49 ms 50 ms 63.240.130.202
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
85 Blood Elf Mage
3375
1) ISP: Resnet (resnet.buffalo.edu - Provided by University at Buffalo)
2) Location (State/Province): Buffalo, New York
3) Modem make and model: No idea.
4) Router make and model: No idea
5) Approximate date issue was first noted: January 16, 2011
6) Approximate time of day latency occurs: 27/7
7) Any special factors for consideration: This is the residency of the University that I attend, University at Buffalo. I've never experienced any in-game latency issues at this university until I returned after Christmas vacation on January 16, 2011. The last time I recall having a stable connection was December 15, 2011, the day I left for vacation.
8) Detailed description of issue: No matter what time of day, my latency is always a high red, a constantly 1k+ latency. I noticed upon logging in that it sometimes > 100 ms, but after a few seconds it jumps to red.
9) Results of pathping to your realm server:


Pathping Test 1

Tracing route to 199.107.6.250 over a maximum of 30 hops

0 Owner-PC.resnet.buffalo.edu [128.205.218.51]
1 l3sw-fillmore219-254.resnet.buffalo.edu [128.205.219.254] reports: Destination net unreachable.

Computing statistics for 25 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Owner-PC.resnet.buffalo.edu [128.205.218.51]
100/ 100 =100% |
1 --- 100/ 100 =100% 0/ 100 = 0% Owner-PC [0.0.0.0]

Trace complete.



Pathping Test 2

Tracing route to 199.107.6.252 over a maximum of 30 hops

0 Owner-PC.resnet.buffalo.edu [128.205.218.51]
1 l3sw-fillmore219-254.resnet.buffalo.edu [128.205.219.254] reports: Destination net unreachable.

Computing statistics for 25 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Owner-PC.resnet.buffalo.edu [128.205.218.51]
100/ 100 =100% |
1 --- 100/ 100 =100% 0/ 100 = 0% Owner-PC [0.0.0.0]

Trace complete.


By my pathping results, I noticed that it seems rather short compared to the one's I've seen submitted by other individuals encountering similar problems. Could this be a issue with my University, or have I simply done this incorrectly?

P.S: I've also come across users upon this forum from the same university claiming to be encountering this problem as well.
Edited by Charden on 1/29/2011 1:40 PM PST
Support Forum Agent
Charden,

01/29/2011 1:39 PMPosted by Charden
By my pathping results, I noticed that it seems rather short compared to the one's I've seen submitted by other individuals encountering similar problems. Could this be a issue with my University, or have I simply done this incorrectly?

P.S: I've also come across users upon this forum from the same university claiming to be encountering this problem as well.

It likely means your college is blocking ICMP, and traceroute, pathpings, and ping sessions will be unable to run.

Kildayen,

Please run those tests again after bypassing your wireless connection. You're even getting some latency to your first hop, which shouldn't be the case.
________________________________________________
Account and Technical Services || Tues - Sat 645 - 1545 PST
Not seeing a resolution on the forums? Contact a Support Rep directly! - http://us.blizzard.com/en-us/company/about/contact.html

Experience is simply the name we give our mistakes.
Like the post? Comments or suggestions? Submit a survey here, please - http://www.surveymk.com/s/RMW9Y6X
Edited by BrianI on 1/29/2011 2:05 PM PST
85 Tauren Shaman
6475
Im having exact same problem as Victrola.

8) Detailed description of issue: Consistent 200ms latency on any realm server. Upon connection to any Instance or Battleground, the latency spikes into the red at a displayed 2000 to 18000ms. Engaging any npc or pc in the instance/battleground causes the screen to freeze anywhere from 5s up to a minute. Following this it either catches up in a quick flash of actions, or disconnects outrigh
Edited by Peyotem on 1/29/2011 3:25 PM PST
Support Forum Agent
Peyotem,
Im having exact same problem as Victrola.

8) Detailed description of issue: Consistent 200ms latency on any realm server. Upon connection to any Instance or Battleground, the latency spikes into the red at a displayed 2000 to 18000ms. Engaging any npc or pc in the instance/battleground causes the screen to freeze anywhere from 5s up to a minute. Following this it either catches up in a quick flash of actions, or disconnects outrigh

I'm sorry to hear that. Please post the information requested after following the troubleshooting steps.
________________________________________________
Account and Technical Services || Tues - Sat 645 - 1545 PST
Not seeing a resolution on the forums? Contact a Support Rep directly! - http://us.blizzard.com/en-us/company/about/contact.html

Experience is simply the name we give our mistakes.
Like the post? Comments or suggestions? Submit a survey here, please - http://www.surveymk.com/s/RMW9Y6X
85 Dwarf Rogue
4410
1. Bell
2. Deep River, Ontario
3. Unsure
4. 2701HG-G 2Wire Gateway
5. Saturday, January 29th 2011 - 12:42 PM
6. All Day - Anywhere from 600 - 900 MS
7. No
8. Even though my latency is very high I have little to zero lag at all. Then it just spikes. 5-15 seconds at a time everything lags out and then catches up all at once. It will do this several times a minute all the time for the past several hours.
9.

Tracing route to 12.129.206.130 over a maximum of 30 hops

1 1 ms 1 ms 1 ms mymodem [192.168.2.1]
2 57 ms 54 ms 50 ms bas15-ottawa23_lo0_SYMP.net.bell.ca [64.230.197.
126]
3 59 ms 48 ms 48 ms bas15-ottawa23_GE1-0_115.net.bell.ca [64.230.164
.22]
4 64 ms 64 ms 64 ms bx2-ashburn_xe2-1-0.net.bell.ca [64.230.185.137]

5 86 ms 72 ms 70 ms 12.86.243.37
6 137 ms 135 ms 137 ms 12.122.134.126
7 * 127 ms 131 ms cr2.wswdc.ip.att.net [12.123.10.249]
8 148 ms 148 ms 152 ms cr1.cgcil.ip.att.net [12.122.18.21]
9 142 ms 140 ms 143 ms cr2.dvmco.ip.att.net [12.122.31.85]
10 137 ms 133 ms 135 ms cr1.slkut.ip.att.net [12.122.30.25]
11 134 ms 131 ms 129 ms cr2.la2ca.ip.att.net [12.122.30.30]
12 134 ms 129 ms 127 ms cr84.la2ca.ip.att.net [12.123.30.249]
13 162 ms 162 ms 146 ms gar5.la2ca.ip.att.net [12.122.129.25]
14 133 ms 135 ms 135 ms 12.122.255.74
15 152 ms 153 ms 148 ms 12.129.193.242
16 12.129.211.34 reports: Destination net unreachable.

Trace complete.

Edited by Dreyfen on 1/29/2011 4:57 PM PST
85 Orc Warrior
11655
@ Dreyfen - I believe the latency meter in WoW does not show your real time latency but shows your average latency over a certain period of time (15 minutes maybe?)
85 Orc Warrior
11655
1) ISP: Access Communications
2) Location (State/Province): Regina, Saskatchewan
3) Modem make and model: Arris WTM552
4) Router make and model: ^ all in one
5) Approximate date issue was first noted: Tuesday, January 25th
6) Approximate time of day latency occurs: 200's during slow times, 400 during peak times.
7) Any special factors for consideration:
8) Detailed description of issue: Latency issues. And disconnects in raids.
9) Results of pathping to your realm server:


Tracing route to 206.18.149.35 over a maximum of 30 hops

0 John-PC.accesscomm.ca [172.18.30.10]
1 10.12.0.1
2 internet-7606.accesscomm.ca [24.72.99.249]
3 66.46.98.209
4 12.89.67.241
5 cr83.cgcil.ip.att.net [12.123.7.14]
6 gar4.cgcil.ip.att.net [12.122.133.205]
7 12-122-254-202 begin_of_the_skype_highlighting              12-122-254-202      end_of_the_skype_highlighting.attens.net [12.122.254.202]
8 63.240.130.206
9 * * *
Computing statistics for 200 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 John-PC.accesscomm.ca [172.18.30.10]
2/ 100 = 2% |
1 27ms 2/ 100 = 2% 0/ 100 = 0% 10.12.0.1
0/ 100 = 0% |
2 34ms 3/ 100 = 3% 1/ 100 = 1% internet-7606.accesscomm.ca [24.72.99.249]
0/ 100 = 0% |
3 79ms 2/ 100 = 2% 0/ 100 = 0% 66.46.98.209
1/ 100 = 1% |
4 92ms 4/ 100 = 4% 1/ 100 = 1% 12.89.67.241
0/ 100 = 0% |
5 --- 100/ 100 =100% 97/ 100 = 97% cr83.cgcil.ip.att.net [12.123.7.14]
0/ 100 = 0% |
6 --- 100/ 100 =100% 97/ 100 = 97% gar4.cgcil.ip.att.net [12.122.133.205]
0/ 100 = 0% |
7 --- 100/ 100 =100% 97/ 100 = 97% 12-122-254-202.attens.net [12.122.254.202]
0/ 100 = 0% |
8 79ms 3/ 100 = 3% 0/ 100 = 0% 63.240.130.206

Trace complete.

-> If someone could respond to me that would be great. My pathping looks especially bad compared to everyone elses. Should I contact my ISP?
Edited by Kelthice on 1/29/2011 5:21 PM PST
85 Draenei Shaman
5710
Can't run a fresh tracert for another hour or so since I need one of the wired systems to do it on, but just in perusing both this thread and the 100 page one, the traces seem to be dying at very similar points. For example, I stopped counting after the 30th or so that is borking at the same point mine is (63.240.130.202). After so many hundreds of traces, it is clear that AT&T has issues.
85 Tauren Shaman
6475
1) ISP: Cable & Wireless Panama
2) Location (State/Province):Panama
3) Modem make and model: ZyXEL Prestige 600 series
4) Router make and model: Belkin N1 Wireless Router
5) Approximate date issue was first noted: January 2011
6) Approximate time of day latency occurs: 4:00pm-10:00pm
7) Any special factors for consideration:
8) Detailed description of issue: At 4:00pm I start getting 1-3k ms and it begans to increase until it gets to 20k, then I start to DC and after a few hours I cant even log on to my character :S. Also, when I enter BGs my latency instantly skyrockets to 28-30k ms and I get tons of DCs until the BG ends. The worst of all is that I lose like 3 or more hours of my life waiting to see if I can connect and nothing, so I come to this forum and see many people have had the same problem since october, PLEASE!!!
9) Results of pathping to your realm server:

Traza a 206.18.148.172 sobre caminos de 30 saltos como m ximo.

0 Diego-VAIO.Belkin [192.168.2.5]
1 192.168.2.1
2 link [192.168.1.1]
3 201.226.61.126
4 10.255.3.13
5 ge-1-0-0.bal1-int-1.ed1-agr-1.cwpanama.net [201.224.254.241]
6 * so-6-0-1.mia11.ip4.tinet.net [77.67.82.201]
7 so-2-1-0.atl11.ip4.tinet.net [89.149.184.21]
8 192.205.36.121
9 cr2.attga.ip.att.net [12.122.84.150]
10 cr1.nsvtn.ip.att.net [12.122.28.106]
11 cr2.nsvtn.ip.att.net [12.122.28.70]
12 cr1.cl2oh.ip.att.net [12.122.28.74]
13 cr1.cgcil.ip.att.net [12.122.2.205]
14 cr83.cgcil.ip.att.net [12.123.7.109]
15 gar4.cgcil.ip.att.net [12.122.133.205]
16 12-122-254-202.attens.net [12.122.254.202]
17 63.240.130.202
18 * * *
Procesamiento de estad¡sticas durante 425 segundos...
Edited by Peyotem on 1/30/2011 11:19 AM PST
85 Troll Druid
3960
01/29/2011 6:41 PMPosted by Peyotem

9) Results of pathping to your realm server: I followed instructions but it wont appear anything in the cmd.


The results are in pathping.txt at C:\pathping.txt
100 Pandaren Rogue
18905
1) ISP: Bell Sympatico
2) Location (State/Province): Ontario, Canada
3) Modem make and model: 2701HG-G 2Wire Gateway
4) Router make and model: 2701HG-G 2Wire Gateway
5) Approximate date issue was first noted: Approx . January 22
6) Approximate time of day latency occurs: 6pm EST - 12am
7) Any special factors for consideration: Lag escalates as time goes on
8) Detailed description of issue: Latency issues. And disconnects in raids.
9) Results of pathping to your realm server
Tracing route to 206.16.118.173 over a maximum of 30 hops

0 PC.gateway.2wire.net [192.168.2.21]
1 mymodem [192.168.2.1]
2 bas3-toronto48_lo0_SYMP.net.bell.ca [64.230.200.171]
3 agg1-toronto47_1-2-0_100.net.bell.ca [64.230.57.194]
4 bx5-chicagodt_xe1-0-0-0.net.bell.ca [64.230.186.242]
5 12.86.65.53
6 cr84.cgcil.ip.att.net [12.122.132.102]
7 cr2.cgcil.ip.att.net [12.123.7.250]
8 cr2.sl9mo.ip.att.net [12.122.2.22]
9 cr2.kc9mo.ip.att.net [12.122.28.89]
10 cr1.dlstx.ip.att.net [12.122.28.85]
11 cr1.phmaz.ip.att.net [12.122.28.182]
12 gar4.phmaz.ip.att.net [12.123.206.145]
13 12.122.255.106
14 mdf002c7613r0002-gig-12-1.phx1.attens.net [63.241.130.202]
15 * * *
Computing statistics for 350 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 PC.gateway.2wire.net [192.168.2.21]
0/ 100 = 0% |
1 7ms 0/ 100 = 0% 0/ 100 = 0% mymodem [192.168.2.1]
0/ 100 = 0% |
2 18ms 1/ 100 = 1% 1/ 100 = 1% bas3-toronto48_lo0_SYMP.net.bell.ca [64.230.200.171]
0/ 100 = 0% |
3 18ms 1/ 100 = 1% 1/ 100 = 1% agg1-toronto47_1-2-0_100.net.bell.ca [64.230.57.194]
0/ 100 = 0% |
4 33ms 1/ 100 = 1% 1/ 100 = 1% bx5-chicagodt_xe1-0-0-0.net.bell.ca [64.230.186.242]
0/ 100 = 0% |
5 98ms 1/ 100 = 1% 1/ 100 = 1% 12.86.65.53
0/ 100 = 0% |
6 --- 100/ 100 =100% 100/ 100 =100% cr84.cgcil.ip.att.net [12.122.132.102]
0/ 100 = 0% |
7 --- 100/ 100 =100% 100/ 100 =100% cr2.cgcil.ip.att.net [12.123.7.250]
0/ 100 = 0% |
8 --- 100/ 100 =100% 100/ 100 =100% cr2.sl9mo.ip.att.net [12.122.2.22]
0/ 100 = 0% |
9 --- 100/ 100 =100% 100/ 100 =100% cr2.kc9mo.ip.att.net [12.122.28.89]
0/ 100 = 0% |
10 --- 100/ 100 =100% 100/ 100 =100% cr1.dlstx.ip.att.net [12.122.28.85]
0/ 100 = 0% |
11 --- 100/ 100 =100% 100/ 100 =100% cr1.phmaz.ip.att.net [12.122.28.182]
0/ 100 = 0% |
12 --- 100/ 100 =100% 100/ 100 =100% gar4.phmaz.ip.att.net [12.123.206.145]
0/ 100 = 0% |
13 --- 100/ 100 =100% 100/ 100 =100% 12.122.255.106
0/ 100 = 0% |
14 182ms 0/ 100 = 0% 0/ 100 = 0% mdf002c7613r0002-gig-12-1.phx1.attens.net [63.241.130.202]

Trace complete.
Edited by Ravsx on 1/29/2011 7:43 PM PST
58 Troll Death Knight
0
.
Edited by Scyl on 6/17/2012 9:57 AM PDT
This topic has reached its post limit. You may no longer post or reply to posts for this topic.

Please report any Code of Conduct violations, including:

Threats of violence. We take these seriously and will alert the proper authorities.

Posts containing personal information about other players. This includes physical addresses, e-mail addresses, phone numbers, and inappropriate photos and/or videos.

Harassing or discriminatory language. This will not be tolerated.

Forums Code of Conduct

Report Post # written by

Reason
Explain (256 characters max)
Submit Cancel

Reported!

[Close]