I've also been seeing the error on and off for the last week.  Interestingly, when the website is working, if I keep a browser window open on the page (and if the window doesn't reload), then I can still click around on the tabs and play the Hi-Lo game when the site is technically down.  It is good that they coded the website well to work on the client-side, and not hit the server with excessive reloads.

As a web developer, I've faced the dreaded 500 internal server error many times.  It is one of the most frustrating problems, because the error is so descriptive, right?  You check the error logs, as advised, and many times there is nothing helpful in there, either.  Fun stuff!  I learned to check file and directory permissions, and that solved a lot of the problems with my scripts.  If it wasn't a permissions problem (99% of problems were file permissions for me), I'd comment out all the non-working code, and add stuff back in one section at a time until I found the culprit.

Internal Server Error can be caused by the following:
- Incorrect file and directory permissions
- Database problems - query errors, slow response
- Misconfigured web server - mistakes or issues with .htaccess files or virtual hosts
- Large files on website consuming too many server resources
- Too many users hitting the server at the same time, consuming too many resources
- Connectivity issues
- Conflicts between different software components (why can't programs play nicely together, right?)

Anyway, my heart goes out to the web developers.  I hope they are able to figure out the problem and fix it, soon.