Blip incident

Blip Desk and Builder - [Degraded performance]

Minor Resolved View vendor source →

Blip experienced a minor incident on November 28, 2024 affecting Bot Builder and Desk and 1 more component, lasting 1h 15m. The incident has been resolved; the full update timeline is below.

Started
Nov 28, 2024, 06:15 PM UTC
Resolved
Nov 28, 2024, 07:31 PM UTC
Duration
1h 15m
Detected by Pingoru
Nov 28, 2024, 06:15 PM UTC

Affected components

Bot BuilderDeskBot Builder

Update timeline

  1. investigating Nov 28, 2024, 06:42 PM UTC

    We are currently experiencing low performance in Blip Desk and Builder. Impact: Slowness when using Blip Desk and processing commands within Builder. Update: Our support team is actively working on it.

  2. identified Nov 28, 2024, 06:47 PM UTC

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

  3. monitoring Nov 28, 2024, 06:58 PM UTC

    After identifying that the infrastructure in which CSPS API requests (Internal APIs) travel was without flow, intervention was carried out in the environment (replicas were scaled to 20). After testing, we identified that the APIs responded again.

  4. resolved Nov 28, 2024, 07:31 PM UTC

    This incident has been resolved.

  5. postmortem Nov 28, 2024, 07:31 PM UTC

    **Start Time:** 28/11/2024 ~15:05 \(GMT-3\) **End Time:** 28/11/2024 ~15:45 \(GMT-3\) **Incident Summary:** Unavailability of Blip APIs created by services teams. **Impact Analysis:** In short, the APIs developed by Blip's services teams were unavailable, causing a break in the conversational flow in smart contacts that have direct integration with them. It is important to highlight that the scenario in question only affected the APIs built by Blip's digital cells and that our platform remained intact throughout this period, having no relation to this incident. **Mitigation Measures:** To restore the APIs, we carried out interventions in the infrastructure where they were located and after testing we confirmed the normalization of the services. **Root Cause Analysis:** In the face of the normalization of the environment, we classify the incident as resolved and now enter the root cause analysis stage. This process will be conducted internally, as quickly as the situation requires, and will be published here on the status page as soon as possible. If you have any questions or need additional clarification, we recommend that you contact the CSM of your account for support.