The site is not dead -_-, the server which the site calls when it loads is throwing HTTP 400 errors because of how the sockets.io engine is setup/being used in conjunction with the proxy routing/load mitigation infrastructure they have.

Responsible... maybe, responsive.. no.

I'm the last person to bash them, but unless they can't afford a spare server to do testing before they put their code live, there is no reason they shouldn't have been able to rollback to a working frontend; unless their code is so... poorly written, a change in the code makes it impossible to interface with new data(bets made, userfiles, player balances) made on the bad code, with the old working frontend.