Time Warner, RoadRunner, Brighthouse players please read.

[Mirthgar]

I know it's on the LOTRO forums but this thread below indicates the situation, (I'd recreate it in it's entirety for DDO but really the only changes I'd make to it for DDO are to the 'how to tracert' would be "tracert gls.ddo.com" (no quotes) and the folder names would be different other than that the effects/steps et al are the same.

http://forums.lotro.com/showthread.php?465900-Time-Warner-RoadRunner-Brighthouse-players-please-read

That linked thread sums up what we believe is occurring.

[tikwid]

i keep getting: 'tracert' is not recognized as an internal or external command,
operable program or batch file, when i type "tracert gls.ddo.com" (no quotes) into the command prompt?

Am i doing something wrong?

[Mirthgar]

i keep getting: 'tracert' is not recognized as an internal or external command,
operable program or batch file, when i type "tracert gls.ddo.com" (no quotes) into the command prompt?

Am i doing something wrong?

It should look exactly like this when typing it in:


tracert gls.ddo.com

Note that there's a space between tracert and gls and that you don't need the http:// or www. etc.

[AreeSoothsayer]

Huh. If the problem is the port in the 9000 and 9010 range, why can't DDO make it so the client has other ports it would allow connection to.

I tried manually forcing it to use port 8080 and got up to where it went fullscreen to connect but failed.

Add: Decided to place my tracert here, maybe if we get enough of them and such one of the eggheads might figure it out.

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.


Tracing route to gls.ddo.com [74.201.102.13]
over a maximum of 30 hops:

1 <1 ms 1 ms 1 ms 192.168.1.1
2 13 ms 9 ms 35 ms 10.65.32.1
3 11 ms 14 ms 14 ms ten9-0-1.bkfd08-ser1.bhn.net [72.31.200.241]
4 14 ms 10 ms 11 ms ten0-2-0-4.bkfd01-car1.bhn.net [72.31.201.29]
5 14 ms 33 ms 39 ms ten1-0-1.bkfd01-cbr1.bhn.net [72.31.200.164]
6 20 ms 22 ms 16 ms te0-7-0-0-lsanca4-rtr3.socal.rr.com [66.75.161.104]
7 16 ms 23 ms 15 ms 107.14.19.32
8 27 ms 17 ms 20 ms ae-0-0.pr0.lax10.tbone.rr.com [66.109.6.133]
9 16 ms 24 ms 25 ms te4-3.mpd01.lax05.atlas.cogentco.com [154.54.11.133]
10 17 ms 16 ms 15 ms te0-1-0-1.ccr21.lax01.atlas.cogentco.com [154.54.6.189]
11 57 ms 56 ms 76 ms te0-1-0-3.ccr21.iah01.atlas.cogentco.com [154.54.44.237]
12 87 ms 81 ms 79 ms te0-0-0-7.ccr21.atl01.atlas.cogentco.com [154.54.29.1]
13 85 ms 79 ms 77 ms te0-0-0-7.ccr21.dca01.atlas.cogentco.com [154.54.28.213]
14 84 ms 88 ms 85 ms te0-5-0-6.ccr21.jfk02.atlas.cogentco.com [154.54.42.22]
15 92 ms 91 ms 93 ms te0-0-0-1.ccr22.bos01.atlas.cogentco.com [154.54.25.114]
16 93 ms 93 ms 107 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.130]
17 89 ms 96 ms 93 ms 38.104.252.70
18 * * * Request timed out.
19 92 ms 93 ms 91 ms turbine-7.border1.bsn003.pnap.net [64.95.76.202]
20 112 ms 87 ms 93 ms 74.201.102.154
21 126 ms 100 ms 106 ms 74.201.102.13

Trace complete.

[Nemonon]

I moved to Socal about 3 days ago and just got my internet and cable turned on today, both Time Warner. After i got it all up and running I played DDO for about 1 1/2 to 2 hours with absolutely no issue.

After logging off for a bit and trying to return, I found that I could connect to my world via the launcher and choose my character perfectly fine but cannot make it past the next load screan. I keep getting stuck on that screen and after waiting 4-5 minutes get a dialog box telling me the "Connection to the Server has been lost".

Is this the same issue your link is refering to? My impression was that people couldn't get passed the initial launcher. Is my only option really to just complain to TW/cancel my DDO sub until it is fixed?

Are all players from these ISPs also unable to play or just a select few? I imagine that would be a large subsect of DDO/LOTROs player base.

Why did they not experiance these problems prior to 20 June?

Thank you for your time and any replies you may have.

[robdrew]

I know it's on the LOTRO forums but this thread below indicates the situation, (I'd recreate it in it's entirety for DDO but really the only changes I'd make to it for DDO are to the 'how to tracert' would be "tracert gls.ddo.com" (no quotes) and the folder names would be different other than that the effects/steps et al are the same.

http://forums.lotro.com/showthread.php?465900-Time-Warner-RoadRunner-Brighthouse-players-please-read

That linked thread sums up what we believe is occurring.
I have very little technical skills and the tracert thing is a foriegn language to me. I am so frustrated being disconnected over and over. Please take the lead for us and liason with Time Warner...who i thought was a sister company to turbine..ty

[Mirthgar]

Is this the same issue your link is refering to? My impression was that people couldn't get passed the initial launcher.

The results of this have been issues with the game client (the 3d 'character select and beyond client that is) being able to connect/maintain a connection using UDP packets on ports 9000 to 9010 (though certainly other ports may be affected) but only on the specific routed ISP network.

Is my only option really to just complain to TW/cancel my DDO sub until it is fixed?

No just that the issue stems from how these packets are getting routed on these ISP's backbone connections, until they can pin it down to a specific location/locale or network hardware though they need items like the tracert's to establish commonality.

Are all players from these ISPs also unable to play or just a select few? I imagine that would be a large subsect of DDO/LOTROs player base.

Ones whose connections specifically route through the affected systems appear to encounter these issues so its a subset of a subset of users for the games as well as these ISP's I'm sure.

Why did they not experiance these problems prior to 20 June?

That I do not know, but the timing is coincedental to the beginning of the East Coasts first major heatwave, other than that though there were no major internet related issues occurring.

Thank you for your time and any replies you may have.

I've put my replies in green above.

[Nemonon]

Thanks for the quick reply. I've contacted Time Warner and gave them Wargfoe's existing ticket number from the LOTRO forums. My tracert is listed below. I have no idea what I'm looking at there.

I did however set up a static IP address and port forwarding for my ddo client. I set the port range to 8080 to 9000 and was able to login on the first try. I'll post back here if and when i get dced again with an update.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Hvymetal>tracert gls.ddo.com

Tracing route to gls.ddo.com [74.201.102.13]
over a maximum of 30 hops:

1 43 ms 25 ms 19 ms cpe-76-89-132-1.socal.res.rr.com [76.89.132.1]
2 29 ms 13 ms 13 ms tge7-3.cmrlcavy-cer01.socal.rr.com [76.166.6.185
]
3 26 ms 22 ms 23 ms tge0-8-0-12.vnnycajz-ccr01.socal.rr.com [72.129.
13.128]
4 24 ms 22 ms 38 ms 72.129.13.0
5 34 ms 21 ms 22 ms ae-5-0.cr0.lax00.tbone.rr.com [66.109.6.102]
6 19 ms 17 ms 19 ms 66.109.9.24
7 216 ms 210 ms 210 ms te2-5.ccr02.lax05.atlas.cogentco.com [154.54.13.
229]
8 22 ms 20 ms 21 ms te0-3-0-5.mpd22.lax01.atlas.cogentco.com [154.54
.44.129]
9 61 ms 58 ms 59 ms te0-2-0-3.mpd22.iah01.atlas.cogentco.com [154.54
.45.9]
10 82 ms 85 ms 83 ms te0-1-0-6.mpd22.atl01.atlas.cogentco.com [154.54
.2.33]
11 80 ms 83 ms 82 ms te0-0-0-7.mpd22.dca01.atlas.cogentco.com [154.54
.3.66]
12 88 ms 104 ms 91 ms te0-4-0-2.mpd22.jfk02.atlas.cogentco.com [154.54
.41.26]
13 114 ms 94 ms 97 ms te0-0-0-6.ccr21.bos01.atlas.cogentco.com [154.54
.5.249]
14 219 ms 207 ms 215 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
15 104 ms 96 ms 97 ms 38.104.252.70
16 111 ms 98 ms 99 ms border1.te7-1-bbnet1.bsn003.pnap.net [63.251.128
.43]
17 96 ms 94 ms 99 ms turbine-7.border1.bsn003.pnap.net [64.95.76.202]

18 96 ms 92 ms 91 ms 74.201.102.154
19 106 ms 98 ms 98 ms 74.201.102.13

Trace complete.

C:\Users\Hvymetal>

[Darrknes]

Same issues, just posting my TRACERT for others to see

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Brian>tracert gls.ddo.com

Tracing route to gls.ddo.com [74.201.102.13]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 14 ms 11 ms 7 ms cpe-76-88-64-1.san.res.rr.com [76.88.64.1]
3 11 ms 11 ms 11 ms ge7-4.sndaca78-cer01.socal.rr.com [76.167.13.185]
4 18 ms 14 ms 24 ms 72.129.1.228
5 15 ms 14 ms 15 ms agg22.lsanca4-rtr1.socal.rr.com [72.129.1.0]
6 25 ms 23 ms 23 ms 107.14.19.32
7 17 ms 13 ms 16 ms ae-0-0.pr0.lax10.tbone.rr.com [66.109.6.133]
8 16 ms 26 ms 15 ms te4-3.mpd01.lax05.atlas.cogentco.com [154.54.11.133]
9 28 ms 15 ms 12 ms te0-1-0-5.ccr21.lax01.atlas.cogentco.com [154.54.82.149]
10 51 ms 57 ms 51 ms te0-1-0-6.ccr21.iah01.atlas.cogentco.com [154.54.0.226]
11 76 ms 79 ms 84 ms te0-0-0-2.ccr21.atl01.atlas.cogentco.com [154.54.24.17]
12 79 ms 79 ms 80 ms te0-0-0-3.ccr21.dca01.atlas.cogentco.com [154.54.28.201]
13 86 ms 84 ms 88 ms te0-2-0-2.ccr21.jfk02.atlas.cogentco.com [154.54.26.186]
14 92 ms 92 ms 88 ms te0-2-0-1.ccr22.bos01.atlas.cogentco.com [154.54.44.94]
15 86 ms 92 ms 87 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
16 * * * Request timed out.
17 98 ms 94 ms 100 ms border1.te7-1-bbnet1.bsn003.pnap.net [63.251.128.43]
18 90 ms 92 ms 98 ms turbine-7.border1.bsn003.pnap.net [64.95.76.202]
19 94 ms 91 ms 90 ms 74.201.102.154
20 89 ms 92 ms 91 ms 74.201.102.13

Trace complete.

[witchboy2012]

Heres my tracert as of 4:30 pm pst.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\tracert gls.ddo.com

Tracing route to gls.ddo.com [74.201.102.13]
over a maximum of 30 hops:

1 19 ms 45 ms 22 ms cpe-76-166-240-1.socal.res.rr.com [76.166.240.1]
2 13 ms 31 ms 14 ms tge2-4.vnnycajz-cer01.socal.rr.com [76.166.17.89]
3 25 ms 23 ms 23 ms tge0-8-0-0.vnnycajz-ccr01.socal.rr.com [72.129.13.12]
4 19 ms 15 ms 25 ms 72.129.13.0
5 42 ms 18 ms 31 ms 107.14.17.132
6 16 ms 49 ms 21 ms 66.109.9.24
7 15 ms 14 ms 16 ms te2-5.mpd01.lax05.atlas.cogentco.com [154.54.10.249]
8 13 ms 47 ms 14 ms te0-1-0-5.mpd21.lax01.atlas.cogentco.com [154.54.82.157]
9 67 ms 57 ms 53 ms te0-2-0-3.mpd21.iah01.atlas.cogentco.com [154.54.44.249]
10 80 ms 82 ms 79 ms te0-2-0-7.mpd21.atl01.atlas.cogentco.com [154.54.2.221]
11 80 ms 84 ms 78 ms te0-0-0-7.mpd21.dca01.atlas.cogentco.com [154.54.28.197]
12 87 ms 85 ms 82 ms te0-1-0-3.mpd21.jfk02.atlas.cogentco.com [154.54.3.46]
13 92 ms 88 ms 107 ms te0-3-0-2.ccr21.bos01.atlas.cogentco.com [154.54.44.14]
14 98 ms 88 ms 88 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.134]
15 89 ms 104 ms 89 ms 38.104.252.70
16 92 ms 89 ms 107 ms border1.te7-1-bbnet1.bsn003.pnap.net [63.251.128.43]
17 93 ms 98 ms 92 ms turbine-7.border1.bsn003.pnap.net [64.95.76.202]
18 98 ms 93 ms 93 ms 74.201.102.154
19 175 ms 247 ms 230 ms 74.201.102.13

Trace complete.

[Nemonon]

Ok so changing the port ranges had very little impact on actual connection. It seems that the real reason I connected right away after changing the ports is because I chose a different character. After I played this character for about an hour I changed zones (Market to House J) and then disconnected from the server. I have not been able to log back into that character since.

I did however log into a different character that had not yet experianced the disconnect. This character loaded in flawlessly and I have experianced no lagg or connection errors while playing the game. This is the third character that I have experianced this phenomenon on and I have no doubt that i will be able to play him until I happen to randomly zone one time and fail to connect. At that point the character will become unplayable like the rest.

My question is this: Is this behavior still consistent with the assumption that it is an ISP issue?

[Gadget2775]

It look like the same issue on the surface. I'd bet that the characters who get hung up unhang eventually. I had a level 7 toon on Sat that I was pushing up to 8 for the stone. It played well long enought to hit 8, but locked up b4 I could level and use a stone. Took trying randomly over the next 3 hours but I finally managed a stable connection...Well stable long enough to level up at least :)

If your toon is perma-locked that's another issue.

[Nemonon]

Ok I've been doing some testing and am starting to believe that the connection phenonmenon does not happen at random. It seems to be linked to the number of times you move from one main instance to another. Quests and Taverns don't seem to make a difference.

For example: I was able to play soley in house J for the better part of two hours. The minute I started jumping between houses I locked that toon out. The next toon I ran from Market in and out of House J, in and out of House D and tried to zone into house P then I locked that toon out. I duplicated this last path with 3 other toons and they all locked out at the same point. Once a toon hangs at a load screen in game it will then start hanging in the first load screen at login and no loger be available to play.


Anyone else do any testing on this? I only have 3 toons left that I can access and I'm not eager to lock them all out right now.

[Nemonon]

Gadget,

So you have actually had a character become unable to load into the game and then become available to play again later?

Funny I ran into this issue today while I was trying to push my TR from 7-8 so I could use my stone as well. Not that its related but I know the frustration you felt. lol

I'm deploying at the end of next month and am really hoping to cap epic lvls on 4 of my toons while I am on my 30 days leave.

If I have to wait for Time Warner to fix this I may as well just cancel my sub and play Diablo. I wish Turbine would send a rep to my house and trouble shoot this. He can sleep in my spare room. I'll even take him surfing. Any volunteers?

[InfidelofHaLL]

The information that mirthgar has provided has been forwarded to TWC's tier 3+ support team and they are looking into it.

[Tharlak]

Well, just got effected by this as well.

I now have 3 characters that are locked out, can't log them into the game from the character selection screen.

Two of the characters got to move around a bit, harbor to market place (talk to fatespinner), back to harbor. One played through Lords of Dust.

Where both of those locked up was when entering the spinners prison, character selection says they are in the spinners prison.

The other loaded in meridia, instantly hung and I can not log in to this character anymore.

In all cases, they hang at the initial load screen then eventually get disconnected from server.

joy.

[InfidelofHaLL]

Well, just got effected by this as well.

I now have 3 characters that are locked out, can't log them into the game from the character selection screen.

Two of the characters got to move around a bit, harbor to market place (talk to fatespinner), back to harbor. One played through Lords of Dust.

Where both of those locked up was when entering the spinners prison, character selection says they are in the spinners prison.

The other loaded in meridia, instantly hung and I can not log in to this character anymore.

In all cases, they hang at the initial load screen then eventually get disconnected from server.

joy.


your best bet is to go see the real world for a couple days till they get is hashed out

[kyrapelicano]

Since Before day 25, i did experience several disconnects, but only 1 or 2 for the night.
On beta, the disconnects went wide up, almost in each 5 min i got disconect. In the normal server at the same time no problem what so ever.
and now in menace expasion after spending 63 euros in the expanse, the connection became as it was in beta, and even maybe more unstable.

So unless you did change the computers or servers in the last couple of days the problem his yours. I can say that i did play lol or wow, champions online without loosing integraty but even if the ping went up, i never got disconnected, only here the disconnections become frequent.

It impossible to play like this, lol.... the last time i went for training, i lost integraty and the game disconnect 8 times in 100m... even in instances are unstable and when i get back up i died.

I really need a solution. and dont give me craps about ipv6, that before expansion that problem was not so bad...

[kyrapelicano]

I have friends from portugal, that never reported this, sometimes a dc, with the same internet. and they are playing now. i am on the vent.

I can examplyfy, in house denieth from the ship teleport to the druid trainer i got dc 8 times....

I payed 63 euros, several months maybe more then 1.5 years now.... and after this i can't played the game .

[Nemonon]

Kyrapelicano,

I had stability issues like yours far before I encountered the phenomenon we are describing here, I call it a phenomenon only because I am not yet convinced its all on the ISP.

My instability and frequent disconnection issue was completely eliminated by using a static ip address and port forwarding. Have you tried that yet?

[kyrapelicano]

i can't define a static ip, by isp dont offer that change, or at least that i know

[Nemonon]

Kyrapelicano,

Go here and select your modem model and DDO and it will give you directions on how to do it.


http://portforward.com/english/routers/port_forwarding/Motorola/SBG6580/Dungeons_+_Dragons_Online.htm

[Nemonon]

Just got off the phone with a teir 3 rep from Time Warner. I am going to try and repeat what it was he just told me.

#1 The issue seems to have stemmed from the expiration from the domain lease on or about 16 June.

#2 Time Warners "Bridge" is waiting on information from Turbine to reestablish a proper connection.

#3 Time Warner will not be making any other inquiries into the issue until Turbine provides them with the required information.

#4 I was about the 4th person that he has talked to today about the issue and that this was the most up to date information available from the complaints. (about 5 minutes before the time stamp on this post)

Now I'm not savy on networks or servers but my understanding from the rep is that maybe the settings for Turbines Domains have changed in some way after the lease expired.

He did however repeat multiple times that the issue is on Turbine. They need to update their information with the ISPs.

[kyrapelicano]

but remained the same

[kyrapelicano]

The problem cannot be from my side, befora the expasion in the main server, it only happen 1 or twice per night (8hours) so not almost in each 5 min, happens cannot be from this side.

Any moderator can assist?

[kyuven]

here's my tracert, still having the issues detailed in the thread today:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.



Tracing route to gls.ddo.com [74.201.102.13]
over a maximum of 30 hops:

1 8 ms 1 ms 1 ms 192.168.1.1
2 12 ms 11 ms 11 ms cpe-72-130-128-1.san.res.rr.com [72.130.128.1]
3 15 ms 6 ms 8 ms ge7-11.sndgcaxt-cer02.socal.rr.com [76.167.9.101
]
4 23 ms 22 ms 24 ms 72.129.2.198
5 31 ms 31 ms 15 ms agg22.tustca1-rtr1.socal.rr.com [72.129.1.2]
6 14 ms 16 ms 16 ms 107.14.19.30
7 15 ms 14 ms 13 ms ae-1-0.pr0.lax10.tbone.rr.com [66.109.6.131]
8 14 ms 18 ms 12 ms te3-3.ccr02.lax05.atlas.cogentco.com [154.54.10.
65]
9 14 ms 18 ms 11 ms te0-3-0-5.mpd22.lax01.atlas.cogentco.com [154.54
.44.129]
10 56 ms 58 ms 61 ms te0-3-0-6.mpd22.iah01.atlas.cogentco.com [154.54
.0.254]
11 77 ms 80 ms 77 ms te0-2-0-7.mpd22.atl01.atlas.cogentco.com [154.54
.2.245]
12 84 ms 79 ms 81 ms te0-0-0-7.mpd22.dca01.atlas.cogentco.com [154.54
.3.66]
13 84 ms 84 ms 82 ms te0-1-0-3.mpd22.jfk02.atlas.cogentco.com [154.54
.6.6]
14 92 ms 91 ms 91 ms te0-2-0-6.ccr21.bos01.atlas.cogentco.com [154.54
.44.22]
15 88 ms 91 ms 90 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
16 90 ms 102 ms 91 ms 38.104.252.70
17 112 ms 91 ms 91 ms border1.te7-1-bbnet1.bsn003.pnap.net [63.251.128
.43]
18 99 ms 97 ms 92 ms turbine-7.border1.bsn003.pnap.net [64.95.76.202]

19 89 ms 89 ms 84 ms 74.201.102.154
20 102 ms 90 ms 91 ms 74.201.102.13

Trace complete.

[Nemonon]

A Brighthouse Rep took the time to post over on the LOTRO forums. Here is what he had to say:

Originally Posted by BHNtechXpert

Hey there,

I received your email and thank you. I just finished reaching out to TWC and hopefully will have an update from a status perspective on the above referenced ticket tomorrow. I must be honest with you however. It is highly unlikely this is a provider side issue and when I mean unlikely I'm talking really unlikely. I don't think you guys realize how many devices and services utilize UDP in that port range in both directions.

I also want to say that it is highly premature and inappropriate for Turbine to blame other parties without having taken the time out to contact them directly. They now have my contact information and I look foward to hearing from and working with them from the Bright House Networks side of the equation so I expect to hear from them. If I don't I will let you guys know.

Just in case they didn't get it the first time email me at BHNtechXpert@mybrighthouse.com

I'll be back in touch and just repeating those of you who are BHN customers I really could use those Bright House Direct Forums posts over at DSLReports. This way I can check your equipment and get this issue working from our network side of the equation.

Thanks again...

[tikwid]

it feels fixed...did whole catatombs chain without a single disconnect....going to bed, lets see how it is in the morning

[Nemonon]

As of Midnight last night I had access to all of my characters and played until 2 am. I did mostly play my wizard though and teleported everywhere hoping I didn't trigger the bug. lol

I don't know who fixed it and I don't care. I imagine we will never know. I can't imagine Time Warner, Brighthouse and Roadrunner all fixed the same thing simultaneously though.

Thanks to whoever found the problem and resolved it though. Nice work.

-Nemo

[kyrapelicano]

in my case the problem mantains.
With the port fowarding, dind't helped.
i am still having crashes. If the problems mantains without solution, i will be forced to close the account. and seek another game. Ashamed that i spended so many month's waitng for druid, and now i can't play.
And the money i have spended including in the buy of the of the expansion and of the collectors edition, so thay can destroy the game and make it impossible to be played.

Since no developer is even reading this, i see no porpose to continue to write.

[Mirthgar]

in my case the problem mantains.
With the port fowarding, dind't helped.
i am still having crashes. If the problems mantains without solution, i will be forced to close the account. and seek another game. Ashamed that i spended so many month's waitng for druid, and now i can't play.
And the money i have spended including in the buy of the of the expansion and of the collectors edition, so thay can destroy the game and make it impossible to be played.

Since no developer is even reading this, i see no porpose to continue to write.

As noted these forums are best for player to player help for official support you need to contact us directly.

Additionally as you stated you are not on the ISP's noted in the title of this thread the issues you are encountering are unrelated to the ones discussed here, please open a tech support request (http://support.turbine.com/ics/support/default.asp?deptID=24001&task=ticket).

[Gadget2775]

Gadget,

So you have actually had a character become unable to load into the game and then become available to play again later?

**snip**

Yes sir. Hung up on an instance change, got the "lost connection to server" message. Tried to reconnect and hung at "looking for log in server". Managed to get back in on that toon about 3 hours later.

[Mirthgar]

We've received reports back on the original thread on the LOTRO forums (http://forums.lotro.com/showthread.php?465900-Time-Warner-RoadRunner-Brighthouse-players-please-read.) that indications are that players are no longer experiencing the issues related to this.

I'll be leaving that thread as well as this one open for another twenty four hours though just to be sure. (Quoting my reply from that thread below for quick reference)


I'll be leaving this thread open* for another twenty four hours to allow for time to confirm everything appears to be stable for the affected players.

(* I'd be closing it only for future clarity because players encountering similar issues down the road in the future may not realize this was a specific incidence rather than a general connectivity issue they might be facing at the time, so as to avoid confusion closing this after a good 'wait and see' time is best).