All platform features are currently operational

We are continuing to monitor for any further issues.

Our environment is 100% restored after the actions taken by the technical team. We continue monitoring.

Start date / time: 05/06/2020 - 09:00 AM and End date / time: 03:00 PM

Customers can experience:
Error messages on Portal Desk;
Access to Portal Desk failed;
Message exchange fail in WHatsApp;

Actions implemented:
Scaling / redistribution of the machines;

The environment was restored after the implementation of the actions mentioned above.

Problem: From the analysis, problems of network degradation and failures of physical infrastructure elements were identified.

Customers can experience:
Error messages on Portal Desk;
Access to Portal Desk failed;
Message exchange fail in WHatsApp;

Palliative actions: The service team continues to carry out interventions in the environment to keep the platform operational.

Actions in progress:
Working in the machine scaling / redistribution part;
In parallel, another front working on application-oriented analysis;

We are continuing to work on a fix for this issue.

We are taking some palliative actions in an attempt to keep the platform operational, while the technical team is focused on investigations and actions to resolve definitively.

We have identified instability in the portal and Desk. Our team continues to investigate the issue.

Os clientes podem experimentar:

Mensagens de erro no Desk;
Portal, falha no acesso ao Desk
Falha na troca de mensagens no WHatsApp

We have identified instability in the portal and Desk. Our team continues to investigate the issue.

We are continuing to work on a fix for this issue.

The issue has been identified and a fix is being implemented.

The environment is stabilized, with some corrective actions taken by the technical team.
We have a multidisciplinary team focused on analysis for identification and actions for definitive correction.

A fix has been implemented and we are monitoring the results.

We had an instability that caused a momentary slow to access the desk portal. An intervention was performed on one of the servers and the accesses, after a peak of connections, normalized and are currently stable. Our team remains mobilized to investigate the problem.

We have identified instability, some users may experience slowness to access portal and Desk. Our team continues to investigate the issue.

We have identified instability in the portal and Desk. Our team continues to investigate the issue.

The environment is stabilized, with some corrective actions taken by the technical team.
We have a multidisciplinary team focused on analysis for identification and actions for definitive correction.

The environment is stabilized, with some corrective actions taken by the technical team.
We have a multidisciplinary team focused on analysis for identification and actions for definitive correction.

A fix has been implemented and we are monitoring the results.

Some users may have lost their connection. Need to update the page and try to reconnect

We are managing to maintain the operational environment, while the technical team is working on definitive solution actions.

We are continuing to work on a fix for this issue.

Customers may still experience some effects:

Error messages on the Desk;
Portal, Desk access failure
failed message exchange on WHatsApp

We are working on a hotfix to try to resolve the issue.

We continue to work to resolve the problem as soon as possible.

We are working with palliative interventions to minimize impacts.

A fix has been implemented and we are monitoring the results.

We carried out some palliative measures in order to restore the platform acess. The technical team continues to investigate based on the evidence collected so that a definitive solution can be implemented.

Period:

Start date / time: 10:17 AM
End date / time: of palliative solution: 11:15 AM

Impact for customers:

Error messages on the Desk;
Portal, Desk access failure
failed message exchange on WHatsApp

The issue has been identified and a fix is being implemented.

We are currently investigating this issue.