I once used Gogo to check my flight mid-air to see which gate we were arriving into and which gate my connection was using. dl.com gave me the IROP warning that the flight I was currently enroute on was CX'd. This thread came to mind http://www.flyertalk.com/forum/delta...ht-midair.html.

It was trying to rebook me the next day. We arrived into ATL on time and I connected on time. No idea what made DL's own system think the flight was CX'd because clearly it wasn't. Was expecting grief boarding connection or to find my seat given away but everything was normal.

I have found using some iPhone apps that pull data from the FAA that sometimes I will get a notification that a flight will take off late, arrive late or some combination but all too often we seem to operate on or very close to the original schedule. What ever is triggering the FAA data to appear off must also trigger DL's own IROP trigger on occasion.

I have also noticed that half the time the FAA based app will know of gate changes when the DL app or the DL website do not, and half the time the DL app alerts me to a gate change but the app using FAA data never does, or does so much later.

Lately I have been very careful not to hang out in the club longer than normal when an app or even dl.com says my next flight is running late - I do not trust them that much.

Clearly the various systems that DL uses are not communicating with each other that well.