All sorted now. It was a bad connection to the feed - the team of tech industry professionals Network Rail contract to effectively manage the open data feed did some improvements last week, which may be a good thing longer term, but could conceivably not agree with my code. Certainly whatever happened we were still connected but only getting a single update every 30 seconds or so, which is just enough to prevent the alerting system from telling us there's a problem, but completely useless for making the site work.
Hopefully I should get the chance to have a look at it this weekend and see if there's anything I can do to make it identify issues and reconnect more reliably.
Probably worth adding that there was another significant outage this week when Digital Ocean, who provide the Traksy servers, fell apart completely for a number of hours. This kind of issue is much rarer, and in fact I think that may be the first time they've had issues for more than about 10 minutes in the entire time the site has been running.
Hopefully I should get the chance to have a look at it this weekend and see if there's anything I can do to make it identify issues and reconnect more reliably.
Probably worth adding that there was another significant outage this week when Digital Ocean, who provide the Traksy servers, fell apart completely for a number of hours. This kind of issue is much rarer, and in fact I think that may be the first time they've had issues for more than about 10 minutes in the entire time the site has been running.
Last edited: