Is This Game Down
This one's theirsReported

RuneScape: Dragonwilds "unknown network error" fix

Trying to browse or join a friend's or public game throws "An unknown network error has occurred. Please try again." — typically when joining a session rather than during normal solo play.

Also appears as: dragonwilds an unknown network error has occurred, runescape dragonwilds unknown network error, dragonwilds cant join eos error, dragonwilds network error please try again

The best-documented cause is a genuine outage, not a local problem. On December 24–25, 2025, Epic Online Services (EOS) — the backend Dragonwilds uses for session listing and joining — suffered a widespread authentication failure that broke matchmaking and joining across many unrelated games at once, independently reported by piunikaweb.com. Dragonwilds players confirmed the same pattern in Steam Discussions, including a thread titled "EOS are back online" once Epic resolved it.

Outside of an active EOS outage, at least one player traced a persistent version of this error to a corrupted local EOS certificate/cache — a community-found explanation, not something Jagex has documented.

Operational

No problems reported in the last 15 minutes.

Is RuneScape: Dragonwilds down right now? Live reports →

What to try

  1. 01

    Check for a wider Epic Online Services outage before troubleshooting

    Check whether it's a wider Epic Online Services outage before troubleshooting locally. A confirmed EOS-wide authentication failure on December 24–25, 2025 broke joining and matchmaking in Dragonwilds and several unrelated games simultaneously, and resolved on its own once Epic fixed it.

    Confirmed
  2. 02

    Try disconnecting your Epic account in settings (one report)

    If EOS looks fine elsewhere and it's just you, try disconnecting your Epic account from in-game settings — one player reported the game working normally without an active Epic account link.

    Reported
  3. 03

    Use -log to confirm a certificate failure, then clear the EOS cache (one report)

    As a deeper fix, launch with the -log Steam launch option to confirm it's a certificate failure, then clear the Epic Online Services cache and reset local certificates. This worked for one player in the Steam Discussions thread, though it's a more involved, command-line-level fix.

    Reported

Did this fix it for you?

Your answer helps the next player know whether these steps are worth trying first.

Hit this error? Leave a comment

Say where you are, what you see on screen, and whether any fix worked for you.

No links. Anonymous, no account. Keep it about the game.

What people are saying

Notes from players who've hit this one — no time limit, an answer from months ago is still an answer.

  • Nothing reported here yet.