[Resolved] Journey Planner issues

UPDATE 07/03/2025 | The relevant fixes have been applied (except for the 8 hour limit, which is in place due to infrastructure limitations). The arrive by option isn't always returning the most optimal results, particularly involving services going through the Thameslink "core" section between St Pancras and London Blackfriars, but it is working - if the returned results are too early, you can tap the "Later" button on the results page. This will eventually be addressed as part of a larger project.

Thank you for your patience during this time.

In recent weeks it has become apparent that the RailChecker journey planner is becoming less and less stable with erratic results or nothing being shown. The investigations into this are ongoing, however the current view is that it will not be a quick fix. RailChecker uses a custom journey planning engine, hence why only RailChecker is affected by this.

Most users should not be affected. If you are using the journey planner, please note:

• The "arrive by" option does not work.
• Journeys exceeding 8 hours will not show results.

If you experience any issues outside of the parameters described above, it would be greatly appreciated if you could please fill out this contact form or send an email to contact [at] topolowski [dot] com with the entered origin/destination as well as the time of the query if possible.

I apologise for any inconvenience caused by this ongoing issue.