Error 60009: Matchmaking is unavailable
Tracked since 11 Sept 2026 · Last researched 11 Sept 2026
Problem
Matchmaking is unavailable at the lobby when Error 60009 appears with the message “Matchmaking currently disabled.” CIG’s service records use the same wording when new game connections are turned off for maintenance.
The exact error is still confirmed in the available Issue Council listing. It has not been officially marked fixed, even though RSI Status showed all services operational when this page was checked.
Applies to Alpha 4.10.x LIVE (4.10.0-live.12519617 deployment authority; exact current hotfix not established) · Current
Best current action
Check RSI Status, then wait for matchmaking to return
Check RSI Status before changing anything locally. If matchmaking, new connections, or the Persistent Universe are disabled or degraded, wait until service is restored and retry once. If status is operational and Error 60009 remains, report the exact case instead of cycling through unrelated fixes.
RSI uses disabled-matchmaking notices when new connections are unavailable. Waiting does not alter your installation or account, but there is no measured Error 60009 success rate.
What to do
- Confirm the displayed code is Error 60009 and the message says 'Matchmaking currently disabled.'
- Check RSI Status for maintenance, degraded Persistent Universe service, or disabled new connections.
- If a matching incident is active, wait until RSI marks the affected service operational or the incident resolved.
- Try entering the game once after service restoration.
Wait only while RSI Status shows a matching maintenance or degraded-service condition. If RSI Status is already operational and the same error returns, do not keep repeating login attempts or local changes.
Diagnostic checks
These checks can identify the affected state, but they are not fixes.
Report a persistent 60009 while status is operational
STARC-218268 is the matching confirmed Issue Council record. Reporting helps CIG investigate a case that outlasts a service incident, but it is not an immediate fix.
What to check
- Record the exact Error 60009 code, displayed message, time, and whether RSI Status was operational.
- Add the reproduction and every attempted step to STARC-218268 if the report is accessible.
- Use RSI Support if game access remains blocked and Issue Council reporting does not resolve access.
Issue Council and RSI Support do not promise immediate access or a response time.
What's not worth trying
Do not count on restarting the launcher
One exact-code guide suggests closing the game and launcher, but it gives no player result, build, or source. There is no evidence that a restart overrides disabled matchmaking.
Do not treat a full launcher logout as a fix
Signing out and back in is repeated in an unsourced guide, but no exact Error 60009 execution shows that refreshing authentication restores matchmaking.
Do not borrow file verification from Error 60012
The only retained verification suggestion groups Error 60009 with Error 60012 and provides no 60009-specific result. A remedy for another lobby code is not evidence for this one.
Do not generalize region switching to 60009
A guide claims another region can help, but it provides no named Error 60009 result. Region switching is documented for other lobby codes, not for this exact disabled-matchmaking message.
Do not use Character Repair for Error 60009
RSI’s current Character Repair guidance does not name Error 60009. The only exact-code suggestion also mixes in Error 60012 and gives no successful execution, while repair itself is irreversible.
Boundaries and evidence
Use this page only when the code is 60009 and the message says matchmaking is currently disabled. Other 600xx codes, generic login failures, and an unnamed loading screen can have different causes and fixes.
RSI Status showed Platform, Persistent Universe, and Arena Commander operational when checked on September 11, 2026. That snapshot does not prove every player could connect or that Error 60009 was fixed.
The accessible STARC-218268 listing says Confirmed, but its build field conflicts with official Alpha 4.10.0 build information. The direct report, contribution history, and any fix target could not be checked.
No controlled or independently corroborated Alpha 4.10.x success was found for waiting, restarting, signing out, verifying files, switching region, or Character Repair.
Data sources
RSI Known Issues · RSI Support · RSI Status · Issue Council · Reddit · YouTube · Specialist Community