|
#1
|
|||
|
|||
This is still happening as late as yesterday evening. Tried several times to no avail. Please, let's get this fixed once and for all.
Thanks |
#2
|
|||
|
|||
I have contacted the hosting company again.
|
#3
|
|||
|
|||
They are not seeing any problems at this time. Please post a screen shot the next time this occurs. Thanks.
|
#4
|
|||
|
|||
2:33 PM EST today.
|
#5
|
|||
|
|||
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." |
#6
|
|||
|
|||
I had this server busy message show over 8 times today. The hosting company can say whatever they want to say. In the end, user experience is impacted, Kinook's reputation is affected, and they have to own it and fix it.
Thanks |
#7
|
|||
|
|||
This occurred about 8:54 PM EST
|
|
|