Just noticed that this is still happening (and it's happening right now since we are at the end of month again...).
Looking at the code, it seems that the issue comes directly from the server side. The server returns a
ux: null in the
trend array after
metar which is why all the wrong time have exactly the same value,
howOld treated it as
0... The returned time is in fact the time since Unix epoch....