Mac OS X 10.7.2 EXTREME Latency Issues

Mac Technical Support
Okay so I get these random latency super spikes, normally my connection is fine. I have Road Runner Lightening with 40MBPS^ stream and 5MBPSv stream. My latency spikes crazy up to 2.3k home and 4.2k world, these is NO WHERE near acceptable or normal. I have given my router a very nice one hour long power cycle and that hasn't helped.

This photo is an example of the issue:
http://i40.tinypic.com/2zi7nfl.png
you had me convinced at "Road Runner"

i doubt even a traceroute would show much, Road Runner is know for making wow run like crap with traffic shaping, even if they try to deny it. I'm sure blue has been following it more then i have as he tends to watch the PC forums and i do not.
I have the BRIGHT HOUSE LIGHTENING... hmm and mac os x 10.7.2. I have the same problem, I think it is a combo of the internet and the new OS. I have no fix. I thought I should mention though... that when I get kicked off of WoW I can still open Safari and it work. I have reset the DNS and everything it works for about 10 min at 100ish latency. I think it has to do with how the new OS runs, epically with handling info. When I had the old one, 10.6.8 it was fine, other then occasional once a week DC. I think this new OS is a bit ahead of it time and doesn't play well with others yet. Like windows vista all over again...
I use RR myself, and I rarely have problems like this. That being said, I do have some suggestions, some of which you've done, some maybe not. But, I like to cover all the bases before I start referring anyone back to the ISP.

And, I would like to see a trace during the spikes if possible. Thanks!

Note: If you are using a wireless connection of any kind, please try to connect using a wired connection such as an ethernet cable as a temporary test.

Wireless connections can be unstable in general and many things beyond your control such as nearby cordless telephones, microwave ovens, refrigerators, walls, distance and outside power lines can and often do interfere with the signal integrity. If you stop being disconnected while using a wired connection you will know your wireless is suffering from interference from a nearby source. If you are still disconnected regularly, please continue using your wired connection for the remainder of our troubleshooting.

* Addons & Custom UI Mods

Reset the permissions on your WoW folder:
1. Select the World of Warcraft folder
2. Press Command + I
3. In the World of Warcraft Info box, go to the Sharing & Permissions section
4. Click on the lock and unlock it, entering your admin password when prompted.
5. Make sure you have Read & Write permissions
6. Click on the Burst icon (cog wheel) and select Apply to enclosed items

Reset the temp files:
1. Navigate to /Applications/World of Warcraft/
2. Delete the Cache folder.
3. Move Interface and WTF to the Desktop.
4. Go to WoW/Data/ and delete the Cache folder.
5. Launch WoW.

* Firewalls (Including the one on your router)

Please see this page for port information and advice on setting up your firewall/router for World of Warcraft:
http://us.blizzard.com/support/article/21015

If all of the above steps haven't resovled your latency, please reply with a trace:

1. Go to Mac HD => Applications => Utilities folder.
2. Open the Network Utility program.
3. Choose Traceroute tab.
4. In the box enter: us.logon.battle.net
5. Click the Trace button.
6. Select all the data that comes up in the box below.
7. Command + C to copy the data.
8. In your reply, use Command + V to paste the data.

To get a trace to the realm while you're connected:
1. Go to Mac HD => Applications => Utilities folder.
2. Open the Network Utility program.
3. Choose Netstat tab and leave "Display the state of all current socket connections" selected.
4. Click "Scan."
5. Find the first foreign address that says battlenet.
6. Copy/paste the IP address into the Traceroute tab.
7. Command + C to copy the data resulting from the trace.
8. In your reply, use command + V to paste the data.
Traceroute has started…

traceroute to us.logon.battle.net (12.129.206.130), 64 hops max, 72 byte packets
1 10.0.1.1 (10.0.1.1) 0.419 ms 0.208 ms 0.183 ms
2 * * *
3 202.128.2.81 (202.128.2.81) 340.795 ms 344.731 ms 419.137 ms
4 gw5-sw1.guam.net (202.128.2.5) 417.939 ms 465.329 ms 203.732 ms
5 gw6-gw5.guam.net (202.128.2.2) 472.172 ms 445.231 ms 479.582 ms
6 198.81.233.238.guam.net (198.81.233.238) 124.646 ms
so-1-3-0.gw4.la.guam.net (198.81.233.230) 138.121 ms
198.81.233.238.guam.net (198.81.233.238) 122.435 ms
7 64.129.197.73 (64.129.197.73) 157.693 ms 158.145 ms 153.064 ms
8 lax2-pr2-xe-0-3-0-0.us.twtelecom.net (66.192.253.170) 161.428 ms 157.776 ms 157.302 ms
9 cr2.la2ca.ip.att.net (12.122.104.70) 125.077 ms
cr1.la2ca.ip.att.net (12.122.104.14) 140.216 ms 159.658 ms
10 gar29.la2ca.ip.att.net (12.122.129.241) 138.090 ms
gar20.la2ca.ip.att.net (12.122.128.181) 138.357 ms
gar29.la2ca.ip.att.net (12.122.129.241) 154.995 ms
11 12-122-254-234.attens.net (12.122.254.234) 155.741 ms 179.506 ms 366.516 ms
12 mdf001c7613r0004-gig-10-1.lax1.attens.net (12.129.193.250) 137.732 ms 155.987 ms 144.176 ms
13 12.129.211.38 (12.129.211.38) 138.249 ms !X 124.996 ms !X *
Whoa, there is something seriously wrong (or at least interesting)! Somehow you are being routed through Guam...
Are you using any kind of "vpn" or "ping" service? What about a company or corporate VPN?


If not, I would call your ISP.

I would also check for viruses. (Don't panic, it could be just a transient routing issue!) I use Sophos -- it's free and I don't know if it does anything because it's never reported anything and I don't think I have ever gotten a virus, but I know it's a free option and they seem pretty legit... (have used them on windows at some companies I have worked at)
it's likely they aren't routing through guam but are in guam based on that traceroute. those hops are terrible either way and definitely causing the problems.
Wow, I was completely unaware that RR ran out of Guam. That would be the simpler answer. :) Hmmm. They're still "bad" but not 2-4k bad. Of course this is just 1 sample. Can you try to get a traceroute while you're seeing these lag spikes?
Glocnasty isn't the op, they don't have RR. they bumped someone elses thread with their problem.
Traceroute has started…

traceroute to us.logon.battle.net (12.129.206.130), 64 hops max, 72 byte packets
1 192.168.1.1 (192.168.1.1) 1.862 ms 1.074 ms 0.981 ms
2 * * *
3 dstswr2-vlan4.rh.wrwkny.cv.net (67.83.253.66) 30.532 ms 29.793 ms 36.042 ms
4 * * *
5 rtr3-tg10-3.wan.prnynj.cv.net (64.15.6.9) 47.062 ms 34.137 ms 34.816 ms
6 * * *
7 xe-11-3-2.edge2.newark1.level3.net (4.28.5.117) 41.715 ms 32.291 ms 87.098 ms
8 ae-31-51.ebr1.newark1.level3.net (4.69.156.30) 33.417 ms 36.491 ms 32.069 ms
9 ae-2-2.ebr1.newyork1.level3.net (4.69.132.97) 34.568 ms 33.307 ms 35.499 ms
10 ae-81-81.csw3.newyork1.level3.net (4.69.134.74) 33.355 ms 34.015 ms 34.839 ms
11 ae-3-80.edge3.newyork1.level3.net (4.69.155.145) 53.613 ms 32.970 ms 33.975 ms
12 att-level3.newyork1.level3.net (4.68.63.142) 37.085 ms 35.779 ms 37.875 ms
13 cr1.n54ny.ip.att.net (12.122.131.102) 109.626 ms 104.896 ms 108.701 ms
14 cr2.cgcil.ip.att.net (12.122.1.2) 103.661 ms 113.898 ms 103.230 ms
15 cr1.cgcil.ip.att.net (12.122.2.53) 106.569 ms 105.289 ms 110.844 ms
16 cr2.dvmco.ip.att.net (12.122.31.85) 127.747 ms 105.207 ms 106.367 ms
17 cr1.slkut.ip.att.net (12.122.30.25) 105.619 ms 107.794 ms 106.186 ms
18 cr2.la2ca.ip.att.net (12.122.30.30) 110.748 ms 103.364 ms 113.554 ms
19 gar29.la2ca.ip.att.net (12.122.129.241) 110.233 ms 99.543 ms 102.939 ms
20 12-122-254-234.attens.net (12.122.254.234) 104.373 ms
12-122-254-238.attens.net (12.122.254.238) 111.089 ms 103.091 ms
21 mdf001c7613r0004-gig-10-1.lax1.attens.net (12.129.193.250) 103.283 ms 119.633 ms 122.262 ms
22 12.129.211.38 (12.129.211.38) 105.061 ms !X * *
23 12.129.211.38 (12.129.211.38) 103.048 ms !X
Traceroute has started…

traceroute to 12.129.206.130 (12.129.206.130), 64 hops max, 72 byte packets
1 10.0.1.1 (10.0.1.1) 0.320 ms 0.239 ms 0.170 ms
2 * * *
3 202.128.2.81 (202.128.2.81) 15.468 ms 17.948 ms 28.049 ms
4 gw5-sw1.guam.net (202.128.2.5) 29.532 ms 34.926 ms 16.913 ms
5 gw6-gw5.guam.net (202.128.2.2) 24.039 ms 19.003 ms 17.147 ms
6 so-1-3-0.gw4.la.guam.net (198.81.233.230) 148.436 ms
so-0-3-0.gw4.la.guam.net (198.81.233.238) 142.367 ms
so-1-3-0.gw4.la.guam.net (198.81.233.230) 152.669 ms
7 64.129.197.73 (64.129.197.73) 141.331 ms 140.888 ms 155.441 ms
8 lax2-pr2-xe-0-3-0-0.us.twtelecom.net (66.192.253.170) 159.100 ms 137.758 ms 145.252 ms
9 cr1.la2ca.ip.att.net (12.122.104.14) 163.916 ms
cr2.la2ca.ip.att.net (12.122.104.70) 145.148 ms
cr1.la2ca.ip.att.net (12.122.104.14) 146.942 ms
10 gar20.la2ca.ip.att.net (12.122.128.181) 127.261 ms
gar29.la2ca.ip.att.net (12.122.129.241) 166.799 ms
gar20.la2ca.ip.att.net (12.122.128.181) 153.888 ms
11 12-122-254-238.attens.net (12.122.254.238) 144.648 ms 153.518 ms
12-122-254-234.attens.net (12.122.254.234) 147.288 ms
12 mdf001c7613r0004-gig-10-1.lax1.attens.net (12.129.193.250) 162.169 ms 159.093 ms 156.299 ms
13 12.129.211.38 (12.129.211.38) 156.494 ms !X * 144.751 ms !X
1 192.168.1.1 (192.168.1.1) 1.862 ms 1.074 ms 0.981 ms
2 * * *
3 dstswr2-vlan4.rh.wrwkny.cv.net (67.83.253.66) 30.532 ms 29.793 ms 36.042 ms
4 * * *
5 rtr3-tg10-3.wan.prnynj.cv.net (64.15.6.9) 47.062 ms 34.137 ms 34.816 ms
6 * * *
7 xe-11-3-2.edge2.newark1.level3.net (4.28.5.117) 41.715 ms 32.291 ms 87.098 ms

So, it seems it may be hops 2, 4 and 6 may be the issue has it seems like the packets are being loss, and the ms goes up during these hops.

Join the Conversation

Return to Forum