All my crunchers ran out of work during the outage and I switched them all off except one. If others too have done the same, then I guess the electricity consumption all over the world might have seen a dip during these days.

Good to see that things are up and running, however, all I am seeing is - Scheduler request failed: Failure when receiving data from the peer, and Scheduler request failed: Timeout was reached.

Just to be pessimistic, there are 22,000 AP tasks waiting to be allocated. At 8 MB each, that's 180,000 MB. Let's be generous and call the 94 Mb/s download limit 10 MB/s. So that's 18,000 secs or 5 hours to download just those, never mind however many have already been allocated but not downloaded, plus the MB load. We'll be seeing timeouts for a while...
____________

Situation normal for recovering from an outage - everything maxed out and lots of re-tries. Given the duration of the outage its going to be a few days before "normal" services are resumed.
Sit tight and enjoy the ride...
____________
Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

Just spotted something strange on the server status page "Lando" appears to have gained an "x" in his name to become "Xlando". Was he a casualty of the recent woes, or is this part of a planned move to retire him gracefully?
____________
Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

That's because Seti Beta's 'Down for Maintenance' web page hasn't got the scheduler url embedied in it (unlike the Main project),
until the normal Seti Beta web page appears very few hosts will manage to connect to Seti Beta, (unless you edit your client_state.xml and put the url back in)

Looks like my one random-chance success earlier was all I've gotten. 50+ attempts since then on both machines and not a single one has gotten through.

I'm getting:

failed sending data to the peer
failure when receiving data from the peer
couldn't connect to server
server returned nothing (no headers, no data)

whoa.. my single-core machine finally got through and got 12 ghosts resent to it. Each of those download on the first try at 45-60KB/sec.

edit: then my main cruncher (AP-only) managed to get through. Reported its tasks, got 8 new ones, then a few failed attempts later, got 4 more lost tasks resent. Each AP DL happened on the first try and ran about 35K/sec the whole way.

So.. it looks like it is spotty success at best, but when the success happens, it seems to work just fine for me. No proxies, opposite coast of the country.
____________
Linux laptop:
Record uptime: 1484d 22h 42m
Ended due to UPS failure, as discovered 14 hours later