I will confirm the problem, but I don't know why it is happening.
It was reported to IB admin about 2 years ago, but we are no closer to a resolution.
It may be something to do with the time and date settings on some of the VM front-end web servers. The underlying data in the database is correct, but it is not always being presented correctly, hence the suspicion falling on the web server layer.
The hope is that moving to a new set of servers when the migration to VB4 is done will eradicate the problem (and hence little effort is being expended on curing it in VB3...).
Testing PPRuNe on VB4 is currently underway, although there's no date announced for implementation.
Sd