Originally Posted by Globaliser

I've seen a few spurious schedule change notifications too. On these occasions, the new "schedule" has been obviously implausible. When I've reset the alert, a further notification then comes back on the next reporting cycle showing the schedule going back to the original times.

I know that EF faithfully reports that which the GDS says, but is there perhaps a problem with the underlying data source that EF is using?

Here's one example of this, notified last week. NB: The 2310 departure and 0450 arrival were always the correct times. The "1620" arrival was clearly implausible and wrong, so this notification was immediately identifiable as spurious. But not all such notifications would be.

The first notification said this:-The second notification said this:-And here is another example that dropped into my inbox this morning. Spot the implausibility:-