BOINC stats for any project only shows the same 186 users. I'm guessing that any user not in that list is getting the "User ID doesn't exist in or doesn't have any credit." mesage.
I think this qualifies as a bug.

Even the forums show a positive point count. Makes me think it's a web issue rather than a database issue.

Hi,

the members of the teams are mixed up, klicking in team members schows different team and many more...

No need to panic.
Boincstats is encountering issues due to some database mayhem.
There has been work on it, but it overlapped with the daily statistics update.
Nothing can be done about the stats immediately.
If the fixes done work out nicely everything should be fine tomorrow around this time of day.
If not, there will be additional maintainance.

Hi Jens,

thx for the info.
Hope to see you in august in Dresden again.
Bye Jörg

Is it still messed up? Because it should be fine now.

Beside some weird negative numbers in the top BOINC Combined row, it seems to be fine again...

I still have -200,585,407 and 630 world positions up at this time, that indicates, that other users also have problems wit credits.

https://www.boincstats.com/stats/-1/user/detail/13056/lastDays

Looks like ALL points of RETIRED projects is gone.

I'll have it sorted out first thing tomorrow morning..

I am still down 653Billion .

It's also not yet tomorrow morning here.

Repairs complete, stats are back to normal.

So what happened?

The MySQL version that BOINCstats runs on (5.7) has been declared end-of-life by Google Cloud, with the recommendation to upgrade to a new version. If not, some extra costs could be charged. I wasn't particularly keen on the upgrade since I'm almost end-of-life myself. So I didn't do it, but those extra costs turned out to be over €200 per month, which is a bit too much for me. That's why I spent this weekend trying to upgrade to the new version. This failed repeatedly (reasons complicated), so I ultimately decided not to upgrade but to migrate to the new MySQL 8.0. This worked, and through a brainwave, I decided not to switch everything over at once, but to also run the updates on the old 5.7 server. And that was lucky because MySQL 8 is stricter than MySQL 5.7, and inserting the retired projects failed on 8.0. However, because I also did the update on 5.7, I was able to transfer everything from 5.7 to 8.0. As a result, all the data is 100% correct again.
The update has since been adjusted and should now work fine on 8.0, but to be safe, I'm letting 5.7 run alongside it for a bit longer. Unfortunately, that costs something, but it's necessary for now.

Thank You!