Explanation of the problem from servstra.com (our hosting provider):
One of the routers in our NOC has crashed. The router did not restore gracefully, and as a result our engineers routed all production traffic away from this node. Emergency Maintenance Activity 488xxxx has been created to reboot this node during our 0001-0500 CDT maintenance window Sunday 8/26/2007. Once the device has restored and verified to be in a healthy state, our engineers will roll-back the previously implemented changes which moved traffic away from this node, thus restoring traffic flow to its original state. At this time, the alternate paths are functioning perfectly and there are no concerns of utilization, latency or packet loss. Traffic traversing these alternate paths may experience a momentary increase in response time as the trunks route back to their original paths; however this maintenance is expected to be a largely unnoticeable event. The maintanence has already gone without any incidents and the router has returned to its normal state.