Is This Game Down
Browse games
Live

RuneScape: Dragonwilds server status: is it down?

Survival craftingby JagexSteam app 1374490

Operational

No problems reported in the last 15 minutes.

Checked 05:50 UTC · this page is rendered fresh on every load

RuneScape: Dragonwilds servers, regions & maintenance →

Report a problem

Select the issue you're having — one tap, no account or email needed.

Your report is anonymous. We store the category and the time. We do not store your IP address — it is hashed with a secret and today's date purely to stop one person filing fifty reports, and the hash cannot be reversed or matched to you tomorrow.

RuneScape: Dragonwilds reports in the last 24 hours

24 hours ago12 hours agonow

0 players reported a problem in the last 24 hours.

Having trouble? Leave a comment

Say where you are and what you see on screen.

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

What people are saying

Notes from players in the last 24 hours.

  • Nothing reported here in the last 24 hours.

Players in game

4,858

Concurrent players on Steam right now. A real outage pulls this number down within minutes, so a normal count alongside a flat report count usually means the problem is on your end.

Source: Steam GetNumberOfCurrentPlayers, cached 60s.

RuneScape: Dragonwilds error codes and crashes

Search your error code below, or browse what we've logged so far — each one links to a full page with the exact symptom, whether it's on you or the studio, and the fix steps other players say worked.

Updated November 2, 2026 · 14 error pages logged

Newest

Client-side

Server-side

All RuneScape: Dragonwilds error codes →

About RuneScape: Dragonwilds' servers

Co-op open-world survival game set on Ashenfall, a dragon-infested continent in Gielinor, from Jagex — the studio behind RuneScape, though this is a separate title built on Unreal Engine 5 rather than RuneScape’s own engine (Steam app id 1374490). It shadow-dropped into Steam Early Access on April 15, 2025, and left Early Access for a full 1.0 release on September 15, 2026, launching simultaneously on PC, PlayStation 5, Xbox Series X|S and Nintendo Switch 2 with crossplay across all four. Its multiplayer runs on player-hosted worlds and rented or self-hosted dedicated servers rather than centralized Jagex-run servers, which is the biggest source of confusion for anyone trying to work out whether “the game is down” or just one session is.

How Dragonwilds’ servers actually work

There’s no regional server list to pick from, because there’s no central server pool. Per Jagex’s own “Dedicated Servers - An Update” post, multiplayer runs one of two ways: a non-dedicated world, hosted directly from a player’s own running game client with up to three friends joining (four total), found via Steam friends or an invite code; or a dedicated server, capped at six players, run by someone on their own PC or cloud instance using Steam Server Binaries, or rented from a third-party host — Jagex specifically worked with Shockbyte as a hosting partner once dedicated servers shipped. Joining either means searching the exact, case-sensitive world name in the Worlds screen’s Public tab, not picking a region.

That structure is also why Jagex doesn’t announce a maintenance window the way a traditional MMO does — there’s no shared server to take down. Client and dedicated-server updates are posted on dragonwilds.runescape.com/news and in the official Discord instead, and every hotfix requires dedicated servers to be individually restarted to sync to the new build; Jagex’s patch notes routinely repeat that instruction. Crossplay across PC, PlayStation 5, Xbox Series X|S and Nintendo Switch 2 is confirmed day one per Jagex’s own console FAQ, but each platform’s storefront has to separately approve a patch before its players can join a session on the new build — a rollout gap, not a bug, that’s the likely explanation behind cross-platform “mismatched build” reports (see the FAQ above).

Maintenance, queues, and real outages

Three different things get reported as "RuneScape: Dragonwilds is down," and only one of them is an outage. The chart above is the fastest way to tell them apart, once there's data on it:

A real outage

Reports spike hard within an hour, then decay as the problem is fixed. Nobody announced it in advance.

Scheduled maintenance

Reports climb steadily and stay flat for the length of the window, because everyone hits the same wall at the same time and keeps hitting it.

A login queue

Matchmaking/login reports climb while server-connection reports stay low, and a Steam player count (if shown above) holds flat instead of dropping. The servers are up and full, not down — waiting is the only fix.

Announced maintenance would show up at the studio's own status channel or the official Discord before it shows up here.

If it's only broken for you

Most "is it down" moments aren't outages. Work down this list before assuming the servers are the problem — it's ordered by how often each one turns out to be the answer, not by how easy it is.

  1. 01

    Check the report count above first

    It costs nothing and it settles the question. A flat report count means other players are getting in fine, and everything below is worth your time. A spike means it isn't you, and none of it is.

  2. 02

    Verify the game files

    In Steam: right-click RuneScape: Dragonwilds → Properties → Installed Files → Verify integrity of game files. A partial patch is the single most common cause of a game that launches and then fails to connect.

  3. 03

    Restart the whole chain, in order

    Game, then your launcher/Steam, then your router. People almost always do the first and skip the third — a stale router NAT table produces exactly the symptom people report as "servers down."

  4. 04

    Rule out a VPN or restrictive network

    A VPN fails matchmaking far more often than it fixes it, and so does a corporate or campus network that blocks the UDP ports a game server needs. If you're on a network you don't administer, that's the likely answer.

  5. 05

    If it crashes rather than fails to connect, treat it as a crash

    A game that starts and then dies, rather than never connecting, is usually a local fault — most often graphics drivers or overlay software, not the servers.

RuneScape: Dragonwilds server status: common questions

Is RuneScape: Dragonwilds down right now?

As of 05:50 UTC, 0 players have reported a problem in the last 15 minutes — counted as people, so repeat taps from one person don't inflate it. This page updates on every load.

Is Dragonwilds down for everyone, or just me?

Compare the two signals on this page, but read them with one Dragonwilds-specific caveat in mind: there is no single set of central Jagex game servers for this title the way there is for a typical MMO. If reports here are flat and the Steam concurrent player count looks normal, thousands of people are getting into the game fine, and whatever you're hitting is local to you, your friend's world, or a specific rented dedicated server — none of which anyone else would notice or report. Reports spiking alongside a real drop in the player count is the pattern that actually points to something broken on Jagex's side (the client patch service, matchmaking/session listing through Epic Online Services, or the storefronts themselves) rather than one player's setup.

What's actually confirmed about the Early Access-to-1.0 timeline?

RuneScape: Dragonwilds shadow-dropped into Steam Early Access on Windows on April 15, 2025 — Jagex's own announcement is dated and opens "Tuesday 15 April, 2025, Cambridge, UK," and Wikipedia's infobox corroborates the date. It left Early Access with a full 1.0 release on September 15, 2026, confirmed in Jagex's own "RuneScape: Dragonwilds Leaves Early Access" announcement and its 1.0 launch post, shipping simultaneously on PC (Steam, the Epic Games Store and the Jagex Launcher), PlayStation 5, Xbox Series X|S and Nintendo Switch 2, with crossplay across all four from day one. Jagex's own posts state the game passed one million sales during Early Access, and that 1.0 shipped with the new "Scorned Wilderness" content (a new endgame region, the Kuldra raid, and Rune/Dragon tier gear) plus everything from the earlier "Umbral Sands" expansion, alongside more than 2,665 bug fixes.

Jagex's own 1.0 launch post →

Does Jagex run official servers for Dragonwilds, or is it all player-hosted?

This is the single biggest point of confusion around this game, and it's worth being precise about. Jagex does not operate central, always-on multiplayer servers for Dragonwilds the way it does for RuneScape itself. Per Jagex's own "Dedicated Servers - An Update" post and the game's wiki, multiplayer runs one of two ways: a non-dedicated world, where one player hosts from their own running game client and up to three friends join it (capped at 4 total, found via the Steam friends list or an invite code); or a dedicated server, capped at 6 players, which someone runs themselves on their own PC or cloud instance using Steam Server Binaries, or rents from a third-party hosting company that Jagex's post describes as "preferred hosting partners." So when you report a problem here, it should be about Jagex's side of things — the client, patch delivery, storefronts, or the session-listing/matchmaking layer everyone depends on — not about a specific friend's world or a specific rented dedicated server being unreachable, which is a private problem between you and that host, not a site-wide outage.

Why doesn't my dedicated server show up in the server browser?

This is the most-repeated Dragonwilds symptom found in this research — enough that multiple game-hosting companies independently publish near-identical troubleshooting pages for it, and Jagex's own official how-to guide and Known Issues page document real, specific causes rather than leaving it unexplained. The short version: check that your server and client are on the same game version, check that your Steam privacy setting isn't set to Private, and make sure you're searching the exact, case-sensitive world name rather than a Steam invite. The full breakdown of causes and the order to check them in is on this site's dedicated page for the issue.

Every confirmed cause, sourced to Jagex's own guide →

Can I invite a friend straight into my dedicated server through Steam?

Not reliably, and this isn't a bug you introduced — Jagex's own Known Issues page for the game states plainly that "Inviting a player to your Dedicated Server via Steam Invites doesn't currently connect as intended." If a Steam invite to your dedicated server isn't working, that's the documented limitation, not something broken on your end. Have the other player open the Worlds screen, go to the Public tab, and search for your server by its exact name instead — that path works even though the invite shortcut doesn't.

Does crossplay carry my save and progress between platforms?

No — crossplay and cross-save are two different things here. Crossplay lets PC, PlayStation 5, Xbox Series X|S and Switch 2 players join the same session when the host turns it on for that world, and Jagex's own console FAQ confirms this works day one. But progress doesn't follow you across platforms: your PS5 character and your Steam character are separate save files with separate progression, even if you use one to crossplay into a session hosted on the other. If you're trying to pick up your PC progress on a console (or vice versa), that isn't currently possible — you're starting fresh on whichever platform you didn't originally play on.

Did the 1.0 launch cause any real console save problems?

Yes, and this is the most serious documented issue from launch week. Shortly after 1.0 shipped on September 15, 2026, console players began reporting corrupted world saves, in some cases losing progress entirely — covered in a review roundup by GameDaily and reported separately by Pure Xbox, which quoted Jagex acknowledging the problem directly: "the entire QA and development team are working flat-out to resolve" it. Jagex's later "Save Corruptions" update said around a thousand players across consoles and PC Game Pass had saves made unreadable after disconnecting or putting a console to sleep, that "the main culprit of this was editing your character's appearance", and that the feature was disabled. Patch 1.0.1 (October 14, 2026) shipped fixes targeting disappearing world saves and a catch-up mechanic for corrupted characters, and Jagex says the occasional player may still be affected.

Do PC Early Access saves carry over into the 1.0 release?

This looks true but isn't backed by a direct Jagex statement, so it's worth being honest about the gap. Jagex's own framing across its "leaves Early Access" and launch posts treats 1.0 as a continuation of the existing PC game rather than a fresh release that wipes progress, and third-party coverage (theclick.gg) states outright that Steam characters and worlds "remain relevant after September 15" without needing a restart. But no Jagex post found in this research directly and explicitly confirms automatic PC save carry-over in those words. Treat it as very likely true and unconfirmed in the strict sense — the opposite is true for consoles, where a real, officially acknowledged save-corruption problem is confirmed above.

Does Jagex publish an official status page for Dragonwilds?

No. Jagex's "Game Status Information Centre" at secure.runescape.com is real and actively maintained, but it says outright that it covers "Old School RuneScape" — Dragonwilds isn't mentioned on it at all, and the two games don't share infrastructure. The closest official channel for Dragonwilds itself is its own news blog at dragonwilds.runescape.com/news, where launch posts and update notes are published, plus a Known Issues page — though as of this writing, six days after the 1.0 launch, that Known Issues page still reflects the older 0.7.1 Early Access build rather than 1.0, so don't treat it as current for launch-week problems like the console save corruption above.

Jagex's Known Issues page (last updated for 0.7.1) →

Is there a login queue for Dragonwilds?

No queue system has been announced, and the game's architecture makes one unlikely in the MMO sense you might expect from RuneScape itself. Because there's no central server pool with a fixed capacity — worlds are either a friend's own game session or an individually run dedicated server, each capped at 4 or 6 players — there's no single "server full" gate for Jagex to queue players behind. A specific world or dedicated server being full is a capacity limit on that one world, not a sitewide queue, and nothing in Jagex's posts describes one existing.

Is the Dragonwilds Discord real, and is it actually official?

Yes — discord.gg/rsdragonwilds is cross-referenced on the game's own wiki (which links it as the official server) and recommended directly in Steam Discussions threads by other players pointing newcomers to it for bug reports and dev polls. It's a large, active community (well over 80,000 members as of this research), not an unofficial fan server standing in for a missing one.

Is RuneScape: Dragonwilds the same game as RuneScape or Old School RuneScape?

No — it's a separate game that happens to share Jagex as the studio and Gielinor as its setting. RuneScape and Old School RuneScape are long-running MMOs with their own servers, their own status page (the Game Status Information Centre, which is OSRS-specific), and their own decades of history; Dragonwilds is a 2025-launched, Unreal Engine 5, 1-4 player co-op survival-crafting game set on Ashenfall, a continent within the same universe. An outage or maintenance window on RuneScape or OSRS says nothing about Dragonwilds, and vice versa — if you're trying to check on the mainline game, this isn't the right tracker.

The game keeps crashing right when I launch it — what's causing that?

The best-documented version is a DirectX 12 rendering failure in the Unreal Engine 5 client, quoted verbatim in a Steam Discussions thread as a "CopyCommandList->Close()" fatal error — not a corrupted save or account problem. Switching the launch options to force Vulkan or DirectX 11 has fixed it for multiple players. A separate variant, where the Play button just resets with no error text, traces to Epic Online Services failing to initialize rather than the renderer.

The exact crash text and the renderer/EOS fixes that worked →

I'm getting "an unknown network error" trying to join a game — is that Jagex's fault?

Often yes, but not always the same cause twice. The best-documented case is a confirmed, platform-wide Epic Online Services outage on December 24–25, 2025 that broke joining across Dragonwilds and several unrelated games at once — nothing to fix locally, since it cleared once Epic resolved it. A separate, rarer version traces to a corrupted local EOS certificate cache instead, with its own fix.

The EOS outage timeline and the local-cache fix →

Why can't I load my character after an update?

One specific, well-documented case: a cluster of matching reports on June 26, 2026 traced an "Error: failed to load player state" message to owning a fire cape right after that week's patch — new characters loaded fine, existing ones with the item didn't. No Jagex fix has surfaced for it yet.

What the pattern is, and what to try →

I can see a server in the list but get a "mismatched build" error joining it — what's that?

A different problem from a dedicated server that never shows up at all (covered above) — this is an explicit error on a world you can already see, most often in cross-platform groups where one platform's patch hasn't fully rolled out yet even though every player believes they're current.

The documented case and the likely crossplay-lag cause →

Why did crossplay stop working after an update?

Jagex has confirmed this one is on its side of the process rather than your setup. Every hotfix has to be approved separately on each console platform, and crossplay only works when everyone is on the same build. Jagex's 1.0.0.4 notes say that patching meant "Nintendo Switch 2 and Jagex Launcher systems will no longer be able to crossplay until the patch has been processed on their respective platforms," and it announced the 1.0.0.5 patch on September 25, 2026 with the Switch 2 build following the other platforms by roughly 45-60 minutes. If your crossplay tick-box still won't enable after everyone has updated, some Steam Discussions posters fixed it by correcting their Windows clock or time zone — a player report, not something Jagex has documented.

What Jagex confirmed and what players reported →

Why can't I play Dragonwilds online on Xbox?

Jagex's Known Issues post of September 16, 2026 says Xbox players "have to set the 'You can see and upload community creations' privacy setting to 'Everyone' to access online play." Patch 1.0.0.5 adds a notification when a conflicting privacy setting is what's stopping you going online, and separately fixes Xbox players being unable to join a world that already has two players in it.

The privacy setting to change, sourced to Jagex →

What did patch 1.0.1 change, and do dedicated servers need updating?

Patch 1.0.1 went live on October 14, 2026. Jagex's announcement calls the save work its headline: "a range of fixes targeting the disappearing world saves we've seen reported, as well as a catch-up mechanic for corrupted character saves that will let you drop in with aggregated stats and Tier 4 gear". It also says "there may still be the occasional player affected by other, extraneous instances of save issues". For dedicated servers, the game and the server must be on the same build. The 1.0.1 notes give no restart instruction, but Jagex's 1.0.0.8 notes said "Dedicated Servers will need to be restarted to apply the hotfix", so update and restart your server after a patch.

What Jagex says 1.0.1 does for missing and corrupted saves →

Why does my dedicated server keep crashing or freezing since 1.0.1?

Several Steam Discussions posters report dedicated servers freezing or crashing (one log ends in "EXCEPTION_ACCESS_VIOLATION reading address 0x0000000000000030") after the 1.0.1 update on October 14, 2026. It looks like a game or server-build bug rather than a hosting fault, and Jagex had not replied in those threads as of October 15, 2026. There is no confirmed fix. Players blame the new Shortbow special or the Vengeance spell, which is unconfirmed. Keep backups of your server's Savegames folder.

The log line, player workarounds and what to back up →

Why does Dragonwilds say my character name is already taken when I join a server?

Two Steam Discussions threads report it, one on a friend's dedicated server and one on PlayStation 5-hosted worlds, where the message reads "A character with this name already exists." One player suggests the host switch the dedicated server off and on to clear a stale connection; that is unconfirmed, and there is no confirmed fix. Jagex's 1.0.1 notes fix an emoji-in-name join problem on console-hosted worlds, which may or may not be related.

What players tried and what is still unconfirmed →

Incident history

Auto-logged from player reports over the last 30 days. An incident is a run of hours with at least six different players reporting in each, the same signal the verdict above responds to — so one frustrated player pressing a button repeatedly can never put an incident on this list.

No incidents logged in the last 30 days.

Other games we track

Is DayZ down?

Hardcore open-world survival sandbox

Is Dune: Awakening down?

Survival MMO

Is Enshrouded down?

Survival action RPG

Is Once Human down?

Survival MMO

While you're waiting

RuneScape: Dragonwilds error codes

Every code we have a fix for, split by whether it's something you can fix.

RuneScape: Dragonwilds servers

Regions, maintenance schedule and cross-play, all in one place.

Official Discord

Where RuneScape: Dragonwilds's own community and, sometimes, the studio itself post first.