RuneScape 3 server status: is it down?
Fantasy MMORPG (Jagex's flagship RuneScape, played on PC and mobile)by JagexSteam app 1343400
No problems reported in the last 15 minutes.
Checked 17:53 UTC · this page is rendered fresh on every load
RuneScape 3 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 3 reports in the last 24 hours
0 players reported a problem in the last 24 hours.
What people report
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.
From isthisgamedownMatched on ""
From isthisgamedownMatched on ""
From isthisgamedownMatched on ""
Players in game
1,983
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 3 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.
Client-side
- ACCESS-BLOCKEDConfirmed
RuneScape 3 "Access Blocked" with a Ray ID: what to check
The website, the mobile app or the Jagex Launcher shows an "Access Blocked" message with a Ray ID and won't let you through.
- HAS-BEEN-UPDATED-RESTARTConfirmed
RuneScape 3: "RuneScape has been updated!" restart error
Logging in shows "RuneScape has been updated! Please restart the game to retry" and the client won't let you sign in.
- COULD-NOT-AUTHENTICATEConfirmed
RuneScape 3 Jagex Launcher: "Could not authenticate"
The Jagex Launcher shows "Could not authenticate" when you open it, so you can't get to RuneScape.
- LOADING-APPLICATION-RESOURCESConfirmed
RuneScape 3 stuck on "loading application resources"
The RuneScape client never gets past "loading application resources", or is stuck on "Loading resources", and never reaches the login screen.
- GRAPHICS-INITIALISATION-ERRORConfirmed
RuneScape 3: client error during graphics initialisation
A pop-up says "The RuneScape client suffered from an error during graphics initialisation" and the desktop client won't load.
- C0000409Confirmed
RuneScape 3 crash: "Error Code c0000409"
The RuneScape client crashes and shows "Error Code c0000409".
- ERROR-GAME-CRASHConfirmed
RuneScape 3: "Error_game_crash" (corrupted cache)
The client crashes with "Error_game_crash", often at startup or while playing.
- GAME-CANNOT-BE-OPENEDConfirmed
RuneScape 3 on Mac: "The game cannot be opened"
On a Mac, opening RuneScape shows "The game cannot be opened" and the client does not start.
- MALFORMED-LOGIN-PACKETConfirmed
RuneScape 3: "Malformed login packet" (fix)
Logging in fails with "Malformed login packet".
- TO-ACCESS-THIS-FREE-WORLDConfirmed
RuneScape 3: "To access this free world, log into a members world"
Logging into a free-to-play world fails with "To access this free world, log into a members world and move your character to a non-members area".
Server-side
- UNEXPECTED-RESPONSE-26Reported
RuneScape 3: "received an unexpected response (26)"
Logging in fails with "RuneScape received an unexpected response (26)", usually through the Steam client, and nothing else happens. Players in the same threads often say the Jagex client or the mobile app still let them in.
- TOO-MANY-LOGIN-ATTEMPTSConfirmed
RuneScape 3: "Too many login attempts from your address"
Login fails with "Too many login attempts from your address", often during a busy period, and gets worse the more you retry.
- ERROR-LOADING-GAME-CONFIGURATIONReported
RuneScape 3: "error loading the game configuration"
The client shows "There was an error loading the game configuration from the website" with a firewall hint and a code in brackets such as (6,200), (7,28) or (7,7), and won't start.
About RuneScape 3's servers
RuneScape 3 is what most people just call RuneScape: Jagex’s long-running fantasy MMORPG, played on PC through the Jagex Launcher, a standalone client or Steam (listed there as “RuneScape”, app 1343400), and on mobile. It is not Old School RuneScape, a separate game with its own client, and it is not RuneScape: Dragonwilds, a survival game set in the same world. Players mix these three up constantly, so check which one you are actually looking at before trusting any status or fix you find.
The blunt part about status: RuneScape 3 has no official live status page. Jagex’s Game Status Information Centre only covers Old School. What exists for RuneScape 3 is announcements: planned downtime on Jagex’s support-site Service update archive, and updates on @RuneScape on X, the RuneScape news feed and the Steam news hub. All of it is posted by hand. That is why this page leads with error pages rather than a live verdict, and why the Steam player count it shows needs a caveat: it only counts players who launched through Steam, a slice of everyone playing. A count that keeps falling toward zero is still our outage signal, but a Steam-only login failure can look the same from here.
The error pages come in two kinds. Most are Jagex’s own documented messages (“Too many login attempts from your address”, “Access Blocked”, “RuneScape has been updated! Please restart the game to retry”, the Mac “The game cannot be opened”), each carrying a link to the Jagex support article it comes from. The other kind is what players report and Jagex has not explained, the clearest being “RuneScape received an unexpected response (26)”, a Steam login failure that has turned up in Steam Discussions threads since 2021 and is labelled as reported, not confirmed, because no Jagex staff reply has turned up in any of them.
Maintenance, queues, and real outages
Three different things get reported as "RuneScape 3 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 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.
- 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.
- 02
Verify the game files
In Steam: right-click RuneScape 3 → 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.
- 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."
- 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.
- 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 3 server status: common questions
Is RuneScape 3 down right now?
As of 17:53 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 there an official RuneScape 3 status page, and where are outages announced?
No. Jagex runs a Game Status Information Centre, but it only works for Old School RuneScape: the address that serves it needs "oldschool=1" on the end, and the same page without it returned a 404 when we checked on September 25, 2026. For RuneScape 3 the channels that exist are all manual announcements rather than a live dashboard: the official @RuneScape account on X (Jagex Support's own X bio points players to @RuneScape for game news; the account posted an "Important Update On Service Issues" notice on November 22, 2022 during an outage), the RuneScape news feed on runescape.com and the Steam news hub for app 1343400, and Jagex's support-site "Service update archive" for planned downtime. Because none of them is a live indicator, a crowdsourced tracker fills a real gap here.
RuneScape 3 maintenance and where it's announced →Does Jagex announce scheduled site-wide outages, and what does it say?
Yes, on its support site's Service update archive, which opens with "From time to time, our services may be brought offline for scheduled maintenance." Entries are dated one-off windows covering both RuneScape and Old School RuneScape. The newest entry on the page when we read it on September 25, 2026 was October 14, 2025, 08:00 to 11:00 UTC, when all game worlds for both games were to be unavailable for approximately 3 hours. Earlier entries include March 31, 2025 (about 4 hours) and February 4, 2025 (about 1.5 hours). Nothing newer is listed, so treat the archive as a record of the larger planned windows, not proof that no maintenance has happened since; check @RuneScape and the Steam news hub as well.
Why does the Steam player count on this page not match how many people are playing RuneScape 3?
The count this site shows comes from Steam and covers only players who launched the game through Steam. RuneScape 3 also runs through the Jagex Launcher, a standalone client and Jagex's mobile apps, and none of those show up in the Steam figure, so it is a slice of the player base rather than the whole; Jagex doesn't publish how large that slice is. A count that falls toward zero is still the outage signal we watch. The caveat is that a Steam-only login failure would also empty the Steam count while Launcher and mobile players carry on, which is what posters in Steam threads describe for the unexpected response (26) error.
RuneScape 3 'unexpected response (26)': Steam login failing →Is RuneScape 3 the same game as Old School RuneScape?
No. Old School RuneScape is a separate game with its own client and its own Steam listing, and it is the one Jagex's Game Status Information Centre covers. RuneScape 3 (the game Steam lists simply as RuneScape, app 1343400) is the current version of the original RuneScape. Jagex's support site covers both, so many articles mention both games, and a Jagex Account character can be played on either (but not on both at once). An outage announced for one is not automatically an outage of the other, though the planned windows in Jagex's Service update archive have so far covered both together.
Is Old School RuneScape down? →Is this RuneScape: Dragonwilds?
No. RuneScape: Dragonwilds is a separate survival game from Jagex set in the RuneScape world, and its 1.0 release went live on September 15, 2026 according to Jagex's own launch post. It has its own servers, its own patches and its own errors. If you are seeing a mismatched build message, a crossplay problem or an Xbox or PlayStation error, that is the Dragonwilds page, not this one.
RuneScape: Dragonwilds status and errors →Do I need a Jagex Account to play RuneScape 3?
It depends on how you launch it. Jagex's Jagex Accounts FAQ says the Jagex Launcher requires a Jagex Account, and that all new players have needed one for the Launcher since November 7, 2023, while the standalone RuneScape client requires an older RuneScape account. It also says upgrading is optional "for now" but that Jagex plans to make Jagex Accounts mandatory in future. Separately, Jagex's Third-Party Login Changes article says Facebook login is unavailable on every client and on the website, and that Apple and Google login no longer work on the desktop client. If you can't log in the way you used to, that article's advice is to download the Jagex Launcher and upgrade to a Jagex Account (desktop) or upgrade from the mobile app.
What does 'Too many login attempts from your address' mean, and how long do I wait?
Jagex's support article calls it a known message commonly associated with periods of high traffic that can stop players logging in. It says simply waiting usually resolves it, that repeated attempts can make it worse, and recommends waiting at least 30 minutes between attempts. Its other suggestions are logging in through the Jagex Launcher or Steam, trying an alternate account or a different network, and using an official client rather than a third-party one.
Too many login attempts: Jagex's full list →What is 'Access Blocked' with a Ray ID, and is my account banned?
Jagex states that your account has not been blocked or locked. The message means its security services decided your connection might be risky. Its article says to turn off any VPN before launching, check your default browser has JavaScript enabled and no ad-blocking extensions interfering, set your device time zone to update automatically, and update your browser, the Jagex Launcher or the mobile app. If it persists, Jagex asks for a report with the Ray ID from the message, though it says it cannot reply to those reports.
Access Blocked: what Jagex says to check →Why does RuneScape say 'received an unexpected response (26)' when I log in through Steam?
Jagex has no support article for this message that we could find. What we have is player reports: at least seven Steam Discussions threads since October 2021 describe it, and in several of them the Steam-launched game fails while the Jagex client or the mobile app still lets the same player in. The newest thread, started September 23, 2026, had 12 replies and a later reply saying it was still down after more than 24 hours. No Jagex reply appeared in any of the threads, so the cause is unconfirmed.
Unexpected response (26): what players report →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.