If you have been paying attention, you may have noticed that YackTrack restarted early this morning. I was waiting to ensure that things continued to be stable for the majority of the day before stating that YackTrack was back to normal. Given the uneventful day, I think we can say that things are stable again.
What went wrong? Honestly, I am not sure entirely. Based on the symptoms, there was a problem with some administrative server software that caused the entire JDK to become unstable. Based on my hosting service, this was a known problem but it did not have a solution as the problematic service has become unsupported. Obviously, this is not the best answer that I wanted to hear, but I did have options. I could move YackTrack to another hosting service, move YackTrack to a new server or just rebuild the server. At this point, I have taken the simplest option of rebuilding the server. Eventually, I will be looking into my other options in the long term as this type of instability could become a problem in the next year.
Thank you for your patience and I apologize for any inconvenience the system outage has caused.

