Arrivals endpoint giving timestamps in the past

Hello,

I am using the /StopPoint/{NaptanID}/Arrivals endpoint to get the upcoming arrivals at a particular stop.

In the case of the DLR I have noticed recently that it is giving results that are in the past. Is this a known bug? (perhaps a recent regression though as I haven’t seen this until very recently)

Example https://api.tfl.gov.uk/StopPoint/940GZZDLLIM/Arrivals returned dlr_arrival.json · GitHub (this was requested at around 13:25 2nd October 2022, but all the timestamps are in the past: 30th September 2022).

This also seems to happen only sometimes. Most of the time I get correct timestamps, example here: dlr_arrival_correct.json · GitHub

Hi @dom96

Welcome.

It appears we have some caching issues on some endpoints. We’re investigating this now.

Thanks,
James

2 Likes