World of Warcraft - English (NA) Forums -> New York Time Warner Connectivity Issues

Nickjs

Blizzard Poster

0. New York Time Warner Connectivity Issues 07/20/2007 12:52:55 PM PDT

UPDATE 8/20 15:40PDT

The New York connectivity issue appears to be resolved. We will create another sticky if need be to collect more data if the need arises again.

There appears to be an issue with connectivity from the Cincinnati, Ohio area for which we have created a sticky here: http://forums.worldofwarcraft.com/thread.html?topicId=1134196354&sid=1

If you are not from the Cincinnati area, yet experiencing connectivity issues, please create a new thread below to begin troubleshooting.

Edited: EvanM

UPDATE 8/16 9:15am PDT

An alteration in the network configuration has been made by a peering partner in effort to relieve the connectivity/latency issue. Please test again to determine if the connectivity/latency is still an issue from your ISP and geographical location.

If you still encounter the issue, please e-mail forumtech@blizzard.com with the the subject line, "New York Time Warner Connectivity" along with a new trace route and your IP address. You can find your IP address by opening a browser window such as Internet Explorer and going to http://www.whatismyip.com .

(Edited by: EvanM)

UPDATE 8/10 5:10pm Pacific Time

Our network team has requested that players in the affected area using Time Warner/Road Runner please run a trace route to the following IP Address and post your results in this thread:

72.5.213.9

In addition to running a trace route to the IP Address above, please also run a trace route to your main realm and post the results as well. Be sure to include the name of the realm. Instructions for running a trace route to this IP Address and to your main realms IP Address can be found at the bottom of my initial post. For those reading this on page 25, the main post with these instructions can be found at:
http://forums.worldofwarcraft.com/thread.html?topicId=383541927&sid=1#0

________________________________________________________________________________

UPDATE 8/8 5:12pm Pacific Time

Our network administrators have been unable to find any abnormalities that would cause these reported connections issues; however, reports of connection problems with services other than World of Warcraft have also been reported at various locations. The cause of these other issues seems to be being blamed on the packet shaping protocols that Time Warner/Road Runner has recently implemented.

Our network administrators are continuing to examine what the cause may be, but at this time the cause does seem to be this packet shaping software.

Please contact Time Warner/Road Runner for more information about this. If we receive any additional information regarding this, I will continue to update the thread.

________________________________________________________________________________

UPDATE 8/6 3:15pm Pacific Time

The requested information has been collected and forwarded on to the appropriate departments. Thank you to everybody who had submitted their information. We no longer need additional submissions for now. While we continue to investigate this issue further, we ask for your continued patience. In the meantime, I will continue to provide updates as I receive them.

________________________________________________________________________________

UPDATE 8/1 1:04pm Pacific Time

Our network team has requested that we gather Public IP Addresses from players who are experiencing these connectivity issues within the area and ISP's specified. Please DO NOT post your Public IP Address here in the forums. We will need you to email it to us at WoWTech@Blizzard.com. Also be sure to put "ATTN: NickJS - IP Address" in the subject field. This information will then be forwarded on to our network team for further investigation. To gather your Public IP Address, please visit (http://www.blizzard.com/support/myip/) and copy/paste this into the email you send in. Remember, DO NOT post your Public IP Address here on the forums. We appreciate everybody's patience while we continue to investigate this.

Please also include the following information in the email -

ISP (Internet Service Provider):
Location (City, State, Country):
Trace Route:
Realm:

________________________________________________________________________________

UPDATE 7/27 3:28pm Pacific Time

Our network team is still investigating this issue. In the meantime, please continue to follow up with Time Warner/Road Runner regarding any updates they may have on their end.

________________________________________________________________________________

UPDATE 7/23 4:46pm Pacific Time

We have seen a pattern within many of the trace routes that have been posted and have forwarded the information to our network team to investigate. Any future updates will be posted.

________________________________________________________________________________

To our customers who are experiencing connection issues using Time Warner/Road Runner from New York:

We apologize for the inconvenience that you are having, and we need to collect information from you in order to work with Time Warner/Road Runner and our service provider to troubleshoot and resolve the issue.

We'll need you to run a trace route to your "home server" and post the results in this thread.

Steps to run the Trace Route command (Windows XP/2000):

1) Click Start and then Run
2) Type "command" and press Enter
3) In the command window, type 'tracert xxx.xxx.xxx.xxx > C:\tracert.txt' (without the quotes) and press the Enter key.

Steps to run the Trace Route command (Windows Vista):

1) Click Start and in the "Start Search" field type "command" or "cmd"
3) In the command window, type 'tracert xxx.xxx.xxx.xxx > C:\tracert.txt' (without the quotes) and press the Enter key.

A file will be created on your C: drive called tracert.txt that contains your trace route information. Please be patient when waiting for the tracert command to complete, it may take several minutes.

Please put in your actual game server's IP address where it says "xxx.xxx.xxx.xxx". For example, if you were playing on the server "Arthas", you would type in "tracert 206.16.235.69 > C:\tracert.txt" in your command window.

Server List:
Aegwynn - 12.129.225.125
Aerie Peak - 206.17.111.82
Agamaggan - 63.241.255.14
Aggramar - 206.16.235.120
Akama - 12.129.225.23
Alexstrasza - 63.241.255.82
Alleria - 63.241.255.77
Altar of Storms - 206.17.111.35
Alterac Mountains - 206.17.111.103
Aman'Thul - 12.129.225.8
Andorhal - 206.17.111.4
Anetheron - 206.17.111.49
Antonidas - 72.5.213.61
Anub'arak - 72.5.213.113
Anvilmar - 206.17.111.126
Arathor - 12.129.233.37
Archimonde - 206.17.111.7
Area 52 - 206.16.147.46
Argent Dawn - 206.16.235.80
Arthas - 206.16.235.69
Arygos - 206.17.111.81
Auchindoun - 206.16.147.59
Azgalor - 206.16.235.98
Azjol-Nerub - 12.129.233.103
Azshara - 63.241.255.98
Azuremyst - 206.16.147.49
Baelgun - 63.241.255.5
Balnazzar - 63.241.255.13
Barthilas - 12.129.225.61
Black Dragonflight - 206.17.111.21
Blackhand - 63.241.255.8
Blackrock - 12.129.225.21
Blackwater Raiders - 72.5.213.94
Blackwing Lair - 206.17.111.115
Bladefist - 72.5.213.95
Blade's Edge - 206.16.147.69
Bleeding Hollow - 206.16.235.43
Blood Furnace - 206.16.147.65
Bloodhoof - 206.16.235.34
Bloodscalp - 12.129.233.7
Bonechewer - 12.129.233.13
Boulderfist - 12.129.233.47
Bronzebeard - 12.129.233.46
Burning Blade - 206.16.235.68
Burning Legion - 206.16.235.64
Cenarion Circle - 72.5.213.115
Cenarius - 72.5.213.52
Cho'gall - 63.241.255.101
Chromaggus - 12.129.225.22
Coilfang - 206.16.147.56
Crushridge - 12.129.233.52
Daggerspine - 12.129.233.88
Dalaran - 206.17.111.111
Dalvengyr - 206.17.111.36
Dark Iron - 63.241.255.67
Darkspear - 12.129.233.12
Darrowmere - 72.5.213.114
Dath'Remar - 12.129.225.73
Deathwing - 206.17.111.83
Demon Soul - 206.17.111.127
Dentarg - 206.17.111.125
Destromath - 63.241.255.102
Dethecus - 63.241.255.97
Detheroc - 63.241.255.66
Doomhammer - 206.17.111.90
Draenor - 12.129.233.33
Dragonblight - 12.129.233.17
Dragonmaw - 12.129.233.94
Draka - 12.129.225.19
Drak'thul - 12.129.225.105
Drenden - 72.5.213.100
Dunemaul - 12.129.233.23
Durotan - 206.16.235.55
Duskwood - 206.17.111.45
Earthen Ring - 206.16.235.63
Echo Isles - 72.5.213.125
Eitrigg - 12.129.225.126
Eldre'Thalas - 12.129.233.48
Elune - 206.16.235.36
Emerald Dream - 63.241.255.83
Eonar - 206.16.235.6
Eredar - 206.16.235.89
Executus - 206.17.111.121
Exodar - 206.16.147.100
Farstriders - 72.5.213.101
Feathermoon - 12.129.233.96
Fenris - 72.5.213.120
Firetree - 12.129.233.25
Frostmane - 12.129.233.53
Frostmourne - 12.129.225.107
Frostwolf - 12.129.225.127
Garithos - 12.129.225.14
Garona - 63.241.255.12
Gilneas - 206.16.235.100
Gnomeregan - 206.17.111.32
Gorefiend - 206.16.235.24
Gorgonnash - 63.241.255.84
Greymane - 63.241.255.56
Gul'dan - 63.241.255.120
Gurubashi - 12.129.233.24
Hakkar - 12.129.225.15
Haomarush - 206.17.111.37
Hellscream - 63.241.255.55
Hydraxis - 72.5.213.43
Hyjal - 72.5.213.8
Icecrown - 206.17.111.120
Illidan - 63.241.255.110
Jaedenar - 206.17.111.114
Jubei'Thos - 12.129.225.103
Kael'thas - 63.241.255.113
Kalecgos - 63.241.255.81
Kargath - 206.16.235.118
Kel'Thuzad - 206.17.111.41
Khadgar - 206.17.111.55
Khaz Modan - 12.129.225.13
Khaz'goroth - 12.129.225.123
Kil'jaeden - 12.129.225.112
Kilrogg - 12.129.225.26
Kirin Tor - 63.241.255.27
Korgath - 12.129.225.11
Korialstrasz - 72.5.213.97
Kul Tiras - 12.129.225.9
Laughing Skull - 206.16.235.31
Lethon - 206.17.111.99
Lightbringer - 72.5.213.58
Lightninghoof - 63.241.255.100
Lightning's Blade - 206.16.235.33
Llane - 206.16.235.99
Lothar - 206.16.235.1
Madoran - 206.16.235.113
Maelstrom - 63.241.255.88
Magtheridon - 206.16.235.8
Maiev - 72.5.213.98
Malfurion - 63.241.255.45
Mal'Ganis - 206.17.111.43
Malorne - 12.129.225.2
Malygos - 206.16.235.71
Mannoroth - 206.16.235.92
Medivh - 206.16.235.85
Misha - 72.5.213.9
Mok'Nathal - 72.5.213.117
Moon Guard - 72.5.213.62
Moonrunner - 63.241.255.9
Mug'thol - 12.129.225.6
Muradin - 12.129.225.3
Nagrand - 12.129.225.43
Nathrezim - 12.129.233.5
Nazgrel - 72.5.213.118
Nazjatar - 63.241.255.10
Ner'zhul - 12.129.225.16
Nordrassil - 72.5.213.54
Norgannon - 206.17.111.88
Onyxia - 206.17.111.1
Perenolde - 12.129.233.42
Proudmoore - 12.129.225.18
Quel'dorei - 72.5.213.99
Ravencrest - 63.241.255.23
Ravenholdt - 72.5.213.96
Rexxar - 12.129.225.5
Rivendare - 72.5.213.55
Runetotem - 12.129.225.1
Sargeras - 63.241.255.89
Scarlet Crusade - 12.129.233.72
Scilla - 206.17.111.22
Sen'jin - 12.129.225.80
Sentinels - 206.17.111.10
Shadow Council - 12.129.233.20
Shadowmoon - 206.16.235.57
Shadowsong - 12.129.233.97
Shandris - 72.5.213.69
Shattered Halls - 206.16.147.109
Shattered Hand - 206.16.235.110
Shu'halo - 72.5.213.83
Silver Hand - 12.129.225.114
Silvermoon - 12.129.233.40
Sisters of Elune - 72.5.213.102:
Skullcrusher - 206.16.235.122
Skywall - 12.129.233.128
Smolderthorn - 12.129.233.21
Spinebreaker - 63.241.255.52
Spirestone - 12.129.233.4
Staghelm - 63.241.255.48
Steamwheedle Cartel - 206.17.111.42
Stonemaul - 12.129.233.22
Stormrage - 206.16.235.117
Stormreaver - 63.241.255.90
Stormscale - 12.129.233.90
Suramar - 12.129.233.2
Tanaris - 206.17.111.3
Terenas - 12.129.233.89
Terokkar - 206.16.147.70
Thaurissan - 12.129.225.82
The Forgotten Coast - 72.5.213.127
The Scryers - 206.16.147.76
The Underbog - 206.16.147.43
The Venture Co - 206.17.111.119
Thorium Brotherhood - 12.129.225.4
Thrall - 206.17.111.100
Thunderhorn - 206.16.235.125
Thunderlord - 206.16.235.11
Tichondrius - 12.129.225.41
Tortheldrin - 72.5.213.36
Trollbane - 206.16.235.97
Turalyon - 206.17.111.87
Twisting Nether - 63.241.255.7
Uldaman - 206.17.111.48
Uldum - 12.129.233.6
Undermine - 206.17.111.124
Ursin - 63.241.255.80
Uther - 72.5.213.44
Vashj - 72.5.213.85
Vek'nilash - 12.129.225.10
Velen - 206.16.147.98
Warsong - 206.16.235.108
Whisperwind - 63.241.255.123
Wildhammer - 63.241.255.128
Windrunner - 12.129.233.11
Ysera - 206.17.111.8
Ysondre - 206.17.111.56
Zangarmarsh - 206.16.147.74
Zul'jin - 206.16.235.112
Zuluhed - 206.17.111.128

[ Post edited by Evanm ]

Blizzard Entertainment Technical Support

Sneakstone

Windrunner

1. Re: New York Time Warner Connectivity Issues 07/20/2007 01:07:27 PM PDT

I posted this under the Connectivity\Lagging post before I saw this one. I am on RoadRunner in NY. Here is my Tracert

Issue:
Lag time spikes to above 700ms shortly after logging in, even in a zone with few players.
No changes have been made to my setup (except for this month's Windows critical updates).
No other issues with my internet connection, browsing, VPN, upload\download are all fine.
I have been playing WoW with this setup for months now with no problems, I logged in today and suddenly have very high lag.

OS: Window XP with SP2 and all the latest updates
NIC: Intel(R) 82562V 10/100 Network Connection
Router: Linksys WRT54G with latest firmware (PC is connected to Linksys router via Cat 5, not wireless)
ISP: RoadRunner Cable
Location: New York,NY
WoW server: Windrunner

Netstat: TCP 12.129.233.11:3724 ESTABLISHED

tracert: 12.129.233.11

Tracing route to 12.129.233.11 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 192.168.1.1
2 8 ms 6 ms 6 ms 10.39.64.1
3 6 ms 6 ms 17 ms pos0-1-nycmnyg-rtr1.nyc.rr.com [24.29.98.85]
4 7 ms 7 ms 6 ms pos4-0.nycmnyb-rtr1.nyc.rr.com [24.29.98.5]
5 7 ms 6 ms 5 ms pos13-0-nycmnya-rtr1.nyc.rr.com [24.29.97.25]
6 7 ms 6 ms 11 ms tenge-3-0-0.nwrknjmd-rtr.nyc.rr.com [24.29.119.106]
7 8 ms 8 ms 7 ms pop2-new-P4-0.atdn.net [66.185.137.21]
8 7 ms 6 ms 8 ms bb2-new-P3-0.atdn.net [66.185.137.18]
9 9 ms 8 ms 8 ms bb1-nye-P4-0.atdn.net [66.185.152.196]
10 8 ms 7 ms 7 ms pop2-nye-P0-0.atdn.net [66.185.151.65]
11 8 ms 11 ms 8 ms 192.205.34.45
12 78 ms 77 ms 77 ms tbr1.n54ny.ip.att.net [12.122.105.18]
13 81 ms 81 ms 80 ms cr1.n54ny.ip.att.net [12.122.10.57]
14 79 ms 77 ms 77 ms cr1.cgcil.ip.att.net [12.122.1.190]
15 77 ms 78 ms 78 ms tbr2.cgcil.ip.att.net [12.122.10.170]
16 80 ms 81 ms 82 ms tbr2.sl9mo.ip.att.net [12.122.10.46]
17 81 ms 84 ms 81 ms tbr2.la2ca.ip.att.net [12.122.10.14]
18 81 ms 81 ms 79 ms 12.127.3.189
19 80 ms 82 ms 81 ms 12.122.255.74
20 184 ms 181 ms 192 ms mdf001c7613r0004-gig-12-1.lax1.attens.net [12.129.193.246]
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.

Shiekk

< Meridian >

Kargath

2. Re: New York Time Warner Connectivity Issues 07/20/2007 01:11:17 PM PDT

Home Server : Kargath

Tracing route to 206.16.235.118 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1

2 7 ms 5 ms 6 ms 10.50.224.1

3 7 ms 7 ms 7 ms ge0-3-nycmny3-ubr2.si.rr.com [24.164.129.61]

4 9 ms 11 ms 7 ms ge0-3-nycmny2-ubr2.si.rr.com [24.164.129.57]

5 8 ms 8 ms 7 ms ge5-2-nycmny1-rtr1.si.rr.com [24.164.129.53]

6 9 ms 7 ms 7 ms pos1-0-nycmnya-rtr2.nyc.rr.com [24.29.100.113]

7 10 ms 16 ms 9 ms tenge-3-0-0.nycsnyoo-rtr1.nyc.rr.com [24.29.119.114]

8 8 ms 8 ms 11 ms te-3-1.car3.NewYork1.Level3.net [4.78.168.45]

9 9 ms 8 ms 8 ms ggr2-p360.n54ny.ip.att.net [192.205.33.93]

10 16 ms 18 ms 28 ms tbr2.n54ny.ip.att.net [12.123.3.61]

11 14 ms 15 ms 16 ms tbr2.wswdc.ip.att.net [12.122.10.54]

12 14 ms 15 ms 18 ms 12.123.8.21

13 111 ms 212 ms 208 ms 12.122.255.50

14 16 ms * 15 ms mdf002c7613r0002-gig-12-1.wdc1.attens.net [63.240.192.142]

15 * * * Request timed out.

16 * * * Request timed out.

17 * *

__________________________________

Tracing route to 206.16.235.118 over a maximum of 30 hops

1 1 ms <1 ms <1 ms 192.168.1.1

2 6 ms 5 ms 6 ms 10.50.224.1

3 7 ms 8 ms 8 ms ge0-3-nycmny3-ubr2.si.rr.com [24.164.129.61]

4 7 ms 7 ms 7 ms ge0-3-nycmny2-ubr2.si.rr.com [24.164.129.57]

5 8 ms 8 ms 6 ms ge5-2-nycmny1-rtr1.si.rr.com [24.164.129.53]

6 8 ms 9 ms 8 ms pos1-0-nycmnya-rtr2.nyc.rr.com [24.29.100.113]

7 * * 8 ms tenge-3-0-0.nycsnyoo-rtr1.nyc.rr.com [24.29.119.114]

8 8 ms 10 ms 8 ms te-3-1.car3.NewYork1.Level3.net [4.78.168.45]

9 9 ms 7 ms 13 ms ggr2-p360.n54ny.ip.att.net [192.205.33.93]

10 18 ms 17 ms 17 ms tbr2.n54ny.ip.att.net [12.123.3.61]

11 17 ms 17 ms 16 ms tbr2.wswdc.ip.att.net [12.122.10.54]

12 13 ms 15 ms 14 ms 12.123.8.21

13 16 ms 15 ms 15 ms 12.122.255.50

14 17 ms 16 ms 18 ms mdf002c7613r0002-gig-12-1.wdc1.attens.net [63.240.192.142]

15 * * * Request timed out.

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

[ Post edited by Shiekk ]

Peredur

Windrunner

3. Re: New York Time Warner Connectivity Issues 07/20/2007 01:23:15 PM PDT

I had originally posted this last night on the other latency thread. I will post an updated one when I get home. To the Windrunner server

Here is my trace route:

Tracing route to 12.129.233.11 over a maximum of 30 hops
1 9 ms 10 ms 11 ms 10.36.32.1
2 19 ms 13 ms 18 ms pos0-0-nycmnye-rtr2.nyc.rr.com [24.29.98.45]
3 26 ms 30 ms 18 ms pos3-0-nycmnyg-rtr1.nyc.rr.com [24.29.98.1]
4 31 ms 18 ms 17 ms 24.29.119.33
5 98 ms 92 ms 86 ms pos4-0.nycmnyb-rtr1.nyc.rr.com [24.29.98.5]
6 58 ms 55 ms 51 ms pos3-2-nycmnya-rtr1.nyc.rr.com [24.29.101.254]
7 82 ms 63 ms 61 ms tenge-3-0-0.nwrknjmd-rtr.nyc.rr.com [24.29.119.106]
8 58 ms 57 ms 65 ms pop2-new-P4-0.atdn.net [66.185.137.21]
9 71 ms 221 ms 180 ms bb2-new-P3-0.atdn.net [66.185.137.18]
10 47 ms 49 ms 50 ms bb1-nye-P4-0.atdn.net [66.185.152.196]
11 52 ms 50 ms 47 ms pop2-nye-P0-0.atdn.net [66.185.151.65]
12 47 ms 51 ms 61 ms 192.205.34.45
13 137 ms 137 ms 141 ms tbr1.n54ny.ip.att.net [12.122.105.18]
14 131 ms 153 ms 141 ms cr1.n54ny.ip.att.net [12.122.10.101]
15 129 ms 139 ms 122 ms cr1.cgcil.ip.att.net [12.122.1.190]
16 122 ms 120 ms 124 ms tbr2.cgcil.ip.att.net [12.122.10.158]
17 121 ms 139 ms 129 ms tbr2.sl9mo.ip.att.net [12.122.10.46]
18 125 ms 141 ms 125 ms tbr2.la2ca.ip.att.net [12.122.10.14]
19 137 ms 146 ms 135 ms 12.127.3.189
20 154 ms 239 ms 204 ms 12.122.255.74
21 154 ms 155 ms 134 ms mdf001c7613r0004-gig-12-1.lax1.attens.net [12.129.193.246]
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 *

Router: none. I disconnected it and hooked up my PC directly to the cable modem to take that out of the equation
Cable Modem: RCA DCM425
Software Firewalls: none temporarily disabled for testing.
ISP: Time warner Cable/Roadrunner
Location: New York City, NY

Usulbrooklyn

< Valence >

Altar of Storms

5. Re: New York Time Warner Connectivity Issues 07/20/2007 01:54:21 PM PDT

Been happening since Monday morning...

Altar of Storms

1 user-12ld2kt.cable.mindspring.com (69.86.138.157) 4380.835 ms 1.623 ms 1.632 ms
2 10.64.32.1 (10.64.32.1) 9.472 ms 7.074 ms 8.380 ms
3 ge5-1-nycmnyr-rtr4.nyc.rr.com (24.29.130.37) 9.990 ms 15.538 ms 8.447 ms
4 pos3-0-nycmnyr-rtr2.nyc.rr.com (24.29.130.41) 7.201 ms 9.472 ms 8.975 ms
5 pos3-0-nycmnya-rtr1.nyc.rr.com (24.29.97.29) 9.968 ms 9.732 ms 8.876 ms
6 tenge-2-0-0.nwrknjmd-rtr.nyc.rr.com (24.29.119.110) 12.555 ms 8.996 ms 8.363 ms
7 pop2-new-p4-0.atdn.net (66.185.137.21) 9.605 ms 10.096 ms 9.453 ms
8 bb2-new-p3-0.atdn.net (66.185.137.18) 9.083 ms 9.803 ms 10.177 ms
9 bb1-nye-p4-0.atdn.net (66.185.152.196) 9.050 ms 10.187 ms 10.381 ms
10 pop2-nye-p0-0.atdn.net (66.185.151.65) 9.479 ms 9.461 ms 10.565 ms
11 192.205.34.45 (192.205.34.45) 18.462 ms 17.870 ms 9.986 ms
12 tbr2.n54ny.ip.att.net (12.122.105.78) 16.530 ms 18.434 ms 15.672 ms
13 tbr1.cb1ma.ip.att.net (12.122.10.21) 17.758 ms 15.564 ms 17.431 ms
14 12.127.5.109 (12.127.5.109) 15.469 ms 16.771 ms 14.493 ms
15 12-122-254-14.attens.net (12.122.254.14) 14.536 ms 16.994 ms 14.412 ms
16 mdf001c7613r0003-gig-10-1.bos1.attens.net (12.130.0.170) 15.554 ms 15.991 ms 15.991 ms
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * *

< Pirate Life >

Tichondrius

6. Re: New York Time Warner Connectivity Issues 07/20/2007 02:16:31 PM PDT

NY:
server: tichondrius

Tracing route to 12-129-225-41.attens.net [12.129.225.41]

over a maximum of 30 hops:

1 7 ms 9 ms 9 ms 10.64.192.1
2 10 ms 10 ms 7 ms cpe-24-29-130-65.nyc.res.rr.com [24.29.130.65]
3 18 ms 7 ms 8 ms pos7-0-nycmnyl-rtr1.nyc.rr.com [24.29.100.122]
4 10 ms 9 ms 14 ms tenge10-0-0.nycmnyrdc-rtr1.nyc.rr.com [24.29.119.117]
5 8 ms 10 ms 13 ms tenge-0-0-0.nwrknjmd-rtr.nyc.rr.com [24.29.119.94]
6 9 ms 11 ms 11 ms pop2-new-P4-1.atdn.net [66.185.141.225]
7 9 ms 10 ms 8 ms bb2-new-P3-0.atdn.net [66.185.137.18]
8 14 ms 9 ms 12 ms bb1-nye-P4-0.atdn.net [66.185.152.196]
9 10 ms 11 ms 7 ms pop2-nye-P0-0.atdn.net [66.185.151.65]
10 8 ms 9 ms 10 ms 192.205.34.45
11 84 ms 92 ms 82 ms tbr1.n54ny.ip.att.net [12.122.105.14]
12 84 ms 82 ms 84 ms cr1.n54ny.ip.att.net [12.122.10.113]
13 82 ms 82 ms 81 ms cr1.cgcil.ip.att.net [12.122.1.190]
14 82 ms 84 ms 82 ms tbr2.cgcil.ip.att.net [12.122.10.174]
15 83 ms 91 ms 83 ms tbr2.sl9mo.ip.att.net [12.122.10.46]
16 85 ms 84 ms 86 ms tbr2.la2ca.ip.att.net [12.122.10.14]
17 82 ms 90 ms 83 ms 12.127.3.189
18 86 ms 83 ms 85 ms 12.122.255.74
19 84 ms 83 ms 85 ms mdf001c7613r0003-gig-10-1.lax1.attens.net [12.129.193.242]
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 *

[ Post edited by Rq ]

http://www.youtube.com/watch?v=N19iSDpfFh4

Arkham

< Miskatonic Universit… >

Azjol-Nerub

7. Re: New York Time Warner Connectivity Issues 07/20/2007 02:25:55 PM PDT

Formerly posted in "High Latency/disconnection info".

Router: Linksys BEFSR41
Modem: Toshiba DAZ8823A
Firewall: none
ISP: TWC Roadrunner
Location: NYC
Issue: Latency spikes and game freezes starting 7/16. The game "fast forwards" after the spike has cleared.

Server is Azjol-Nerub.

traceroute to 12.129.233.103 (12.129.233.103), 30 hops max, 38 byte packets
1 10.34.0.1 (10.34.0.1) 36 bytes to 192.168.1.101 13.237 ms 7.305 ms 7.970 ms
2 pos0-0-nycmnyc-rtr1.nyc.rr.com (24.29.97.45) 36 bytes to 192.168.1.101 7.992 ms 5.302 ms 5.997 ms
3 tenge2-0-0.nycmnyrdc-rtr2.nyc.rr.com (24.29.119.142) 36 bytes to 192.168.1.101 7.491 ms 7.226 ms 5.494 ms
4 tenge-0-0-0.nycsnyoo-rtr1.nyc.rr.com (24.29.119.102) 36 bytes to 192.168.1.101 7.521 ms 9.281 ms 6.470 ms
5 te-4-1.car3.NewYork1.Level3.net (4.78.182.45) 36 bytes to 192.168.1.101 7.050 ms 7.685 ms 7.504 ms
6 att-level3-oc192.NewYork1.Level3.net (4.68.127.150) 36 bytes to 192.168.1.101 7.884 ms 5.866 ms 6.870 ms
7 tbr1.n54ny.ip.att.net (12.123.0.90) 148 bytes to 192.168.1.101 78.693 ms 80.013 ms 77.492 ms
8 cr1.n54ny.ip.att.net (12.122.10.57) 148 bytes to 192.168.1.101 81.641 ms 80.916 ms 81.575 ms
9 * cr1.cgcil.ip.att.net (12.122.1.190) 148 bytes to 192.168.1.101 180.327 ms 178.985 ms
10 tbr2.cgcil.ip.att.net (12.122.10.158) 148 bytes to 192.168.1.101 77.557 ms 79.421 ms 76.591 ms
11 tbr2.sl9mo.ip.att.net (12.122.10.46) 148 bytes to 192.168.1.101 81.610 ms 82.058 ms 80.938 ms
12 tbr2.la2ca.ip.att.net (12.122.10.14) 148 bytes to 192.168.1.101 81.600 ms 82.058 ms 81.021 ms
13 12.127.3.189 (12.127.3.189) 36 bytes to 192.168.1.101 243.832 ms 111.052 ms 80.606 ms
14 12.122.255.74 (12.122.255.74) 36 bytes to 192.168.1.101 79.571 ms 80.507 ms 80.072 ms
15 mdf001c7613r0004-gig-12-1.lax1.attens.net (12.129.193.246) 36 bytes to 192.168.1.101 80.617 ms 80.885 ms 83.095 ms
16 * * *

Atticus

< Infamy >

Mo'grosh

8. Re: New York Time Warner Connectivity Issues 07/20/2007 02:34:26 PM PDT

Live in NYC, also have strange lag issues and I use TWC

I ran a couple tests..my server is the underbog

Traceroute has started ...

traceroute to 206.16.147.43 (206.16.147.43), 64 hops max, 40 byte packets
1 192.168.1.1 (192.168.1.1) 2328.016 ms 2.464 ms 1.089 ms
2 10.34.224.1 (10.34.224.1) 9.014 ms 21.934 ms 10.571 ms
3 pos2-3-nycmnyc-rtr2.nyc.rr.com (24.29.97.89) 14.806 ms 47.893 ms 7.938 ms
4 tenge8-0-0.nycmnya-rtr2.nyc.rr.com (24.29.119.133) 9.640 ms 13.249 ms 8.592 ms
5 tenge-3-0-0.nycsnyoo-rtr1.nyc.rr.com (24.29.119.114) 21.440 ms 8.516 ms 7.669 ms
6 te-3-2.car3.newyork1.level3.net (64.156.82.81) 91.819 ms 8.888 ms 9.341 ms
7 att-level3-oc192.newyork1.level3.net (4.68.127.150) 10.654 ms 10.770 ms 14.630 ms
8 tbr2.n54ny.ip.att.net (12.123.3.110) 16.932 ms 26.170 ms 22.752 ms
9 tbr1.cb1ma.ip.att.net (12.122.10.21) 16.882 ms 16.158 ms 28.712 ms
10 12.127.5.93 (12.127.5.93) 17.188 ms 16.013 ms 14.391 ms
11 12-122-254-14.attens.net (12.122.254.14) 24.054 ms 18.612 ms 13.364 ms
12 mdf001c7613r0003-gig-10-1.bos1.attens.net (12.130.0.170) 16.444 ms * 19.612 ms
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *

Traceroute has started ...

traceroute to 206.16.147.43 (206.16.147.43), 64 hops max, 40 byte packets
1 192.168.1.1 (192.168.1.1) 1703.064 ms 1.751 ms 1.130 ms
2 10.34.224.1 (10.34.224.1) 9.885 ms 9.539 ms 10.137 ms
3 pos2-3-nycmnyc-rtr2.nyc.rr.com (24.29.97.89) 7.549 ms 7.118 ms 7.950 ms
4 tenge8-0-0.nycmnya-rtr2.nyc.rr.com (24.29.119.133) 11.319 ms 8.282 ms 9.295 ms
5 * * *
6 te-3-2.car3.newyork1.level3.net (64.156.82.81) 8.542 ms 10.002 ms 16.141 ms
7 att-level3-oc192.newyork1.level3.net (4.68.127.150) 9.808 ms 9.406 ms 8.882 ms
8 tbr2.n54ny.ip.att.net (12.123.3.110) 27.114 ms 16.571 ms 19.732 ms
9 tbr1.cb1ma.ip.att.net (12.122.10.21) 16.640 ms 16.700 ms 16.154 ms
10 12.127.5.93 (12.127.5.93) 17.301 ms 14.419 ms 15.732 ms
11 12-122-254-14.attens.net (12.122.254.14) 16.264 ms 17.059 ms 25.293 ms
12 mdf001c7613r0003-gig-10-1.bos1.attens.net (12.130.0.170) 18.264 ms 15.675 ms 13.770 ms
13 * * *
14 * * *
15 * * *
16 * * *
Traceroute has started ...

traceroute to 206.16.147.43 (206.16.147.43), 64 hops max, 40 byte packets
1 192.168.1.1 (192.168.1.1) 1748.460 ms 1.164 ms 1.270 ms
2 10.34.224.1 (10.34.224.1) 8.014 ms 14.126 ms 8.785 ms
3 pos2-3-nycmnyc-rtr2.nyc.rr.com (24.29.97.89) 10.517 ms 7.889 ms 7.979 ms
4 tenge8-0-0.nycmnya-rtr2.nyc.rr.com (24.29.119.133) 9.834 ms 7.580 ms 16.601 ms
5 * * *
6 * te-3-2.car3.newyork1.level3.net (64.156.82.81) 8.232 ms 10.063 ms
7 att-level3-oc192.newyork1.level3.net (4.68.127.150) 11.267 ms * 11.229 ms
8 tbr2.n54ny.ip.att.net (12.123.3.110) 15.956 ms 18.828 ms 14.713 ms
9 tbr1.cb1ma.ip.att.net (12.122.10.21) 34.272 ms 15.909 ms 15.157 ms
10 12.127.5.93 (12.127.5.93) 15.767 ms 14.571 ms 15.201 ms
11 12-122-254-14.attens.net (12.122.254.14) 15.849 ms * 16.569 ms
12 mdf001c7613r0003-gig-10-1.bos1.attens.net (12.130.0.170) 14.613 ms 15.837 ms 15.504 ms

[ Post edited by Atticus ]

Stevetu

Kargath

9. Re: New York Time Warner Connectivity Issues 07/20/2007 02:38:56 PM PDT

Staten Island, NY

No router
Motorolla SB5100 Modem

Tracing route to us.logon.worldofwarcraft.com [12.129.232.112]

over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1

2 14 ms 9 ms 13 ms 10.50.224.1

3 9 ms 7 ms 8 ms ge0-3-nycmny3-ubr2.si.rr.com [24.164.129.61]

4 8 ms 9 ms 8 ms ge0-3-nycmny2-ubr2.si.rr.com [24.164.129.57]

5 7 ms 7 ms 8 ms ge5-2-nycmny1-rtr1.si.rr.com [24.164.129.53]

6 13 ms 8 ms 9 ms pos1-0-nycmnya-rtr2.nyc.rr.com [24.29.100.113]

7 8 ms 15 ms * tenge-3-0-0.nycsnyoo-rtr1.nyc.rr.com [24.29.119.114]

8 10 ms 8 ms 13 ms te-3-2.car3.NewYork1.Level3.net [64.156.82.81]

9 9 ms 11 ms 11 ms ggr2-p360.n54ny.ip.att.net [192.205.33.93]

10 79 ms 79 ms 79 ms tbr1.n54ny.ip.att.net [12.123.3.57]

11 89 ms 81 ms 81 ms cr1.n54ny.ip.att.net [12.122.10.57]

12 81 ms 87 ms 78 ms cr1.cgcil.ip.att.net [12.122.1.190]

13 82 ms 83 ms 81 ms tbr2.cgcil.ip.att.net [12.122.10.162]

14 83 ms 93 ms 85 ms tbr2.sl9mo.ip.att.net [12.122.10.46]

15 81 ms 81 ms 80 ms tbr2.la2ca.ip.att.net [12.122.10.14]

16 90 ms 81 ms 82 ms 12.127.3.189

17 84 ms 86 ms 99 ms 12.122.255.74

18 82 ms 83 ms 86 ms mdf001c7613r0003-gig-10-1.lax1.attens.net [12.129.193.242]

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.

Skwishie

< Death Dealers >

Shattered Hand

10. Re: New York Time Warner Connectivity Issues 07/20/2007 02:46:50 PM PDT

Location- new york, new york
ISP- TWC
Issue- Started around 7/16, about every 30 seconds the game would pause for 5 seconds then fast forward. I think on hop 7 of my trace it spiked? that's what it looks like anyway.

Trace to Shattered Hand

Tracing route to 206.16.235.110 over a maximum of 30 hops

1 3 ms 1 ms 1 ms 192.168.1.1

2 * * * Request timed out.

3 9 ms 10 ms 11 ms 24.29.119.9

4 10 ms 12 ms 8 ms 24.29.98.9

5 * 10 ms 9 ms tenge-0-0-0.nwrknjmd-rtr.nyc.rr.com [24.29.119.94]

6 9 ms 19 ms 12 ms pop2-new-P4-0.atdn.net [66.185.137.21]

7 35 ms 157 ms 197 ms bb2-new-P3-0.atdn.net [66.185.137.18]

8 13 ms 9 ms 10 ms bb1-nye-P4-0.atdn.net [66.185.152.196]

9 11 ms 8 ms 9 ms pop2-nye-P0-0.atdn.net [66.185.151.65]

10 10 ms 11 ms 18 ms 192.205.34.45

11 17 ms 17 ms 18 ms tbr2.n54ny.ip.att.net [12.122.105.90]

12 21 ms 20 ms 22 ms tbr2.wswdc.ip.att.net [12.122.10.54]

13 18 ms 16 ms 18 ms 12.123.8.21

14 21 ms 17 ms 19 ms 12.122.255.50

15 20 ms 22 ms 19 ms mdf002c7613r0001-gig-10-1.wdc1.attens.net [63.240.192.138]

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.

Donlegacyx

< Chain Reaction >

Lightning's Blade

11. Re: New York Time Warner Connectivity Issues 07/20/2007 03:00:35 PM PDT

I also posted this in the other latency thread.

Router: None
Modem: RCA DCM425
Firewall: Sygate Firewall
ISP: Earthlink/Time Warner
Location: Brooklyn/NYC
Issue: Pause in connection during WOW, very random and very frequent at all hours of the day including early morning (7am).

Using pingplotters over a extended period of time (paste to notepad for a better view):

Target Name: us.scan.worldofwarcraft.com
IP: 12.129.232.126
Date/Time: 7/20/2007 5:47:33 PM

1 9 ms 9 ms 11 ms 9 ms 7 ms 19 ms 6 ms 10 ms 9 ms 11 ms [10.46.160.1]
2 11 ms 8 ms 20 ms 9 ms 10 ms 9 ms 21 ms 9 ms 18 ms 12 ms gig0-3nycmnys-ubr2.nyc.rr.com [24.29.101.65]
3 8 ms 10 ms 10 ms 9 ms 37 ms 9 ms 10 ms 17 ms 9 ms 11 ms [24.29.119.173]
4 17 ms 9 ms 11 ms 8 ms 8 ms 9 ms 7 ms 11 ms 10 ms 21 ms cpe-24-29-130-58.nyc.res.rr.com [24.29.130.58]
5 10 ms 11 ms 23 ms 9 ms 7 ms 9 ms 10 ms 9 ms 10 ms 10 ms tenge-3-0-0.nycsnyoo-rtr1.nyc.rr.com [24.29.119.114]
6 10 ms 10 ms 12 ms 9 ms 10 ms 22 ms 10 ms 28 ms 11 ms 9 ms te-4-1.car3.NewYork1.Level3.net [4.78.182.45]
7 7 ms 20 ms 11 ms 12 ms 10 ms 21 ms 9 ms 11 ms 9 ms 10 ms att-level3-oc192.NewYork1.Level3.net [4.68.127.150]
8 82 ms 84 ms 85 ms 85 ms 83 ms 83 ms 82 ms 87 ms 83 ms 85 ms tbr1.n54ny.ip.att.net [12.123.0.90]
9 80 ms 81 ms 81 ms 81 ms 82 ms 77 ms 79 ms 78 ms 81 ms 78 ms cr1.n54ny.ip.att.net [12.122.10.113]
10 77 ms 80 ms 80 ms 81 ms 89 ms 78 ms 80 ms 79 ms 89 ms 79 ms cr1.cgcil.ip.att.net [12.122.1.190]
11 80 ms 81 ms 91 ms 82 ms 81 ms 83 ms 81 ms 85 ms 83 ms 81 ms tbr2.cgcil.ip.att.net [12.122.10.174]
12 86 ms 82 ms 84 ms 86 ms 82 ms 99 ms 85 ms 83 ms 87 ms 83 ms tbr2.sl9mo.ip.att.net [12.122.10.46]
13 125 ms 82 ms 86 ms 82 ms 86 ms 83 ms 86 ms 85 ms 85 ms 85 ms tbr2.la2ca.ip.att.net [12.122.10.14]
14 82 ms 80 ms 80 ms 85 ms 82 ms 81 ms 80 ms 80 ms 85 ms 85 ms [12.127.3.189]
15 84 ms 84 ms 83 ms 83 ms 83 ms 84 ms 84 ms 86 ms 100 ms 86 ms [12.122.255.74]
16 83 ms 191 ms 258 ms 99 ms 144 ms 82 ms 90 ms 84 ms 92 ms 83 ms mdf001c7613r0003-gig-10-1.lax1.attens.net [12.129.193.242]
17 * * * * * * * * * * [-]

Target Name: 206.16.235.33:3724
IP: 209.86.66.91
Date/Time: 7/20/2007 5:48:18 PM

1 8 ms 11 ms 20 ms 9 ms 9 ms 10 ms 7 ms 8 ms 8 ms 7 ms [10.46.160.1]
2 10 ms 26 ms 11 ms 9 ms 8 ms 9 ms 8 ms 9 ms 10 ms 10 ms gig0-3nycmnys-ubr2.nyc.rr.com [24.29.101.65]
3 7 ms 8 ms 21 ms 6 ms 10 ms 9 ms 7 ms 10 ms 9 ms 12 ms [24.29.119.173]
4 10 ms 24 ms 10 ms 8 ms 8 ms 11 ms 8 ms 7 ms 9 ms 12 ms cpe-24-29-130-58.nyc.res.rr.com [24.29.130.58]
5 12 ms 12 ms 10 ms 7 ms 10 ms 20 ms * * * * tenge-3-0-0.nycsnyoo-rtr1.nyc.rr.com [24.29.119.114]
6 11 ms 8 ms 8 ms 7 ms 12 ms 16 ms 10 ms 8 ms 9 ms 9 ms te-3-2.car3.NewYork1.Level3.net [64.156.82.81]
7 20 ms 31 ms 21 ms 10 ms 10 ms 19 ms 19 ms 15 ms 8 ms 21 ms vlan99.csw4.NewYork1.Level3.net [4.68.16.254]
8 27 ms 19 ms 9 ms 20 ms 20 ms 11 ms 12 ms 23 ms 20 ms 12 ms ae-93-93.ebr3.NewYork1.Level3.net [4.69.134.109]
9 19 ms 15 ms 21 ms 23 ms 20 ms 15 ms 16 ms 35 ms 18 ms 17 ms ae-3.ebr3.Washington1.Level3.net [4.69.132.89]
10 30 ms 22 ms 16 ms 21 ms 19 ms 29 ms 30 ms 14 ms 18 ms 15 ms ae-93-93.csw4.Washington1.Level3.net [4.69.134.174]
11 15 ms 17 ms 25 ms 18 ms 17 ms 14 ms 14 ms 17 ms 15 ms 16 ms ae-44-99.car4.Washington1.Level3.net [4.68.17.198]
12 26 ms 16 ms 25 ms 26 ms 15 ms 19 ms 156 ms 99 ms 13 ms 16 ms unknown.Level3.net [64.158.57.50]
13 29 ms 31 ms 30 ms 32 ms 30 ms 31 ms 31 ms 32 ms 30 ms 29 ms bor02-so-3-1.ga-atlanta0.ne.earthlink.net [209.165.110.73]
14 29 ms 31 ms 31 ms 30 ms 30 ms 30 ms 28 ms 33 ms 30 ms 41 ms [209.86.66.58]
15 * * * * * * * * * * [-]
16 * * * * * * * * * * [-]

Peedeebee

< The Church >

Darkspear

12. Re: New York Time Warner Connectivity Issues 07/20/2007 03:09:29 PM PDT

I have just started paying again after a little bit of an absence, and on Darkspear, I have started seeing some very bad latency and lag spikes at times. I haven't done a lot just yet, as I just purchased a new computer and am not sure if it is caused by the new computer or something else.

My tracert to Darkspear

C:\Users\Jason>tracert 12.129.242.24

Tracing route to 12.129.242.24 over a maximum of 30 hops

1 3 ms 1 ms 1 ms 192.168.1.1
2 8 ms 8 ms 6 ms 10.46.224.1
3 9 ms 9 ms 11 ms g3-0.nycmnyr-rtr1.nyc.rr.com [24.29.98.22]
4 6 ms 8 ms 7 ms g1-0.nycmnyr-rtr2.nyc.rr.com [24.29.113.125]
5 9 ms 8 ms 7 ms pos3-0-nycmnya-rtr1.nyc.rr.com [24.29.97.29]
6 7 ms 10 ms 9 ms tenge-2-0-0.nwrknjmd-rtr.nyc.rr.com [24.29.119.110]
7 8 ms 10 ms 7 ms pop2-new-P4-0.atdn.net [66.185.137.21]
8 8 ms 18 ms 10 ms bb2-new-P3-0.atdn.net [66.185.137.18]
9 374 ms 198 ms 202 ms bb1-nye-P4-0.atdn.net [66.185.152.196]
10 7 ms 10 ms 11 ms pop2-nye-P0-0.atdn.net [66.185.151.65]
11 10 ms 11 ms 14 ms 192.205.34.45
12 84 ms 88 ms 82 ms tbr1.n54ny.ip.att.net [12.122.105.14]
13 79 ms 83 ms 79 ms cr1.n54ny.ip.att.net [12.122.10.101]
14 82 ms 82 ms 83 ms cr1.cgcil.ip.att.net [12.122.1.190]
15 82 ms 83 ms 82 ms tbr2.cgcil.ip.att.net [12.122.10.158]
16 84 ms 83 ms 100 ms tbr2.sl9mo.ip.att.net [12.122.10.46]
17 83 ms 84 ms 83 ms tbr2.la2ca.ip.att.net [12.122.10.14]
18 83 ms 90 ms 81 ms 12.127.3.189
19 84 ms 93 ms 88 ms 12.122.255.74
20 84 ms 83 ms 91 ms mdf001c7613r0003-gig-10-1.lax1.attens.net [12.129.193.242]
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.

a second one, for good measure:

C:\>type trace.txt

Tracing route to 12.129.242.24 over a maximum of 30 hops

1 <1 ms 1 ms <1 ms 192.168.1.1
2 13 ms 8 ms 14 ms 10.46.224.1
3 19 ms 23 ms 10 ms g3-0.nycmnyr-rtr1.nyc.rr.com [24.29.98.22]
4 10 ms 7 ms 9 ms g1-0.nycmnyr-rtr2.nyc.rr.com [24.29.113.125]
5 6 ms 7 ms 9 ms pos3-0-nycmnya-rtr1.nyc.rr.com [24.29.97.29]
6 9 ms 9 ms 7 ms tenge-2-0-0.nwrknjmd-rtr.nyc.rr.com [24.29.119.110]
7 18 ms 11 ms 9 ms pop2-new-P4-0.atdn.net [66.185.137.21]
8 9 ms 9 ms 12 ms bb2-new-P3-0.atdn.net [66.185.137.18]
9 8 ms 9 ms 10 ms bb1-nye-P4-0.atdn.net [66.185.152.196]
10 12 ms 12 ms 9 ms pop2-nye-P0-0.atdn.net [66.185.151.65]
11 8 ms 11 ms 11 ms 192.205.34.45
12 81 ms 82 ms 87 ms tbr1.n54ny.ip.att.net [12.122.105.14]
13 78 ms 78 ms 79 ms cr1.n54ny.ip.att.net [12.122.10.101]
14 81 ms 85 ms 85 ms cr1.cgcil.ip.att.net [12.122.1.190]
15 103 ms 84 ms 85 ms tbr2.cgcil.ip.att.net [12.122.10.158]
16 82 ms 88 ms 103 ms tbr2.sl9mo.ip.att.net [12.122.10.46]
17 84 ms 82 ms 87 ms tbr2.la2ca.ip.att.net [12.122.10.14]
18 83 ms 82 ms 82 ms 12.127.3.189
19 277 ms 188 ms 201 ms 12.122.255.74
20 94 ms 94 ms 83 ms mdf001c7613r0003-gig-10-1.lax1.attens.net [12.129.193.242]

Router: Linksys WRT54G
Modem: RCA DCM315
No firewalls but the one provided by router.
ISP: RoadRunner (Time Warner NYC)
Geographical Location: NYC (Brooklyn, NY)

I should note that other services, such as nyc.speakeasy.net, and newsgroups, all report me downloading at almost a full 9 Mbps, so I think this Warcraft related.

Just adding that the description given above "About 3 days, I began experiencing ~5 sec lag spikes every 30 sec or so. Latency will remain green during the spikes. The spikes cause everything to freeze during the duration then everything rapidly catches up. If I'm in motion when the spikes occur, I continue to move normally while everything else is frozen in place, then everything catches up rapidly. " -- this seems to happen to me, too. I will also get chat/text lag occasionally

I have more 70's than you :)

Peedeebee - 70 priest || Peedeebeejr - 70 druid || Everoma - 70 mage || Damorey - 70 hunter

Swann

Emerald Dream

13. Re: New York Time Warner Connectivity Issues 07/20/2007 03:17:52 PM PDT

Router: Netgear WGR614
Modem: Toshiba PCX2500
Firewall: none
ISP: TWC Roadrunner
Location: Brooklyn, NY (NYC)
Issue: Since approx. 7/17, latency spikes into yellow and sometimes red. Even when numbers are low, game will freeze then resume and as someone else said, "fast-forward" to catch up. This occurs every minute or so. Sometimes even more often. Never had similar issues before.

I use two servers. Problems occur with both

"Home server" Emerald Dream:

Tracing route to 62-241-255-83.customer.karistelefon.fi [62.241.255.83]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms user-12ld141.cable.mindspring.com [69.86.132.129]
2 6 ms 8 ms 6 ms 10.47.0.1
3 6 ms 9 ms 8 ms pos0-0-nycmnys-rtr1.nyc.rr.com [24.29.100.21]
4 9 ms 8 ms 6 ms pos5-0-nycmnys-rtr2.nyc.rr.com [24.29.119.6]
5 8 ms 8 ms 7 ms cpe-24-29-130-58.nyc.res.rr.com [24.29.130.58]
6 9 ms 8 ms 9 ms tenge10-1-0.nycmnya-rtr1.nyc.rr.com [24.29.119.129]
7 8 ms 9 ms 7 ms tenge-2-0-0.nwrknjmd-rtr.nyc.rr.com [24.29.119.110]
8 10 ms 9 ms 9 ms pop2-new-P4-0.atdn.net [66.185.137.21]
9 8 ms 7 ms 7 ms bb2-new-P3-0.atdn.net [66.185.137.18]
10 16 ms 10 ms 11 ms bb1-nye-P4-0.atdn.net [66.185.152.196]
11 9 ms 7 ms 7 ms pop1-nye-P0-0.atdn.net [66.185.151.49]
12 15 ms 8 ms 7 ms sl-gw37-nyc-12-0.sprintlink.net [144.232.228.73]
13 10 ms 15 ms 7 ms sl-bb21-nyc-4-0.sprintlink.net [144.232.13.65]
14 10 ms 8 ms 7 ms sl-bb25-nyc-11-0.sprintlink.net [144.232.13.1]
15 17 ms 9 ms 10 ms sl-bb20-msq-2-0.sprintlink.net [144.232.20.74]
16 9 ms 9 ms 10 ms sl-bb21-msq-15-0.sprintlink.net [144.232.9.110]
17 94 ms 93 ms 95 ms sl-bb20-cop-14-0.sprintlink.net [144.232.19.30]
18 93 ms 90 ms 92 ms sl-bb21-cop-15-0.sprintlink.net [80.77.64.34]
19 100 ms 103 ms 104 ms sl-bb21-sto-14-0.sprintlink.net [213.206.129.34]
20 102 ms 101 ms 101 ms sl-gw10-sto-15-0.sprintlink.net [80.77.96.42]
21 102 ms 107 ms * sle-finne1-2-0.sprintlink.net [80.77.97.102]
22 109 ms 107 ms 109 ms hki2r5.k.fv.fi [217.78.198.185]
23 109 ms 110 ms 118 ms ktab-k.cust.fv.fi [217.78.199.118]
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.

Secondary server: Thorium Bortherhood

Tracing route to 12-129-225-4.attens.net [12.129.225.4]

over a maximum of 30 hops:

1 1 ms 1 ms 1 ms user-12ld141.cable.mindspring.com [69.86.132.129]
2 7 ms 7 ms 7 ms 10.47.0.1
3 7 ms 8 ms 6 ms pos0-0-nycmnys-rtr1.nyc.rr.com [24.29.100.21]
4 7 ms * 7 ms 24-29-104-198.nyc.rr.com [24.29.104.198]
5 8 ms 6 ms 7 ms pos1-1-nycmnya-rtr2.nyc.rr.com [24.29.130.58]
6 7 ms 8 ms 8 ms tenge-3-0-0.nycsnyoo-rtr1.nyc.rr.com [24.29.119.114]
7 8 ms 8 ms 7 ms te-3-1.car3.NewYork1.Level3.net [4.78.168.45]
8 16 ms 7 ms 7 ms att-level3-oc192.NewYork1.Level3.net [4.68.127.150]
9 80 ms 83 ms 86 ms tbr1.n54ny.ip.att.net [12.123.0.90]
10 78 ms 79 ms 79 ms cr1.n54ny.ip.att.net [12.122.10.113]
11 77 ms 77 ms 80 ms cr1.cgcil.ip.att.net [12.122.1.190]
12 78 ms 79 ms 77 ms tbr2.cgcil.ip.att.net [12.122.10.162]
13 81 ms 78 ms 79 ms tbr2.sl9mo.ip.att.net [12.122.10.46]
14 77 ms 80 ms 78 ms tbr2.la2ca.ip.att.net [12.122.10.14]
15 77 ms 76 ms 78 ms 12.127.3.189
16 82 ms 77 ms 79 ms 12.122.255.74
17 79 ms 77 ms 78 ms mdf001c7613r0003-gig-10-1.lax1.attens.net [12.129.193.242]
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.

Note

< Ilterendi >

Silvermoon

14. Re: New York Time Warner Connectivity Issues 07/20/2007 03:21:00 PM PDT

Road Runner
NYC
Silvermoon

Every 30 seconds or so I get a 3-5 second lag spike; running in place midcast and whatnot, then everything catching up all at once. Impossible to play on, and obviously a huge hinderance to raiding. :/

Tracing route to 12.129.233.40 over a maximum of 30 hops

1 * * * Request timed out.

2 9 ms 8 ms 8 ms ge4-1.nycmnyu-rtr2.nyc.rr.com [24.29.104.193]

3 18 ms 9 ms 10 ms pos6-0-nycmnyrdc-rtr2.nyc.rr.com [24.29.113.218]

4 56 ms 12 ms 11 ms tenge-2-0-0.nycsnyoo-rtr1.nyc.rr.com [24.29.119.98]

5 9 ms 9 ms 13 ms te-4-1.car3.NewYork1.Level3.net [4.78.182.45]

6 9 ms 9 ms 10 ms ggr2-p360.n54ny.ip.att.net [192.205.33.93]

7 157 ms 83 ms 82 ms tbr1.n54ny.ip.att.net [12.123.3.57]

8 79 ms 77 ms 79 ms cr1.n54ny.ip.att.net [12.122.10.113]

9 79 ms 77 ms 80 ms cr1.cgcil.ip.att.net [12.122.1.190]

10 85 ms 80 ms 87 ms tbr2.cgcil.ip.att.net [12.122.10.174]

11

[ Post edited by Note ]

No one ever said I was a Hallmark™ card.

Follow - Human warlock
Note - Well groomed druid
Overture - Wannabe mage

Natsuki

< Sakura Yume >

Durotan

15. Re: New York Time Warner Connectivity Issues 07/20/2007 04:09:06 PM PDT

Ysera

Tracing route to 206.17.111.8 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 16 ms 21 ms 15 ms 10.52.64.1
3 10 ms 10 ms 8 ms 24-168-128-30.nj.rr.com [24.168.128.30]
4 17 ms 25 ms 11 ms 24-168-128-57.nj.rr.com [24.168.128.57]
5 10 ms 9 ms 8 ms pos3-0-nycmnyc-rtr1.nyc.rr.com [24.29.101.245]
6 12 ms 10 ms 8 ms tenge2-0-0.nycmnyrdc-rtr2.nyc.rr.com [24.29.119.142]
7 11 ms 11 ms 10 ms tenge-2-0-0.nycsnyoo-rtr1.nyc.rr.com [24.29.119.98]
8 8 ms 9 ms 11 ms te-3-2.car3.NewYork1.Level3.net [64.156.82.81]
9 16 ms 8 ms 13 ms att-level3-oc192.NewYork1.Level3.net [4.68.127.150]
10 17 ms 23 ms 14 ms tbr2.n54ny.ip.att.net [12.123.0.94]
11 18 ms 13 ms 17 ms tbr1.cb1ma.ip.att.net [12.122.10.21]
12 16 ms 14 ms 14 ms 12.127.5.93
13 25 ms 21 ms 17 ms 12-122-254-14.attens.net [12.122.254.14]
14 37 ms 23 ms 24 ms mdf001c7613r0004-gig-12-1.bos1.attens.net [12.130.0.174]
15 * * * Request timed out.
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.

Dawn

< JTP >

Cho'gall

16. Re: New York Time Warner Connectivity Issues 07/20/2007 04:18:27 PM PDT

Router: Netgear WGT624
ISP: Earthlink//Time Warner Cable
Location: NYC [Queens, NY]

Server -- Cho'gall

----------------------------------------------------------------------------------
Tracing route to 63.241.255.101 over a maximum of 30 hops


 1     1 ms     1 ms     1 ms  user-1087hri.cable.mindspring.com [64.131.199.114] 

  2    31 ms     9 ms     9 ms  10.42.32.1 

  3     7 ms    11 ms    13 ms  pos0-0-nycmnyl-rtr2.nyc.rr.com [24.29.98.161] 

  4    10 ms     9 ms     9 ms  tenge10-0-0.nycmnya-rtr1.nyc.rr.com [24.29.119.181] 

  5     *       29 ms    11 ms  tenge-3-0-0.nwrknjmd-rtr.nyc.rr.com [24.29.119.106] 

  6    10 ms    10 ms    34 ms  pop2-new-P4-0.atdn.net [66.185.137.21] 

  7    37 ms    47 ms    11 ms  bb2-new-P3-0.atdn.net [66.185.137.18] 

  8     9 ms    12 ms    11 ms  bb1-nye-P4-0.atdn.net [66.185.152.196] 

  9    11 ms    13 ms    12 ms  pop2-nye-P0-0.atdn.net [66.185.151.65] 

 10    12 ms    10 ms     9 ms  192.205.34.45 

 11    52 ms    56 ms    53 ms  tbr2.n54ny.ip.att.net [12.122.105.74] 

 12    58 ms    55 ms    57 ms  tbr2.wswdc.ip.att.net [12.122.10.54] 

 13    53 ms    54 ms    51 ms  cr2.wswdc.ip.att.net [12.122.2.41] 

 14    51 ms    54 ms    52 ms  cr1.attga.ip.att.net [12.122.1.173] 

 15    57 ms    62 ms    59 ms  tbr2.attga.ip.att.net [12.122.12.54] 

 16    66 ms    56 ms    58 ms  tbr1.dlstx.ip.att.net [12.122.2.89] 

 17    57 ms   151 ms   161 ms  br2.dlstx.ip.att.net [12.123.16.209] 

 18    95 ms    56 ms    55 ms  12.122.255.226 

 19    56 ms    66 ms    72 ms  mdf001c7613r0003-gig-10-1.dal1.attens.net [63.241.193.10] 

 20     *        *        *     Request timed out.

 21     *        *        *     Request timed out.

.

.

.

.

30     *        *        *     Request timed out.

Trace complete.

[edit] -- For greater ease in viewing/reading data

[ Post edited by Dawn ]

Ganymeda

< Ascent >

Farstriders

17. Re: New York Time Warner Connectivity Issues 07/20/2007 04:38:49 PM PDT

I'm not using a router

TWC customer

Tracing route to 72.5.213.101 over a maximum of 30 hops

1 8 ms 6 ms 5 ms 10.34.224.1

2 8 ms 5 ms 6 ms pos2-3-nycmnyc-rtr2.nyc.rr.com [24.29.97.89]

3 8 ms 5 ms 6 ms tenge8-0-0.nycmnya-rtr2.nyc.rr.com [24.29.119.133]

4 * * 6 ms tenge-3-0-0.nycsnyoo-rtr1.nyc.rr.com [24.29.119.114]

5 6 ms 7 ms 6 ms te-3-2.car3.NewYork1.Level3.net [64.156.82.81]

6 6 ms 7 ms 7 ms att-level3-oc192.NewYork1.Level3.net [4.68.127.150]

7 77 ms 78 ms 77 ms tbr1.n54ny.ip.att.net [12.123.3.57]

8 77 ms 77 ms 77 ms cr1.n54ny.ip.att.net [12.122.10.113]

9 74 ms 74 ms 74 ms cr1.cgcil.ip.att.net [12.122.1.190]

10 87 ms 76 ms 78 ms tbr2.cgcil.ip.att.net [12.122.10.170]

11 78 ms 85 ms 77 ms tbr2.st6wa.ip.att.net [12.122.10.62]

12 77 ms 75 ms 75 ms 12.127.6.198

13 75 ms 76 ms 77 ms 12.118.34.18

14 75 ms 76 ms 80 ms border8.t8-1-bbnet2.sef.pnap.net [63.251.160.82]

15 * * * Request timed out.

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.

and here is another for good measure

Tracing route to 72.5.213.101 over a maximum of 30 hops

1 6 ms 5 ms 7 ms 10.34.224.1

2 6 ms 5 ms 5 ms pos2-3-nycmnyc-rtr2.nyc.rr.com [24.29.97.89]

3 5 ms 6 ms 6 ms tenge8-0-0.nycmnya-rtr2.nyc.rr.com [24.29.119.133]

4 8 ms 9 ms 7 ms tenge-3-0-0.nycsnyoo-rtr1.nyc.rr.com [24.29.119.114]

5 7 ms 18 ms 8 ms te-3-2.car3.NewYork1.Level3.net [64.156.82.81]

6 8 ms 7 ms 7 ms att-level3-oc192.NewYork1.Level3.net [4.68.127.150]

7 79 ms 76 ms 77 ms tbr1.n54ny.ip.att.net [12.123.3.57]

8 82 ms 78 ms 77 ms cr1.n54ny.ip.att.net [12.122.10.113]

9 76 ms 74 ms 75 ms cr1.cgcil.ip.att.net [12.122.1.190]

10 77 ms 78 ms 79 ms tbr2.cgcil.ip.att.net [12.122.10.170]

11 77 ms 77 ms 78 ms tbr2.st6wa.ip.att.net [12.122.10.62]

12 75 ms 77 ms 77 ms 12.127.6.198

13 79 ms 77 ms 77 ms 12.118.34.18

14 75 ms 75 ms 76 ms border8.t8-1-bbnet2.sef.pnap.net [63.251.160.82]

15 * * * Request timed out.

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.

Bula

< Elis Guild >

Gorgonnash

18. Re: New York Time Warner Connectivity Issues 07/20/2007 04:40:51 PM PDT

Server -- Gorgonnash
Location -- Manhattan, NYC

At times the connection appears to be very stable. However then I will hit a pocket of extreme lag and updates will stop for anywhere from 5 to 30 seconds. This results in either some crazy "fast forward" action or a disconnection.

Tracing route to 63.241.255.84 over a maximum of 30 hops

1 2 ms <1 ms <1 ms 192.168.1.1
2 20 ms 17 ms 15 ms 10.54.0.1
3 12 ms 11 ms 10 ms ge2-1-nycmnyd-rtr1.nyc.rr.com [24.29.104.157]
4 20 ms 18 ms 19 ms pos10-0-nycmnya-rtr2.nyc.rr.com [24.29.97.38]
5 * 13 ms 11 ms tenge-3-0-0.nycsnyoo-rtr1.nyc.rr.com [24.29.119.114]
6 17 ms 18 ms 18 ms tenge-2-1-0.nwrknjmd-rtr.nyc.rr.com [24.29.119.154]
7 15 ms 11 ms 16 ms pop2-new-P4-1.atdn.net [66.185.141.225]
8 17 ms 12 ms 13 ms bb2-new-P3-0.atdn.net [66.185.137.18]
9 18 ms 15 ms 14 ms bb1-nye-P4-0.atdn.net [66.185.152.196]
10 18 ms 18 ms 15 ms pop2-nye-P0-0.atdn.net [66.185.151.65]
11 12 ms 13 ms 18 ms 192.205.34.45
12 55 ms 62 ms 53 ms tbr2.n54ny.ip.att.net [12.122.105.74]
13 65 ms 58 ms 64 ms tbr2.wswdc.ip.att.net [12.122.10.54]
14 68 ms 66 ms 62 ms cr2.wswdc.ip.att.net [12.122.2.45]
15 78 ms 57 ms 62 ms cr1.attga.ip.att.net [12.122.1.173]
16 65 ms 57 ms 58 ms tbr2.attga.ip.att.net [12.122.12.118]
17 60 ms 57 ms 59 ms tbr1.dlstx.ip.att.net [12.122.2.89]
18 58 ms 83 ms 59 ms br2.dlstx.ip.att.net [12.123.16.209]
19 63 ms 58 ms 145 ms 12.122.255.226
20 109 ms 116 ms 76 ms mdf001c7613r0003-gig-10-1.dal1.attens.net [63.241.193.10]
21 * * * Request timed out.
....

< Pirate Life >

Tichondrius

19. Re: New York Time Warner Connectivity Issues 07/20/2007 04:54:56 PM PDT

Q u o t e:
NY:
server: tichondrius

Tracing route to 12-129-225-41.attens.net [12.129.225.41]

over a maximum of 30 hops:

1 7 ms 9 ms 9 ms 10.64.192.1
2 10 ms 10 ms 7 ms cpe-24-29-130-65.nyc.res.rr.com [24.29.130.65]
3 18 ms 7 ms 8 ms pos7-0-nycmnyl-rtr1.nyc.rr.com [24.29.100.122]
4 10 ms 9 ms 14 ms tenge10-0-0.nycmnyrdc-rtr1.nyc.rr.com [24.29.119.117]
5 8 ms 10 ms 13 ms tenge-0-0-0.nwrknjmd-rtr.nyc.rr.com [24.29.119.94]
6 9 ms 11 ms 11 ms pop2-new-P4-1.atdn.net [66.185.141.225]
7 9 ms 10 ms 8 ms bb2-new-P3-0.atdn.net [66.185.137.18]
8 14 ms 9 ms 12 ms bb1-nye-P4-0.atdn.net [66.185.152.196]
9 10 ms 11 ms 7 ms pop2-nye-P0-0.atdn.net [66.185.151.65]
10 8 ms 9 ms 10 ms 192.205.34.45
11 84 ms 92 ms 82 ms tbr1.n54ny.ip.att.net [12.122.105.14]
12 84 ms 82 ms 84 ms cr1.n54ny.ip.att.net [12.122.10.113]
13 82 ms 82 ms 81 ms cr1.cgcil.ip.att.net [12.122.1.190]
14 82 ms 84 ms 82 ms tbr2.cgcil.ip.att.net [12.122.10.174]
15 83 ms 91 ms 83 ms tbr2.sl9mo.ip.att.net [12.122.10.46]
16 85 ms 84 ms 86 ms tbr2.la2ca.ip.att.net [12.122.10.14]
17 82 ms 90 ms 83 ms 12.127.3.189
18 86 ms 83 ms 85 ms 12.122.255.74
19 84 ms 83 ms 85 ms mdf001c7613r0003-gig-10-1.lax1.attens.net [12.129.193.242]
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 *

^ this is my mains server.

this is my alts server, agamaggan:

Tracing route to 63.241.255.14 over a maximum of 30 hops

1 22 ms 10 ms 7 ms 10.64.192.1
2 7 ms 7 ms 7 ms gig5-0nycmnyj-rtr1.nyc.rr.com [24.29.130.65]
3 10 ms 7 ms 7 ms pos7-0-nycmnyl-rtr1.nyc.rr.com [24.29.100.122]
4 9 ms 10 ms 9 ms tenge10-0-0.nycmnyrdc-rtr1.nyc.rr.com [24.29.119.117]
5 9 ms 9 ms 9 ms tenge-0-0-0.nwrknjmd-rtr.nyc.rr.com [24.29.119.94]
6 8 ms 12 ms 9 ms pop2-new-P4-1.atdn.net [66.185.141.225]
7 10 ms 9 ms 9 ms bb2-new-P3-0.atdn.net [66.185.137.18]
8 10 ms 12 ms 9 ms bb1-nye-P4-0.atdn.net [66.185.152.196]
9 10 ms 10 ms 9 ms pop2-nye-P0-0.atdn.net [66.185.151.65]
10 * 9 ms 9 ms 192.205.34.45
11 90 ms 57 ms 55 ms tbr2.n54ny.ip.att.net [12.122.105.78]
12 58 ms 55 ms 55 ms tbr2.wswdc.ip.att.net [12.122.10.54]
13 56 ms 55 ms 55 ms cr2.wswdc.ip.att.net [12.122.2.37]
14 60 ms 55 ms 54 ms cr1.attga.ip.att.net [12.122.1.173]
15 50 ms 53 ms 52 ms tbr2.attga.ip.att.net [12.122.12.118]
16 50 ms 49 ms 49 ms tbr1.dlstx.ip.att.net [12.122.2.89]
17 50 ms 50 ms 51 ms br2.dlstx.ip.att.net [12.123.16.209]
18 52 ms 51 ms 51 ms 12.122.255.226
19 51 ms 56 ms 52 ms mdf001c7613r0003-gig-10-1.dal1.attens.net [63.241.193.10]
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.

i have no issue playing on my alts server thats really noticeable solo farming in a low populated zone (not really sure other then that) but its border-line unbearable to play my main. is there any real issue with servers or..?

http://www.youtube.com/watch?v=N19iSDpfFh4

TECHNICAL SUPPORT