First it doesn't look like the host stats has updated since 08-04.
https://www.boincstats.com/page/projectUpdateInfo
Second is that there are no stats listed for any date. All dates are listed as NaN.
https://www.boincstats.com/stats/158/user/detail/212647/lastDays

The stats data files from the Universe project are OK and other stats sites show current data.
Something must be broken here at BOINCstats.

Thanks for chiming in. Something is messed up for sure. Never seen the NaN value here before.
And I looked at FreeDC and even there it doesn't look correct. Everybody's credits have fallen off the cliff since 7-31.
I posted a PM to Krystof and asked whether the host scraping script was working correctly but haven't heard back yet.

My script indicated that two days ago the host file export was corrupt and it was therefor not imported. The last export was OK and was processed.

I'm still not seeing any good data for the 60 days page. Still NaN values. I have cleared cookies and cleared the browser cache also.

Willy, the hosts 60 day stats page is still messed up for Universe@home.

https://www.boincstats.com/stats/158/user/detail/212647/lastDays

The hosts stats file from them must still be corrupted.

All dates values are still listed as NaN.

I asked a team mate to look at their Universe 60 day totals web page and it displays correctly.

So the problem is with my account only it seems. So can you look at my account and determine why I still have NaN values for my 60 day totals page for Universe project?

Nothing wrong with your data. I tried to optimise the display code of that particular page and choose Universe to test it with. It obviously didn't work correctly so I reverted the changes.

Do I understand that you tried to optimize the display code of just my account page?

When I asked a teammate to check their Universe 60 day stats, they showed me a correct looking page.

I just looked at my Universe 60 day stats page and your reversion of the display code has returned my 60 day stats page to normalcy.

Thanks for fixing this. It sure caused a lot of confusion for me and others.

Not just yours. You were however affected since the attempt used a separate database and you were not in it.