Status
Site status
Everything this page can check is working.
Checked less than a minute ago, at 15:24 UTC on 12 October 2026.
Player lookups from Jagex
WorkingOn its last run, 24 minutes ago, the tracking job got a usable answer from Jagex for 18 of the 18 players it asked about.
Every profile is read from Jagex's RuneMetrics service. The Codex does not test Jagex for this page: it goes by how the tracking job's own reads went on its last run.
Tracking (XP history and milestones)
WorkingThe tracking job last ran 24 minutes ago. It runs every 30 minutes.
A background job re-reads a batch of tracked players on each run. It adds to each player's XP history and puts dates on their milestones.
Alerts to Discord and phones
WorkingThe alerts job last ran 4 minutes ago, and Jagex answered for 13 of the 13 players it checks.
A background job checks the players who have alerts set up and sends what is new. This page can see that the job ran. It cannot see whether Discord or a phone delivered the message.
Daily clan readings
WorkingThe newest run of the daily clan reading, about 5 hours ago, stored 20 of the 20 clan lists it asked Jagex for.
Every day the Codex reads the member lists of the clans at the top of Jagex's clan XP ranking, in several short runs, which adds to the XP history of their members. This row is about that daily job only: a clan page reads Jagex itself when it is opened, and this page has no record of how that went.
If you can read this page, the website itself is up.
How this page knows
- Each background job leaves a short note when it runs: when it was, and how much of its work got done.
- This page reads the newest of those notes about once a minute, however many people are looking, and turns them into the lines above.
- It never asks Jagex anything to find out. Jagex only lets a small burst of requests through at a time, and the tracking job needs them.
- When a note is missing or too old to go on, the line says "Cannot tell right now". It does not say "Working" on a guess.
Recent problems
Written by hand, newest first: problems visitors could see, with the day each was fixed.
Fixed 11 October 2026
Jagex was refusing many of the tracking job's reads
Two of the Codex's background jobs asked Jagex at the same second every half hour, and when they collided Jagex refused most of what the tracking job asked for: of the 72 most recent tracking runs on record on 10 October, 22 went that way. Players were re-read less often than they should have been. The two jobs no longer run at the same moment.
Fixed 11 October 2026
A new 99 or 120 could go without a date or an alert
If the Codex had not checked a player for two days or more, a 99 or 120 reached in that gap could be missed: no date on the site and no alert. The tracking job now compares each new reading with an earlier one even when that one is days or weeks old, so a gap like that no longer hides a milestone.
7 to 10 October 2026
Nobody could sign in with Discord
For three and a half days every attempt to sign in ended on a bare "Server error" page, because Discord had changed a small detail in how it hands people back to the site. Signing in works again, and a sign-in that fails now lands on a Codex page that says so and offers another try.
Seeing a problem this page does not show?Send feedbackAsk in the Discord
The Codex is an unofficial fan project. It is not affiliated with, endorsed by, or sponsored by Jagex Ltd.