Guild Wars 2

Confirmed: Guesting on another server “fixed it”. I’m now playing my toon that was stuck.

Edit -However – Porting within the affected region (Brisban wildlands, in my case) makes the client error reappear. I just completed a storyline quest, and got ported back out, to the disconnect limbo.
-Tried guesting on yet another server, but that didnt help.

-So, the issue remains unsolved

ISP: ComHem
Region: Sweden, Europe (Playing on NA server)
Server: Jade Quarry

Character: Ms Rytera. Stuck in: Brisban Wildlands loading screen, subsequently getting the disconnect-error mentioned in thread title.

Tracert:

C:\>tracert 64.25.33.55 (The /ip command ingame on another toon gave me that ip)

Tracing route to 64.25.33.55 over a maximum of 30 hops

1 63 ms <1 ms <1 ms 192.168.0.1
2 8 ms 8 ms 7 ms c83-253-136-1.bredband.comhem.se [83.253.136.1]

3 9 ms 7 ms 7 ms 213.200.164.177
4 13 ms 16 ms 13 ms 213.200.163.21
5 16 ms 13 ms 13 ms ae52.bar1.Stockholm1.Level3.net [213.242.69.113]

6 163 ms 164 ms 164 ms vl-3506-ve-112.ebr1.Stockholm2.Level3.net [4.69.
158.246]
7 164 ms 174 ms 164 ms ae-44-44.ebr1.Dusseldorf1.Level3.net [4.69.201.2
42]
8 164 ms 166 ms 165 ms ae-45-45.ebr3.Frankfurt1.Level3.net [4.69.143.16
6]
9 163 ms 165 ms 165 ms ae-93-93.csw4.Frankfurt1.Level3.net [4.69.163.14
]
10 174 ms 163 ms 166 ms ae-91-91.ebr1.Frankfurt1.Level3.net [4.69.140.13
]
11 * * * Request timed out.
12 164 ms 163 ms 163 ms ae-43-43.ebr2.Washington1.Level3.net [4.69.137.5
8]
13 167 ms 163 ms 164 ms ae-72-72.csw2.Washington1.Level3.net [4.69.134.1
50]
14 167 ms 167 ms 166 ms ae-71-71.ebr1.Washington1.Level3.net [4.69.134.1
33]
15 * * * Request timed out.
16 165 ms 165 ms 163 ms ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21]
17 164 ms 164 ms 164 ms ae-73-73.csw2.Dallas1.Level3.net [4.69.151.145]

18 * * * Request timed out.
19 163 ms 161 ms 162 ms 4.59.197.34
20 179 ms 198 ms 162 ms 64.25.32.9
21 163 ms 162 ms 161 ms 64.25.32.26
22 166 ms 162 ms 168 ms 64.25.32.82
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.

Yep, tried that. The only difference it made was that i had to wait even longer in the loading screen before it crashed :/

Similar issue here. I just created a ticket.
https://forum-en.gw2archive.eu/forum/support/account/Porting-from-DT-to-Brisban-Disconnect/first#post4258623

-edit- Adding traceroute-

C:\>tracert 64.25.38.238

Tracing route to 64.25.38.238 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 7 ms 9 ms 7 ms c83-253-136-1.bredband.comhem.se [83.253.136.1]

3 9 ms 14 ms 8 ms 213.200.164.175
4 13 ms 13 ms 11 ms 213.200.163.19
5 13 ms 13 ms 13 ms 212.73.250.133
6 164 ms 163 ms 163 ms vl-3501-ve-115.ebr1.Stockholm2.Level3.net [4.69.
202.21]
7 164 ms 167 ms 174 ms ae-41-41.ebr1.Dusseldorf1.Level3.net [4.69.201.2
30]
8 162 ms * 164 ms ae-47-47.ebr3.Frankfurt1.Level3.net [4.69.143.17
4]
9 173 ms 162 ms 163 ms ae-73-73.csw2.Frankfurt1.Level3.net [4.69.163.6]

10 167 ms 163 ms 163 ms ae-71-71.ebr1.Frankfurt1.Level3.net [4.69.140.5]

11 * * * Request timed out.
12 163 ms 163 ms 163 ms ae-41-41.ebr2.Washington1.Level3.net [4.69.137.5
0]
13 163 ms 165 ms 165 ms ae-82-82.csw3.Washington1.Level3.net [4.69.134.1
54]
14 161 ms 164 ms 165 ms ae-81-81.ebr1.Washington1.Level3.net [4.69.134.1
37]
15 * * * Request timed out.
16 163 ms 162 ms 162 ms ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21]
17 161 ms 161 ms 175 ms ae-73-73.csw2.Dallas1.Level3.net [4.69.151.145]

18 * * 192 ms ae-2-2503.ear1.Dallas1.Level3.net [4.69.146.10]

19 160 ms 159 ms 160 ms 4.59.197.34
20 161 ms 159 ms 159 ms 64.25.32.9
21 162 ms 161 ms 159 ms 64.25.32.26
22 162 ms 163 ms 163 ms 64.25.32.82
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.

C:\>

I posted it here since it is not a hardware/computer related issue, but I appreciate that you looked it up. I created a ticket, now we just have to wait… and hope.

So, I was going to do the storyline on some of my alts, to get some more keys and goodies, activated the first story in season 2 on my ranger that was standing around in dry top, and headed to the portal from DT to Brisban. Loading screen takes forever, and the end result is: “Client disconnected from server”.
I restarted the client, tried logging on my ranger again, but she’s stuck in limbo. -Character selection screen claims she’s in Brisban, but the loading screen still does the same thing; disconnects.
My other toons seem to work just fine but I dont dare take any of them to Brisban just yet.
I am currently running a “-repair” on my client to see if that resolves the issue….
…pause for the last 2 minutes of client repairs…
-The repair ran it’s course, but the problem persists. My poor Ms Rytera seems to be stuck in a flawed matrix. Please help her, she needs to feed her pets!

(Code=7:11:3.191:101)