What did the Q&A say about OCE?
Wowhead’s liveblog reports Oceanic hosting with a shared US-wide auction house. Grouping with overseas friends can increase latency because a data centre is chosen for the group.
These are reported developer answers, not a RaidMuster network test. They do not supply a promised ping for a particular location or connection.
A shared market does not measure your connection
For planning purposes, separate three questions: where your usual group plays, when its members are available and how the game behaves on each person’s connection. A market boundary does not answer the other two.
A player who lives near the rest of the guild may still have different playing hours. A friend overseas may fit the schedule but experience a less comfortable session. Collect both observations before deciding whether a recurring team works for everyone.
Run one representative group trial
Use the mix of locations you actually expect for your regular group. Ask each participant to note their displayed latency and whether movement, targeting and ability use feel comfortable. Record the session time, group makeup and any disconnects.
Do not turn one trial into a published regional benchmark. Repeat a concerning result before attributing it to a server decision; connection conditions and the test environment can change. The useful outcome is whether your own group wants another session under similar conditions.
| Record | Why it helps |
|---|---|
| Participant location, broadly | Compare sessions without collecting exact addresses. |
| Local start and finish times | Check that the plan is sustainable for each member. |
| Displayed latency and observed problems | Keep measurements separate from impressions. |
| Group composition by location | Avoid comparing unlike sessions as if nothing changed. |
| Agreed follow-up | Decide whether to repeat the test or adjust the schedule. |
Write dates and time zones into invitations
For a mixed Australia, New Zealand and North America group, write an actual date and a named time zone for the organiser. Ask everyone to confirm their local equivalent. Recheck recurring events around daylight-saving changes; a fixed difference written months earlier may stop being correct.
Example invitation: “Please confirm your local start and finish time for this dated event, plus whether the previous test was comfortable on your connection.” This makes availability and connection quality explicit without promising a network result the guild cannot control.
Finish with one shared joining note
Put the chosen ruleset, faction, full character names and agreed hours in the same place. Use the grouping guide for the compatibility decision and the naming guide for character records. If a player cannot join, note the actual obstacle before recommending a reroll or transfer.
Our advice is to settle the repeatable evening first. A geographically broad membership list is valuable only if the people who want to play together can attend and enjoy the session.