On two consecutive days I've had to cease using this site because of repeated server errors. Anybody else having this trouble?

Become a supporter
cycle.travel now has Ordnance Survey maps
Plan multi-day adventures easily
Thanks to Swaledale Outdoor Club!
We’re now in Australia and New Zealand too
Stick to tarmac with our new routing option
cycle.travel expands to Scandinavia and Eastern Europe
Smart Turns – new on cycle.travel's route-planner
On two consecutive days I've had to cease using this site because of repeated server errors. Anybody else having this trouble?
Log in with your cycle.travel account:
| Password |
Or simply use your account on:
Comments
Shane, assuming you are correctly referring to the website and not the app, it was probably an update in CT itself. These can affect some functionality of the site (but usually improve it!).
As I understand it, these updates normally take place at night - but I think that might be day-time for you?
If this is happening too often maybe check the internet connection, including any VPN that is in use. Sometimes, an alternative browser can solve functionality issues, too.
Shane – am I right in thinking you are planning routes in Australia?
Usually the route-planning server is pretty reliable but I can see a little cluster of failures on the Australia server in the last two days, which I suspect is what you’ve encountered. There’s probably a one-off piece of bad routing data which you’ve encountered. I’ve turned up the logging on the server to see if I can track it down, but if you can point me to what route you were trying to plan at the time, that might help – thank you!
Hi Guys,
I wasn't using a VPN. Yes, planning from Australia, but I'm in the process of editing many routes atm, so I don't recall which. If it happens again I'll post details here.
Thanks.
Yep, I just got a server error editing https://cycle.travel/map/journey/889581
And they just keep occurring, rendering the site unusable.
Great, thank you for the report. I have worked out what was going wrong (…though not yet why!) and squished it such that it shouldn’t crash any more.
If you switch the route to ‘Any’ then back to ‘Gravel’, then reinstate the ‘Go direct’ points at the southern end of the route, then that seems to heal the route and stop the error from happening in any case.
Thanks Richard.