
If PAYDAY 3 stops at login or says Failed to fetch game config data, check the time of the latest official announcement and compare with a player on another network. Starbreeze publishes updates in the PAYDAY 3 news feed and in the official PAYDAY Discord, while your platform may report a separate sign-in incident. The message tells you the game failed to retrieve its configuration, but it gives no reliable diagnosis by itself. The links below lead to live sources, and this page does not display a live uptime reading.
See whether an outage has been confirmed
Read the most recent official posts for the maintenance window, affected platforms and any follow-up saying the service has come back. Compare the time in the notice with the first time you saw the error, including the time zone. A notice from yesterday might describe an ended incident, while a notice without an end time only confirms what the publisher reported at that moment. If there is no current statement, leave the service status unconfirmed and test from a second connection or ask another player to try right now.
On console, check PlayStation Network status or Xbox status. On PC, check Epic Games status if you use Epic, or see whether you can sign in to Steam and load another Steam online function. A green service page for your platform establishes little about PAYDAY-specific login or matchmaking. When multiple players outside your household fail at the same stage, give support that information together with the connection time and platform.
Pinpoint the stage that fails
If the error appears before the main menu, focus first on login, the installed build and any maintenance notice. If both people reach the menu but a specific invitation fails, start with the PAYDAY 3 crossplay guide and reproduce it from a fresh party. If everyone loads into other sessions and only one host's game drops players, try a different host on the same contract. Starbreeze's March 2026 peer-to-peer rollout lets the host's game serve the session, so a session problem and an account-service problem can show up at different points. Peer-to-peer announcement
A public lobby can also be quiet even when sign-in and hosting work. Compare the result of joining a friend, hosting privately and using CRIME.NET, where practical. The Steam player count measures people running the game on Steam, and a rise or fall in that count provides no official confirmation of a service incident. The exact stage where the problem occurs is more useful in a report than a graph or a screenshot of an old outage post.
Fix Failed to fetch game config data on PC
Close PAYDAY 3 and its launcher normally so you can update and restart from a clean login state. Check the client's update queue, then use the storefront's built-in file verification tool when available. Starbreeze's PC support also recommends updating your operating system and graphics drivers for technical issues, which is especially relevant when the game fails to start or crashes. If you installed PC mods, remove them before the retest and compare with the same action on the clean build. Starbreeze technical support
If the message persists, do one controlled network comparison. Try Ethernet instead of Wi-Fi or a second trusted connection you are already entitled to use, and record which test worked. If you use a VPN or proxy, test once without it so you can distinguish routing differences from client changes. Keep the other settings steady and avoid deleting saves or changing account links in response to this message alone.
Check PS5 and Xbox Series separately
On PS5, close the game from the console interface, look for its update, check PSN status and sign back in on the profile that owns the game. On Xbox Series, fully quit PAYDAY 3 so the retest starts a new session, then check the queue for game and system updates. On either console you can run its built-in network test, and testing another online title can help determine whether the problem extends beyond PAYDAY 3. Note the platform, the version shown and whether the error occurs right after a download or at every startup.
If your friend is on another storefront, look for any platform-specific release timing in the patch archive. For example, Starbreeze said the 3.9.1 hotfix initially reached Steam, Epic and PS5 before Xbox and Microsoft Store later the same day. This kind of stagger can give users different builds for part of a rollout. The changelog's platform note and the actual installed versions are the details to compare. 3.9.1 rollout
Send a report that support can reproduce
If the issue repeats after updating and using a clean build, include the exact wording, time and time zone, platform and storefront, installed version, and the last screen you reached. Say whether another player on a separate connection reproduced it and whether a different host or network changed the result. Attach the error screenshot or any diagnostic files requested by the publisher, while leaving login codes and passwords out of the report. Use the Starbreeze support form to send the details.
Compare a wider outage with one failing device
A failure across multiple connections is more informative when people report it within the same few minutes and at the same stage. Ask them whether only the invitation failed, whether the game gives the same configuration error, or whether the launcher cannot connect either. If each friend sees a different symptom, keep those observations separate in your report. Starbreeze's release-era server issue notice is an example of a publisher-confirmed incident, and its date puts those specific problems in the 2023 launch period. Starbreeze launch incident notice
If your console reaches other online games and your friend gets through PAYDAY 3 sign-in, pause any changes to the account while you test repeated startup on your own device. Changing both the linked account and the installation at once would make it difficult to trace whether a restart, update or connection fixed it. If other people begin to reproduce the same symptom later, add the new times to the support request. A report that keeps the device, network and time together is easier to compare with a later maintenance notice.
Retest after a maintenance window or full restart
Check the latest maintenance update first, then begin a fresh session once the launcher has completed any downloads. Confirm whether you reach the main menu and can enter a private heist before rebuilding a full group. If a fresh session still fails and the status remains unconfirmed, send the information you already collected to support instead of assuming the original incident continued. Store the exact error text so you can tell whether the next failure occurs at the same step.