Where most complaints about this service are coming from, over the last 24 hours.
Shows where the service URL was unreachable during the detected outage periods. Percentages indicate the share of failed checks from monitoring locations in each country.
Tap what’s going wrong — one click helps thousands of others see the outage.
If the game refuses to start, the first place to look is your GPU drivers — outdated drivers are responsible for a huge chunk of launch failures. Update them, then verify the integrity of game files through Steam or the Epic Games Launcher. Also check that your system meets the minimum requirements: ARC Raiders demands a modern DirectX 12-capable GPU.
Latency issues in a co-op shooter like this can make the game unplayable. Try these steps:
Random crashes mid-match usually point to one of three things: overheating, RAM instability, or a driver conflict. Monitor your GPU and CPU temperatures with MSI Afterburner or HWiNFO. If temps are fine, run a RAM stress test with MemTest86. Also try lowering in-game graphics settings — some shader combinations trigger driver crashes on specific hardware configs.
If you can't get past the login screen, first check whether the game's authentication servers are having issues — the official ARC Raiders social channels usually post status updates. Clear your credential cache by logging out of the launcher completely and back in. If the error code mentions a token failure, deleting the local config folder and re-authenticating tends to fix it.
Blurry textures or missing geometry mid-game almost always mean the game files are corrupted or the shader cache needs to be rebuilt. Run a file integrity check through your launcher. Additionally, delete the shader cache folder — the game will rebuild it on next launch, which takes a few extra minutes but resolves most visual glitches.
If the matchmaking queue spins forever, the issue is often a firewall or NAT type problem. Open the required UDP ports for the game in your router settings, and make sure Windows Firewall isn't blocking the executable. A NAT type of 'Strict' will consistently break session joining.