Well, this is embarrassing. The matches were calculated correctly, but due to an unknown database issue, some of the data was not saved. I have no words.
In order to shed some light on the whole issue, I'll try to give you a short timeline of how this came to be. First, I completely missed the fact that most yesterdays matches have not started on time, so that's on me. I was informed of the issue at 4AM (CET). At 6AM, I fixed the issue that cause the delay and the matches finally ran. Again, at that point I was completely unaware of the issue with the boxscores.
If I had been aware of the missing data, I could have rerun the matches. This means that some matches might have been calculated differently, so that option is not exactly a preferred one. The alternative is this: we leave the matches as is and just force the boxscore page to show the data it does have. This is what I ended up doing anyway.
Of course, this couldn't have happened at the worse time, as never do the consecutive matches run so close together as this.
Our database, hardware and software both, are, lately showing so many signs of wear and tear that we might be pushed to stop work on everything else and try and migrate BB to a new server. This means a lot of downtime. Were talking days. Hopefully, this is not what we're gonna have to do, but we might as well. Usually, such downtime should be announced months in advance but this might push our hand. I'll let you know once I confer with my colleagues.
As usual, sorry for the inconvenience. I'll see what I can do to calculate some of the missing data for the affected matches but I know for a fact that for most of it, it will not be possible.