Desk e Portal.blip.ai unavailable
Incident
Report for Blip
Postmortem
Good afternoon,
First of all I would like to apologize for the inconvenience caused.
Identified scenario:
A request overload was identified in the webapp service (Communication between applications that is responsible for user authentication), which did not allow user authentication or access.
Impact to the customer:
The client did not have access to the portal and blipdesk
Correction applied:
Instances of the webapp were escalated. After the service was performed, access to the platform was normalized
Root cause:
The performance of the technical team was to mitigate the overload in the webapp, and an investigation is being carried out in order to identify the cause of the overload in the period.
Start date / time: 15:10
End date / time: 16:39
Resolved
This incident has been resolved.
Update
We are continuing to monitor for any further issues.
Update
We are continuing to monitor for any further issues.
Monitoring
Status: Monitoring
Scenario: The service webapp instance was increased from 6 to 10 and all the accesses have normalized. Our team is monitoring the scenario to guarantee Blip’s stability for all customers. The main cause of the problem is still under investigation. When we have identified the reason for this error, we will be reporting in the postmortem
Incident Location: Blip Desk and Portal
Affected Users: Enterprise, Business and Standard
Scenario: The service webapp instance was increased from 6 to 10 and all the accesses have normalized. Our team is monitoring the scenario to guarantee Blip’s stability for all customers. The main cause of the problem is still under investigation. When we have identified the reason for this error, we will be reporting in the postmortem
Incident Location: Blip Desk and Portal
Affected Users: Enterprise, Business and Standard
Update
Status: Under investigation
Scenario: The service webapp instance was increased and related components restarted. A good part of the accesses have already normalized. However, because of the large volume of inputs, isolated failure occurrences persist.
Incident Location: Blip Desk and Portal
Affected Users: Enterprise, Business and Standard
Next Update: in 30 minutes
Scenario: The service webapp instance was increased and related components restarted. A good part of the accesses have already normalized. However, because of the large volume of inputs, isolated failure occurrences persist.
Incident Location: Blip Desk and Portal
Affected Users: Enterprise, Business and Standard
Next Update: in 30 minutes
Identified
Status: Identified
Scenario: Our monitoring identified a connection failure with the database responsible for authenticating the users of the blip, causing failure in accessing the Portal and Desk.
Incident Location: Blip Desk and Portal
Affected Users: Enterprise, Business and Standard
Next Update: in 15 minutes
Scenario: Our monitoring identified a connection failure with the database responsible for authenticating the users of the blip, causing failure in accessing the Portal and Desk.
Incident Location: Blip Desk and Portal
Affected Users: Enterprise, Business and Standard
Next Update: in 15 minutes
Update
We are continuing to investigate this issue.
Investigating
We identified unavailability of access to the Portal and Desk.
This incident affected: Desk and Blip Platform (Portal).