The short answer
Record whether the problem differs between standard maps and map conditions, or between solo and party play. Then check clock synchronization, the whole party’s crossplay settings and the Automatic server region one at a time. Keep a note of each change and its result. If login itself fails or an official outage is announced, follow the relevant support notice rather than repeating these changes.
Different symptom or still not fixed? Find the next check →Key facts
- Only map conditions fail
- Check device clock synchronization
- Longer waits in a party
- The most restrictive member’s crossplay setting applies to the party
- Server region
- Gameplay → Server → Automatic
Find your symptom
Start with your symptom. Skip steps that do not apply to your setup.
| What you see | What to check | Go to |
|---|---|---|
| Standard maps work, but map conditions do not | An incorrect device clock is one possible cause | Step 2 |
| Queues get longer when playing with friends | Check crossplay settings across the party | Step 3 |
| A server region is selected manually | Compare with the official Automatic recommendation | Step 4 |
Fixes, in order
Continue this issue
Private notes stay in this browser. Nothing is sent automatically. Back up important notes on My Page. PC settings are never changed by this site.
Step 1|Identify what fails and check official notices
Separate login failures from getting stuck after starting matchmaking.
Time: About 2 minutes · Risk: low
- Record whether the lobby opens, when matchmaking stops progressing and the full error message, if any.
- Using what you have already tried, note differences between standard maps and map conditions, and between solo and party play. Do not abandon an active raid just to collect a comparison.
- Open the official support and update links below. If they announce a relevant outage or maintenance, follow that recovery guidance first.
The checked date on this article is not a live server-status report or a guarantee that the service is currently available.
Step 2|Synchronize the Windows clock and restart the PC
Embark recommends this for matchmaking and map-condition access problems.
Time: About 3–5 minutes · Risk: low
- Close the game and save any open work.
- Open Windows Settings → Time & language → Date & time, and enable Set time automatically.
- Select Sync now. Its position and wording may vary with your Windows version.
- Once synchronization finishes, restart the PC, reopen ARC Raiders and check whether the same symptom remains.
If a managed PC prevents this change, ask its administrator rather than trying to remove the restriction.
Step 3|Check every party member’s crossplay setting
Your own setting can be on while another player’s restriction still limits the party.
Time: About 2 minutes · Risk: low
- Ask whether any party member has crossplay disabled.
- Only if the members are comfortable playing across platforms, have them enable crossplay in their own settings and compare the result.
- Respect a preference to keep crossplay off and continue with the region check. Turning it on does not guarantee an immediate match.
The exact path to the crossplay toggle has not been verified here; do not rely on an invented menu location.
Step 4|Compare with the server region set to Automatic
The official PC instructions specify Gameplay → Server → Automatic.
Time: About 1 minute · Risk: low
- Open settings with the gear icon at the bottom right of the game screen.
- Open Gameplay → Server, note the previous value and choose Automatic.
- Without changing other settings at the same time, check whether matchmaking behaves differently.
Step 5|Prepare a useful report if the problem remains
Explain how far you can get instead of piling on changes that have not helped.
Time: About 3 minutes · Risk: low
- Record the date, time and time zone, your PC storefront and the error text.
- Write one line each for clock synchronization, crossplay settings and the result with Automatic selected.
- Open Embark’s official support link below to check contact options. Hide personal information or unrelated conversations in any screenshots.
Queue length alone does not establish a faulty connection or an account restriction.
Avoid
- Do not factory-reset the router or disable the whole firewall to speed up matchmaking.
- Do not leave an active raid merely to collect comparison data.
- Do not apply error-code fixes from another game to ARC Raiders.
Important cautions
- These settings instructions are for PC. For console menu paths, use the corresponding section of the official support article.
- The October 8, 2026 update changed the map-selection screen. Check the meaning of the setting rather than relying solely on an older screenshot.
FAQ
Why is matchmaking slow in a party when my crossplay is on?
Embark says the most restrictive crossplay setting in the party applies. Check the other members’ settings too. That does not prove crossplay caused this particular delay; compare the result after any agreed change.
The Solo vs. Squads option is missing. Is my configuration broken?
The official 2.0 notes dated October 8, 2026 say Solo vs. Squads was removed from matchmaking options. Do not delete configuration files just because that option is absent. Check official updates for future changes.
Sources
Based on Embark’s official support and patch notes, checked on October 8, 2026. The symptom comparisons and order of checks are editorial guidance, not hands-on proof or a measured success rate. English UI labels are retained from the official instructions.
Embark: matchmaking troubleshooting for PC and consoleEmbark: syncing your device clockEmbark: Frozen Trail 2.0 fixes and known issues, October 8, 2026Embark: ARC Raiders supportARC RaidersJapanese version of this page