Thanks.
I note with interest that the calls to the TfL API that we use to gather the tube data are taking ages. The job is taking 52.8s rather than about 3s. This is the only call we do that doesn’t use a timeout (as it’s using multicurl).
I’m so glad I cached the data… Should I see if I can use the .zip file TransX file to fill in the missing tube data? I kind-of-thought this problem would be sorted by now.
When it’s the timetable and so it’s without actual platform numbers, but it’s better than being court short for over a week!
The code change for this turned out to be…
Fingers crossed for live data so I can put this back as it was…
Is there any update on when the feeds in general, and, from a selfish point of view, the jamcams and cycleHire feeds specifically, will be back online? (or will they ever be…)
I know they’ve been down since the 2nd - are we looking at days, weeks, or nevers?
Hi, we expect that the feeds will return, however I cannot provide an indication of when that will be. We will update this thread if there is anything we can share on that.
[Post Updated 24 Sept: ‘Static station crowding’ data is no longer updating - this has been added to the list in main post]
Hi all, I have been using - https://api.tfl.gov.uk/Line/circle/Arrivals/940GZZLUEMB?app_key=*** for sometime, but not recently. I have a demo coming up and it does not seem to work anymore. All I receive is - is there an issue?
I have not only tried on my system but also on Postman and through https://api-portal.tfl.gov.uk/
Thanks in advance,
Hello and welcome to the forum.
Sorry about this, but live Tube arrivals are currently unavailable. We will update this thread if there is any news.
If it helps at all, we do have live arrivals for other modes of transport (e.g. bus, tram, Elizabeth line, London Overground, DLR and River Bus).
I’ve been using this API for many years: https://tfl.gov.uk/tfl/syndication/feeds/cycle-hire/livecyclehireupdates.xml
It looks like it’s not updating. Will it be fixed. Or is there a suggested alternative (to get the number of current bikes at each docking station)?
Thanks,
Aidan.
Hello, welcome to the forum.
Sorry, but that is one of the data feeds that is currently unavailable, and we are unable to provide an alternative.
We are still dealing with an ongoing cyber security incident, but hope to restore the feeds as soon as we can.
If we have any updates, we will provide them in this thread.
Hi!
Is this endpoint also not working? https://api.tfl.gov.uk/Line/8/timetable/490000044E
I get "No timetable available for 490000044E > 1000044, inbound > R, 8 > 60008.
Hi @ndjik - this is not related to the cyber incident response. I’ve created a new thread for this issue: Timetable API Unavailable
Many thanks,
James
Do these feeds really have to still be frozen. It’s been over a month.
Hi @ryan.forsyth - obviously, I can’t discuss the details of the incident response here. Systems are being brought online based on criticality and whether it can be restored securely. This is not yet the case for the systems mentioned on this post, but the teams are working hard to get these systems back.
Many thanks,
James
One of the key words in the cyberattack description is “ongoing”, assuming that this is still accurate. I don’t expect to get any details of the cyberattack (and if I did I wouldn’t understand it anyway) but “ongoing” suggests to me that bad actors are still trying and might succeed if risks were taken by bringing back services prematurely. While I share the frustration of @ryan.forsyth we users just have to trust the professionals here. We also have to accept that open data are not going to be at the top of the queue if services are being brought back cautiously, one-by-one.
What is not clear to me is whether the files (or whatever) which are usually available as open data are still being created internally. The thread on the 295 (and W9) suggests that it may be a bit patchy.
hi @mjcarchive - I understand the frustration, but we can’t share details on the recovery from this attack.
Customer-facing data, including open data is important to us but as you can imagine this has to be weighed up against the current risk.
In terms of bus predictions, we’re aware of the following routes with low or zero prediction levels due to service changes not yet reflected in iBus data:
4, 160, 295, 380, 114, W9, 660, 210, 284
We will continue to update this thread as and when we have updates.
Many thanks,
Thanks, @jamesevans. I appreciate all that you say about what you cannot say! I imagine that you guys, who have put the hard yards in to get where we are (or were) on open data feel it just as much as we users.
The list of “low prediction” routes will be useful. It is bizarre that only some changes are impacted; several operators are involved so no common thread there but I have a feeling they are not the most recent changes.
Unfortunately I don’t have the full details on why these routes only. I know that some changes seem to be impacting more than others.
I mused on a possible reason here. No idea if it makes sense.
