Their reply:
"According to the provided screenshot, the time effective was 2:33p EDT,
which unfortunately does not coincide with any immediate server issues.
There was an incident chronologically recent enough which it could have
impacted server performance, but only managed to slow the server down.
Please have the client reach out once again, when the database is showing
to be incommunicable or is resulting with any errors. Given the length of
time expended between this issue and that on 25 March, we would like to
observe any further events that may arise."
|