Ability/Loot Lag on Oceanic Servers Despite Normal Latency

I repeat - when they ask for it, we can do it. Stop being pedantic.

they’ve already asked for it.
that’s the point of the stickies.

help them to help you, provide relevant information.
“server bad” gives absolutely zero information to work with.

what rubbish, this is effecting everyone in OCE, the info you want us to provide is just stalling, blizzard needs to take some responsibility for their own servers

2 Likes

sorry chief, but this one I cant agree with you on.
this problem has existed at LEAST since bfa beta, and is still ongoing infesting a new expansion.
Can only imagine the chaos if it was this bad in the US or EU…

Providing them with latency and network information from “your” end will not fix an issue that, by all accounts, seems to be on “their” end. If pretty much everyone who has replied to this post since 2018 has claimed that their home/world latency was never high, then what would be the point in providing them with more of that information?

Additionally, they specifically logged in to view Oce sharding issues… And never bothered replying about anything since then. They even stopped asking for WinMTRs. They just wanted to know how, when where and why you were suffering from the problems by that point. None of the supplied WinMTRs helped them (because it’s not our issue).

Can we put the myth that it’s on our end to rest please, or in fact anywhere but on Blizzard’s end?

The fact that everyone is keeping normal home/world latency while servers go down and after a crash that happens 3-4+ times per day.

The fact that characters move back a few minutes in time to a previous location, have quest progress removed that they made in the last few minutes, lose loot they obtained in the last few minutes (myself included) after everyone lags out and is finally able to log back in?

The fact it’s happening to people coming from US servers onto Oceanic servers, where our local ISPs would have nothing to do with it, and if it’s a transit provider problem that would be on Blizzard to escalate?

This is on Blizzard to resolve, and as this has been happening since BFA, the only resolution I can see is wait for people to stop logging in, because that’s what we had to do last time. We had to wait for people to lose interest and move on from playing WoW just to have stable servers.

It’s gone well beyond being acceptable, funny, amusing.

It’s just pathetic now.

7 Likes

This is not something that’s only affecting a certain number of players on Oceanic. It’s affecting everyone server wide (be they in Shadowlands zones or in org for example) in the same way across all Oceanic servers. Mass DC’s - as in entire zones DC constantly. Maldraxxus last night was one such example. Everyone in the zone DC’ed at the same time… Lag was affecting everyone in the same way.

It is currently middle of the day on a Tuesday afternoon, Oceanic time for those of us on the east coast of Australia. The game is currently barely playable with serverwide lag affecting SL zones and Org currently… The AH is barely functional, same with vendors and mail. My alt is currently stuck in no-man’s land after getting DC’ed trying to zone into a LFD and unable to log back onto it. My main is currently trying to sell something to a vendor in Ardenweald… I say trying because it’s not selling due to lag.

And this is how it is 24/7 for us. It has existed since BFA and persists. It only eased somewhat when mass people quit the game (which is a crappy business practice if that is how Blizzard are dealing with this). The Oceanic server itself is unstable and has been since BFA. If it’s like this now while most people are at work or school, what’s going to happen during our summer break when everyone is on holidays and when raiding starts?

8 Likes

At least a blue post saying “we are aware of the issue”. But apparently, they are not aware of any issues (read from another post who spoke to GM). How are they not aware of any issues with a 2000+ thread in their own Tech Support forum?

(Lag selling, spell casting, DC zone in LFD, unable to login after DCed - “name already existed” error)

1 Like

This was a black mark against BfA’s launch until it was fixed and now it seems like Blizzard has learned nothing in this regard since it’s now a black mark against Shadowland’s launch too. It’s particularly bad in Ardenweald for some reason and it can make the zone unplayable at times.

It’s cruel how the only thing that can fix it is turning war mode on while oceanic Alliance dominate all the WQs and will kill all Horde on sight despite having the 25% bonus which oceanic Alliance don’t deserve since it’s based on the US server war mode representation and not oceanic war mode representation. Such a broken system all around.

I’ve noticed this problem throughout all of BFA. It wasn’t every 5mins like it was at launch or even now but it was there and happened almost daily. Considering this problem was never fixed and is a big issue again, I think using this thread is fine.

I’m not sure it was even actually ‘fixed’. I think the problem became less noticeable after a real reduction in the number of people playing on Oceanic over the months. I know in my own main’s guild, half of the people who logged in during the first couple of months disappeared from the game, and they have only started coming back over this week. Whatever is wrong with the Oceanic server, it just can’t seem to cope with significant loading. I dunno whether they are using 6 year old technology that they just haven’t bothered to update but whatever it is, it is actually and factually driving subscribers away.

PS: One of our servers, Frostmourne, is among the most populated servers in the game. It is 10th on the list on Wowprogress, for example. So in case people think the game doesn’t get busy down here, rethink that.

1 Like

so it started right around the time when people started getting forcibly switched to NBN?

It started exactly the time that BFA launched. Please, honestly - they have already said amongst many different ISPs, there was no connection to the issues.

We have no latency issues, and you can port to another zone and it might just fix itself. It is definitely a Blizzard server issue with sharding. Unless you’re suggesting that being in Warmode can sometimes fix the fact you have NBN?

Again, I don’t mean to be combative but there is 2,000+ posts here. This isn’t our first rodeo with this issue.

they all use the same cables.
why would there be any difference between ISPs?

Exactly … this is not an internet issue and never has been. Ability/loot lag that only occurs in outside zones and not in instances etc is caused by server issues and they know it.

1 Like

It’s also ignorant of the fact that NBN is uniquely Australian and Oceanic servers cover most of the Asia Pacific region - what would your logic be for New Zealanders or Singaporeans with the same loot lag etc, for example?

I assure you our cables don’t stretch that long.

do you think the signals just travel through the air?

the only time i’ve experienced this type of thing from an oceanic server, is after having joined a group and then left, and the game hasn’t punted the character back to my original shard properly.

I mean, if you’re going to be both obtuse and rude, we can play ball if you want.

So… Basically… What you’re saying… Is that the issues are directly related to the servers? Is that what I’m reading?

Unless you’re on our lord and saviour NBN and it just favours US realms magically.

that’s not what i’m saying at all, but i’m pretty sure you know that.

if i connect to an oceanic server, i’m going from my pc, through the hops to the oceanic servers and back.
if i connect to an oceanic server and join a group on US servers, i’m going from my pc, through the hops to the oceanic server, then through the hops to a US server, then back through the oceanic server and back to me.
one is going to take longer than the other.

this back and forth isn’t solving anything.

if people are experiencing issues, they need to be part of the solution and provide information which can be worked with.

“it’s broken, fix it!” gives nothing to work with.