The schedule reboot was intended to push out some updates and give us a chance to stabilize two servers that were misbehaving (the HTTP daemon was restarting itself confusing the load balancer and causing time outs and debug pages for some users). The system did not cooperate and we had to push up the reboot schedule to 17:30 without any chance to update the notification. We apologize for the timing error and hope it wasn't too much of an inconvenience.

We have one server that did not come up cleanly which we will address tomorrow. If it requires a system reboot we will provide as much advance notice as possible.