[WEBSITE UPDATE] February 11, 2026 Update Notes

hirei

We’ve rolled out several improvements to the J-Novel Club website this month — including the new “Last Read” series sorting feature to help you pick up right where you left off! We’ve also fixed a few pesky bugs. 🪲

j-novel.club

Sort series by Last Read
Improve network utilization

Fixed Bugs

Change the manga domain to avoid being blocked by routers
Fix random logouts due to network error

More Info

Last Read Series Sorting
We have added a new sorting option to the series page. The "Last Read" option sorts series by the latest date you read a part of a volume in that series.

Initially, what series will be sorted will be any you have read since last week. The sorting option uses a backend update deployed last week that adds to how progress is saved.

We will be using the backend update to add more UI features to help you continue reading from where you left off and to provide other kinds of recommendations. This sorting option is the first part of that.

Improved Network Utilization
We have made several changes to improve the site's network utilization. This should make page loading faster and, in other cases, reduce bandwidth usage.

Bug Fixes
If you find any bugs, please send them by email to support@j-novel.club. You can also let us know in #report-issues on our discord.

Blocked Manga Domain
Following reports from users, we have changed the domain from which manga is served from flame.jnc-cps.nexus to flame.j-novel.club. In January, some users' routers had begun to block traffic to flame.jnc-cps.nexus. All manga has been served from flame.jnc-cps.nexus for about a year. flame.jnc-cps.nexus is a domain controlled by J-Novel Club, but we have gone ahead and made this change since we view serving from flame.j-novel.club to be more reliable for scenarios like this.

Random Logouts
With help from users on our Discord, we tracked down a bug that was unexpectedly logging out users. An unstable internet connection may cause requests to fail. Those network errors triggered a part of the code that handles server errors and logs users out on the client side. We have fixed it so that an unstable internet connection no longer logs users out.