Asteroids is still broken.
Noticed that I had a 1/2 dozen of download failures and a few uploads that keep timing out

Tried to go to project forums and got the same message as a few days ago. Then tried several times refreshing with same results.

Forbidden
You don't have permission to access this resource.

Got a reply to my post on Android project forum (once I was able to get a good connection)...Message 9525

The issue has existed since the last server update last year, more or less often, but since yesterday, the server has become practically inaccessible. I told Radim about the issue again, hope he can figure something out.

Getting the following from CPDN again on website

Forbidden

You don't have permission to access this resource.
Apache/2.4.58 (Ubuntu) Server at main.cpdn.org Port 443

and

Thu 28 May 2026 08:57:37 AM BST |  | Project communication failed: attempting access to reference site
Thu 28 May 2026 08:57:37 AM BST | climateprediction.net | Scheduler request to https://main.cpdn.org/cgi-bin/cgi failed: SSL peer certificate or SSH remote key was not OK
Thu 28 May 2026 08:57:38 AM BST |  | Internet access OK - project servers may be temporarily down.

from BOINC.

Uploads at least were working 20 minutes ago. They go to a different server.

CPDN seems to be fully back now. One task failed to report a trickle because of a 'feeder not running' error (a normal interim state while a server is being started), but I could report it manually while I was checking.

Sidock shows now an official maintainance message on there website. Better then just an error ;)

---

---------- 24/7 Crunching since 2011 -----------
DSKAG Austria: http://www.dskag.at

From MilkyWay@home project Admins:
Message 77991

Hello everyone,

The server will be down briefly tomorrow for an update. The update has improvements to how we optimize our runs and some preparations for a new version that we will release later this week (more info on that in a day or two).

Please let us know if you notice any new issues that arise.

LHC@Home and LHCdev@Home websites are screwed. Production project seems to show development project web pages (message board, server status) and can't find my production project account. I don't have account on development project.
[edit] Also reporting finished tasks is broken.

In reply to Harri Liljeroos's message of 2 Jun 2026:

LHC@Home and LHCdev@Home websites are screwed. Production project seems to show development project web pages (message board, server status) and can't find my production project account. I don't have account on development project.
[edit] Also reporting finished tasks is broken.

It was just a short mayhem, seems to work normally now.

From MilkyWay@home project Admins:
Message 77994
Hello again

The update to the server code caused some unexpected problems that we did not experience in testing. These bugs made it impossible for any workunits made before the update to be validated. After much tinkering around we decided the best way to make sure everyone gets as much of their deserved credit as possible is to revert back to the previous server code and let completed runs validate on that. The new server code will launch with our new version update tomorrow and will be implemented in a way that these issues should not arise again. Unfortunately, any tasks that were created after the update needed to be deleted to ensure things run smoothly. We apologize for any credit that was lost because of this.

We plan to have our version update take place tomorrow, 6/3 at 18:00 UTC . This update introduces some new dwarf profiles which we will be using in our runs. With the update, we will be putting up two new "core fitting" runs which will attempt to fit the parameters of a cored-NFW profile to our dwarf as well our usual parameters. Since this is something a bit new, keep an eye out for any odd behavior.

Additionally, with this update we will be launching a new application version for Linux aarch64. Our testing shows that this should have identical behavior to the current applications, but again we ask that you look out for anything unexpected if using this. We are going to try to release applications for additional new platforms in the future. Our next focus will be on apple silicon, but I can not yet guarantee that it will happen.

Anyone else having problems connecting to Milkyway@home since they "upgraded" their servers some days ago?

According to https://www.isitdownrightnow.com/milkyway.cs.rpi.edu.html

Milkyway.cs.rpi.edu is DOWN
It is not just you. The server is not responding...

Anyone else having problems connecting to Milkyway@home since they "upgraded" their servers some days ago?

Yes; almost every connection attempt times out, though intermittently I can reach the forums (suggesting that the servers are up and running).

They posted a couple of days ago that they were aware of the issue but had yet to identify the cause.

Around the same time they reported that they have found unexpected bugs in the new application they’d deployed (1.96), which I think means there’s no work available anyway until that is fixed.

Project acts like normal here. Having one dedicated Cruncher there and it shows no signs of bad connections at the moment and cache stays pretty filled.

---

---------- 24/7 Crunching since 2011 -----------
DSKAG Austria: http://www.dskag.at

LHC@Home: website out of reach at the moment.

And so it goes, day after day :/

---

---------- 24/7 Crunching since 2011 -----------
DSKAG Austria: http://www.dskag.at

In reply to Harri Liljeroos's message of 9 Jun 2026:

LHC@Home: website out of reach at the moment.

LHC@home admins identified massive ongoing activity from rogue ai bots as root cause for the recent timeout issues.
Maybe other projects also suffer from that.
Looks like counter measures require some modifications in the BOINC server code which needs further investigation and testing.
See:
https://github.com/BOINC/boinc/issues/7119

LHC@home admins identified massive ongoing activity from rogue ai bots as root cause for the recent timeout issues.
Maybe other projects also suffer from that.
Looks like counter measures require some modifications in the BOINC server code which needs further investigation and testing.

CPDN experienced this, I think last year sometime. They made access to parts of the site where data was being harvested dependent on being logged in. They may also have blocked some IP addresses from access too but I am unsure about that.

Since the LHC@home homepage is partly shut down this is what Laurence wrote at their forum:

Degraded Website Availability
Some of you may have already noticed reduced website availability. We have been experiencing unusually heavy traffic from a distributed scraping bot. To mitigate the impact in the short term, we have temporarily disabled a number of pages and will gradually restore them over time. Thank you for your patience and understanding.

Looks like the scheduler is still online, so hosts may get work and may be able to report it back.

I wonder if they can trace back the origins of these scraper bots and write them an angry email?

In reply to danwat1234's message of 10 Jun 2026:

I wonder if they can trace back the origins of these scraper bots and write them an angry email?

Or better still get another AI lot to start scraping them.

New BOINC project idea..