BEES incident

Deliver portal application facing issues in affected countries

Minor Resolved View vendor source →

BEES experienced a minor incident on October 8, 2026 affecting Latin America, lasting 5h 20m. The incident has been resolved; the full update timeline is below.

Started
Oct 08, 2026, 03:42 PM UTC
Resolved
Oct 08, 2026, 09:03 PM UTC
Duration
5h 20m
Detected by Pingoru
Oct 08, 2026, 03:42 PM UTC

Affected components

Latin America

Update timeline

  1. investigating Oct 08, 2026, 03:42 PM UTC

    BEES Support is investigating cases of degraded performance affecting Deliver in Paraguay, Argentina, Bolivia, Colombia, Mexico, Ecuador, Panama, Peru and Brazil. More information will be shared in 30 minutes or as the situation unfolds. Ticket for Reference: ITOPS-63169

  2. investigating Oct 08, 2026, 04:11 PM UTC

    The investigation is still ongoing and the case is being handled with the highest priority by our specialists. Updates to follow within the next hour.

  3. identified Oct 08, 2026, 05:11 PM UTC

    BEES Support continues to work on resolving the portal application issues for Deliver. The point of failure has been identified and the specialists are working towards the incident resolution. Updates to follow within the next hour.

  4. identified Oct 08, 2026, 06:11 PM UTC

    BEES Support continues to work on resolving the portal application issues for Deliver. The point of failure has been identified and the specialists are working towards the incident resolution. Updates to follow within the next hour.

  5. identified Oct 08, 2026, 07:11 PM UTC

    BEES Support continues to work on resolving the portal application issues for Deliver. The point of failure has been identified and the specialists are working towards the incident resolution. Updates to follow within the next hour.

  6. monitoring Oct 08, 2026, 08:16 PM UTC

    Signs of improvement have been observed and BEES specialists are now monitoring it closely.

  7. resolved Oct 08, 2026, 09:03 PM UTC

    The issue has been resolved and the service is now operating normally. This case is, therefore, closed.