What is wrong with 180 on tfl app the board

[mjcarchive]

@Lex
As you are probably aware TfL has been suffering from the cyberattack back in September - see the sticky post at the top of the page and the thread
[UPDATED: 24 Oct]: Issues with Data Feeds - #111 by mjcarchive.

One of the consequences seems to have been difficulty in getting revised bus schedules into TfL systems. As a result, an increasing number of routes are reporting no predictions, or far fewer than they should be.

If you look at this thread

Routes not reporting predictions, or mapping incorrectly on bustimes.org

According to bustimes.org there are currently 7 vehicles out on route N18 in the middle of the afternoon. One of them is actually on 469 and the others on 308. 16 buses are shown currently on N15! Most of the buses actually operating on 56 are shown as 301. I suspect that the problems with the bustimes.org maps are more widespread than I first thought. Of course I have no idea whether the issues are present in what they take (from BODS?) or in what BODS (?) is getting from TfL. It doesn’t appea…

you will find 180 identified as one of these routes.

Hope that is helpful.