Submitted by alleyes007 t3_126joq2 in boston
Until recently, the Transit app has been pretty reliable for figuring out when the buses are due on my commute. The last couple weeks or so though, not so much. I’ve seen it changing the ETA seemingly at random (13 minutes away, now 16 minutes away, now 5) and have more than once run into ‘ghost buses,’ where it says the bus has come and gone and I’ve been standing at the stop the whole time.
Anyone know what’s going on? Is it even an app issue, or is it an MBTA problem? Usually the buses have been the reliable part of my commute compared to the trains.
ImpressiveEffect8212 t1_je9j4gf wrote
Transit uses the MBTA API to retrieve data about the schedule and about where buses are currently. They provide this guide to determining whether the data you see is based on a schedule or realtime data https://help.transitapp.com/article/445-how-to-track-departures-on-your-transit-line. If the realtime data you see is off/flaky, it’s the MBTAs fault because the data is taken from the MBTA API. If the ghost buses are based on schedule time data and not realtime data, that means the bus is either delayed relative to the schedule or that run was cancelled by the MBTA (and not reported as such on the API). I recommend only looking at realtime data for the buses unless you’re near the beginning and end of the route since realtime data is typically much more accurate (but often realtime data only starts reporting once the bus leaves its origin stop)