Short answer
There is no confirmed one-click fix yet. The useful path is to separate a local connection failure, a party/crossplay mismatch, and a release-side incident, then capture the exact reproduction.
What the launch evidence supports.
Steam discussions currently include connection complaints, and the launch conversation includes reports of custom-lobby failures with PS5 friends. Those are player reports, not an official incident notice. Older demo-era notes mention a matchmaking timer stuck at 00:00 and players not loading; they explain why this symptom is worth checking, but they do not prove that the same bug remains in the release.
Run the checks in this order.
- Confirm the build and platform pair.Update the game on every client. Write down whether the session is PC–PC, PC–Xbox, PC–PS5, or includes Switch; the launch crossplay status is not identical across those pairs.
- Split queue from party failure.Try one public queue and one invite-only lobby. If public matchmaking works but the invite fails, preserve the party platform pair and host/join role in the report.
- Retry with a clean session.Exit the game, restart the platform client, and create a fresh lobby. On Steam, verify the installed files if the same client still fails; treat this as a diagnostic step, not a guaranteed fix.
- Capture the failure.Save the exact error, queue timer, mode, party size, timestamp, and screenshot or clip. Do not merge a historical demo workaround with a current SpeedRunners 2 fix without a repeat test.
Symptom to evidence map.
| Symptom | Most useful next check | Evidence state |
|---|---|---|
| Network Error | Does a solo/public queue fail too, or only a party invite? | Player report |
| 00:00 matchmaking | Record whether players never load or the timer never starts. | Historical lead |
| PS5 custom lobby crash | Re-test with a fresh host and note the crossplay pair. | Needs verification |
FAQ
Is SpeedRunners 2 down when I see Network Error?
Not necessarily. Current launch discussions contain connection and friend-lobby reports, but they do not establish a global outage. Record your platform, region, queue, party size, and exact error before treating it as a server-wide incident.
Why does matchmaking stay at 00:00?
A 00:00 matchmaking timer was called out in older demo-era patch notes. That is useful historical context, not proof of the current release cause. Check the live build and report whether the timer is stuck, the lobby loads without players, or the game returns Network Error.
What should I include in a bug report?
Include platform, crossplay pair, game mode, party size, host or join role, approximate time, build number, the exact message, and a screenshot or short clip. This turns a vague connection complaint into a repeatable case.