UPDATE June 24 10:30CST: The error was caused by an incorrect configuration file being sent to some sites. The mistake has been corrected, and all sites are back up and running per normal. We are sorry for the disruption.
This morning we're getting reports of internal server errors on some sites which were not caught by our montiors. The tech team is looking into it and we will update this status ticket as soon as we have more information.