Prodmore?
Last night we had to continually boot players from prodmore that DC’d while loading in.
Pretty much everyone who plays on Oceanic servers is having this problem.
I am currently stuck on loading screen, trying to load into SD… sigh
How has this not been addressed yet?
First time playing in years and I can’t even queue for dungeons because it keeps getting stuck loading at 3/4 and by the time I manage to log in because of “Character with that name is already in game” nonsense I’ve been kicked and have to queue for an hour again.
2 days without any acknowledgement from blizzard, it is pretty clear at this stage they are not interested in fixing this, but hey when 99% of your player base are not experiencing this issue, its not really worth your time and effort right?
In any case, the issue for oceanic players seems to occur when you get into a US instance phase, so the trick at the moment for any oceanic players is - avoid US instances at all costs.
- With dungeons this means finding a group of oceanic friends to queue up with or walk in with together.
- With battlegrounds you cannot avoid this, it often lumps you into a US instance, so queue for for this at your own risk.
If that’s the case, it might be related to an ISP routing issue to the US-based dungeons. I pinged someone about the issue, so I’m hoping there will be more info regarding this when their work hours start.
In the meantime, can someone from OCE region run a traceroute to both 137.221.105.2 (US West) and 24.105.62.129 (US Central), then post the results here?
Results from Traceroute from Sydney Aus first IP of 137.221.105.2
Tracing route to 137.221.105.2 over a maximum of 30 hops
1 1 ms <1 ms <1 ms mygateway [10.0.0.138]
2 7 ms 7 ms 9 ms gateway.nb08.sydney.asp.telstra.net [58.162.26.72]
3 8 ms 7 ms 8 ms ae10.ken-ice301.sydney.telstra.net [203.50.61.81]
4 10 ms 9 ms 9 ms bundle-ether25.ken-core10.sydney.telstra.net [203.50.61.80]
5 9 ms 11 ms 10 ms bundle-ether1.pad-gw11.sydney.telstra.net [203.50.6.61]
6 9 ms 10 ms 17 ms 203.50.13.90
7 10 ms 10 ms 9 ms i-10302.sydo-core03.telstraglobal.net [202.84.222.170]
8 9 ms 10 ms 10 ms i-10403.sydo-core04.telstraglobal.net [202.84.222.130]
9 147 ms 146 ms 146 ms i-10604.1wlt-core02.telstraglobal.net [202.84.141.225]
10 153 ms 149 ms 151 ms i-93.tlot02.bi.telstraglobal.net [202.84.253.86]
11 150 ms 149 ms 149 ms xe-11-2-0.edge1.losangeles6.level3.net [4.68.62.9]
12 * 149 ms * ae-2-3614.ear4.LosAngeles1.Level3.net [4.69.211.214]
13 150 ms 150 ms 150 ms 4.7.26.166
14 150 ms 152 ms 153 ms ae1-br01-csla1.as57976.net [137.221.89.33]
15 * * * Request timed out.
16 * * * Request timed out.
17 152 ms 151 ms 150 ms et-0-0-0-pe03-swlv10.as57976.net [137.221.83.85]
18 150 ms 152 ms 168 ms 137.221.105.2
Results of the second Traceroute 24.105.62.129
Tracing route to 24.105.62.129 over a maximum of 30 hops
1 1 ms <1 ms <1 ms mygateway [10.0.0.138]
2 7 ms 7 ms 8 ms gateway.nb08.sydney.asp.telstra.net [58.162.26.72]
3 8 ms 7 ms 8 ms ae10.ken-ice301.sydney.telstra.net [203.50.61.81]
4 9 ms 10 ms 9 ms bundle-ether25.ken-core10.sydney.telstra.net [203.50.61.80]
5 9 ms 10 ms 9 ms bundle-ether1.pad-gw11.sydney.telstra.net [203.50.6.61]
6 11 ms 8 ms 10 ms 203.50.13.90
7 9 ms 12 ms 9 ms i-10102.sydp-core03.telstraglobal.net [202.84.222.133]
8 15 ms 10 ms 10 ms i-10401.sydo-core04.telstraglobal.net [202.84.222.138]
9 146 ms 146 ms 146 ms i-10604.1wlt-core02.telstraglobal.net [202.84.141.225]
10 151 ms 153 ms 150 ms i-93.tlot02.bi.telstraglobal.net [202.84.253.86]
11 151 ms 149 ms 150 ms xe-11-2-0.edge1.losangeles6.level3.net [4.68.62.9]
12 * 153 ms 149 ms ae-2-3614.ear4.LosAngeles1.Level3.net [4.69.211.214]
13 150 ms 151 ms 150 ms 4.7.26.166
14 208 ms 226 ms 220 ms ae1-br01-csla1.as57976.net [137.221.89.33]
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 199 ms 199 ms 199 ms et-0-0-0-pe03-eqch2.as57976.net [137.221.69.55]
19 204 ms 207 ms 203 ms 24.105.62.129
What’s your normal ping if you play with a group of US players?
I know that wasn’t directed at me - but between 150 - 230 depending on where the server is based. (e.g. east or west).
Also to note - the issue doesn’t seem to occur very frequently for me, only about 1 in every 5 times I am getting phased in with US players. (As oppose to 35+ times with oceanic players where I did not experience this once).
I’m experiencing the same issues. Tracert to those IP’s gives the same ping as I get when playing with US realm players. So when I manage to actually connect to a queued instance my ping is normal. The issue occurs when either loading into the dungeon or occasionally from looting a boss. If the dungeon is hosted on an oceanic realm and does manage to load the US players experience the very long load time (1-5 minutes), followed by issues with looting.
I’ve had the issue make an epic ring vanish into thin air. Hope to see it fixed soon, although it could just be ISP.
Those tests are showing 150 to West and 204 to Central, so that seems okay. It could be that another route is being used to one of the servers periodically from the ISP or a routing peer in Oceania (Telstra controls most of the routing there).
And here lies the god damn problem with this issue. People aren’t going to put up with OCE people having to time-out before they can get in to an instance so we get the boot. By the time we log back in we’re on a dungeon cooldown and can’t queue for another 10 minutes.
4 Likes
Having the same issue on Barthilas (Oceanic)
First time I closed WoW after a few minutes, restarted everything tried to log back in and got the “character with this name already exists” bug. Logging into an alt cleared that one up.
Tried again and got dc’d on the load screen after 5 minutes. Same error coming back in, logged an alt and then back to main.
It hung on the load screen again and eventually put me into the dungeon.
But now the other people trying to get into the dungeon are having the same issues as well, I’m not able to get the button to find more people as they get booted from the group (Not my doing, I’m trying to be patient and see how they go getting in)
My ping is normal for a non-oce dungeon (Max 195) for which I don’t have much lag.
Same thing happens when i enter Battleground, Sometimes i get in after half the time has expired.
Good news everyone! We’ve progressed from getting stuck at 3/4 bar, to getting stuck at a full bar. Same crap, different load bar.
3 Likes
Totally worth $20 a month. So glad they sacked the 30 staff in Sydney looking after the servers.
1 Like
Same issue since yesterday. It took 30 minutes for the server to remove my stuck character. Meanwhile I could login to other characters. Hopefully it is resolved with this reset, but hey knowing Blizz they’ll just say it is our fault, not theirs.
same issue, like 1 in 20 dungeons work… only dungeon ive been able to get into is one where 3 others were from oceanic servers experiencing the same issue
I am done, Only Fool’s will continue to put up with this kinda service. 13hrs left on my account.
Same issue, have only successfully loaded into 1/4 dungeons 