Error 60k / 60030 / 60015: Can't enter the Persistent Universe
Tracked since 22 Aug 2026 · Last researched 29 Aug 2026
Problem
Persistent Universe entry is blocked by Error 60030, Error 60015, Error 40015, or another 60k lobby code after Star Citizen reaches the Universe login flow.
These codes do not all have the same cause. Error 60015 and 40015 now have their own region-switching route; Error 60030 and other 60k errors may clear with time or need the limited fallback checks below.
Applies to Alpha 4.10.x LIVE · Current
Best current action
Check service status, wait, then retry once
For Error 60030 or another 60k code without a more specific route, check RSI Status, wait, and retry once. If the code is 60015 or 40015, change region before entering the Universe instead.
CIG says some 60k login errors clear with time. There is no published success rate, but this is the safest first move because it changes nothing on your account or PC.
What to do
- Confirm that the displayed code is Error 60030, Error 60015, or another 60k-series lobby error.
- Check RSI Status for a current Persistent Universe or platform disruption.
- If service is disrupted, wait until RSI marks it resolved; otherwise, leave the game and launcher closed for a while.
- Try entering the Persistent Universe once more.
If the same code returns, stop repeating the login attempt and move to the route that matches your code.
Another option
If the lobby error is 60015 or 40015
Change region for Error 60015 or 40015
CIG says these two codes mean the instance selected for you is not working properly. Choosing another region is the current code-specific fix, but it may still fail to clear the error.
What to do
- Confirm that the displayed code is Error 60015 or its 40015 variant.
- Before selecting Enter Universe, change the login region to a different available region.
- Try entering the Persistent Universe in that region.
Another login region must be available to select. A more distant region may give you higher latency for that session, and changing region is not guaranteed to clear the error.
Diagnostic checks
These checks can identify the affected state, but they are not fixes.
Report the code and every failed step
If the applicable troubleshooting fails, CIG asks for both successful and failed results on Issue Council and directs blocked players to RSI Tech Support. Reporting is not an immediate fix.
What to check
- Record the exact 60k code and the troubleshooting steps that succeeded or failed.
- Add those details to a relevant Issue Council report.
- If access is still blocked after the supported troubleshooting, send a ticket to RSI Tech Support.
Use the applicable low-impact route before escalating the case. CIG does not promise an immediate recovery or give a support response time.
Other options
Try the DNS checks once
CIG sends the 60k family to its 30k troubleshooting, which includes a DNS flush and an optional DNS-server change. This can help a local DNS problem, but it cannot release a backend or account-side lock.
Steps
- Close Star Citizen, the RSI Launcher, and other open applications.
- Open Command Prompt as administrator, run ipconfig /flushdns, and wait for the success message.
- Try entering the Persistent Universe once.
- If a local DNS problem remains plausible, try one reputable alternate DNS server, then retry once.
You need administrator access; use a trustworthy provider if you change DNS servers. Flushing the cache is temporary. Changing the DNS server alters a Windows network setting until you change it back.
If lower-impact paths fail
Escalation
If the repeated 60k started after a crash or ship-bed logout
Use Character Repair only as a last resort
CIG's linked troubleshooting leaves Character Repair for repeated errors that began after a crash or ship-bed logout. Results reported for Error 60030 conflict, so do not use it as a general 60k fix.
What to do
- Use the lower-impact workaround that matches the displayed error first and report the incident on Issue Council.
- Sign in on the RSI website and open Account Dashboard, Settings, then Character Repair.
- Start the repair and do not interact with the account while it processes.
- Wait at least one hour before logging back into Star Citizen.
Try the wait-and-retry and bounded DNS routes first. Character Repair cannot be stopped or reversed once started. It moves your character to its spawn point, sends equipped items to inventory, leaves already missing items missing, and may still fail to restore access.
What's not worth trying
Do not rely on the Arena Commander trick
For Error 60030, one older player report says an Arena Commander session helped and another says it did not. No current 4.10.x test or CIG 60k guidance confirms this route.
Do not treat firewall whitelisting as a 60k fix
CIG currently lists firewall whitelisting under Error 19k. It is not in the 30k checklist that the current 60k guidance tells players to follow.
Related
Build status
CIG still lists the 60k login family in Alpha 4.10.x and has not named an exact affected hotfix.
Known Issue Continues · LIVE
Boundaries and evidence
Use this page only for a 60k-series lobby code. Error 19k, 30k, 41013, 60010, 60012, 60016, 60029, 64006, 64010, and an infinite loading screen are different incidents.
CIG is still investigating the causes of Error 60030, Error 60015, and other 60k codes, so there is no universal fix.
No current independent Alpha 4.10.x success rate was available for waiting, changing region, DNS checks, or Character Repair.
Older player reports may reflect different builds, shard expiry, or a CIG backend hotfix rather than the step they tried.
Data sources
RSI Known Issues · RSI Support · RSI Status · Reddit