Desk Application Degradation
Incident Report for Blip
Resolved
This incident has been resolved.
Posted May 04, 2021 - 14:37 GMT-03:00
Monitoring
Fault identified:

We had a high CPU consumption on three of our servers with one of our clusters of six servers. We have not yet been able to identify which offender caused the high requisition volume in a short period of time. The environment is already restored.

Reflection for the client:

Slowness in accessing the portal and desk, failure to load conversations on the desk, disconnection on the desk, problems with forwarding messages between the attendant and the customer.

Action in progress: The technical team is evaluating what caused the high volume of requests culminating in the high consumption of CPU and memory resources. The Post Mortem for customers will be updated on this Here on the status page as soon as we have an update on the root cause.

Start date 04/05/2021 time: 10:07
End date 04/05/2021 time: 10:30
Posted May 04, 2021 - 10:30 GMT-03:00
Update
We are continuing to work on a fix for this issue.
Posted May 04, 2021 - 10:20 GMT-03:00
Identified
In our monitoring, we identified a degradation in the Desk.

The team is already verifying this degradation.
Posted May 04, 2021 - 10:07 GMT-03:00
This incident affected: Desk.