We saw the following error for about one hour this morning (6:30AM - 7:20AM
EST). Assume it was a bad update, and once a new update arrived all corrected
itself.
Could this be a local issue, something that we may have been able to prevent, or
something beyond our control.
Sat 2009-07-18
Peer-to-Peer (Support) wrote:
We saw the following error for about one hour this morning (6:30AM - 7:20AM
EST). Assume it was a bad update, and once a new update arrived all corrected
itself.
Could this be a local issue, something that we may have been able to prevent, or
something beyond our
NetEase Operations Manager wrote:
I had the same thing this morning. About 3400 before the new update fixed
it.
What time was your event?
_M
#
This message is sent to you because you are subscribed to
the mailing list
