#39 - May 9, 2009, 7:43 p.m.
Due to the unique nature and sporadic recurrence of this issue, it can be incredibly difficult to isolate the cause and eliminate it. Early indications led us to believe that this issue was directly related to our servers; however, previous resolutions appear to have been unsuccessful. Because this issue has reappeared, we have forwarded it on for further review by our Quality Assurance and Development teams.
I, personally, am unaware as to whether or not the core of the issue has been identified. With that being said, it's entirely possible that the issue has been identified but information has not yet been provided.
Should any further information come our way, we'll do our best to keep you updated.