Service delay figures don't match up when the delay crosses midnight

[peter-mount]

Although the archive db is still under development it has shown an issue where the delay figures from the D3 service are plain wrong when the delay crosses midnight.

From these services from London bridge we have:

• Caterham service due to depart at 23:48, marked as delayed but 23:36 early.
• Terminate at LBG due 23:53 expected 00:16 but 23:37 but still 23:37 early
• Selhurst due to depart at 23:54, departed 00:07 but 23:47 early.
• Streatham Hill depart 23:58 expected 00:11 but 23:47 Early.

This is clearly the D3 service not handling delays crossing midnight as the last one should have been 13 minutes late not 23 hours 47 minutes early!

RID's for reference:

• Caterham 201905167116138
• Terminate at london bridge 201905167118679
• Selhurst 201905167113446
• Streatham Hill 201905167114466

[peter-mount]

This also affects departureboards.mobi so it's definitely in the d3 microservice