BEES Outage History

BEES is up right now

Pingoru has recorded 48 incidents for BEES: 21 in the last 12 months and 7 in the last 90 days.

Source: status.bees.com

48incidents recorded
21last 12 months
7last 90 days
117 minutestypical duration

Incidents, newest first

Critical July 30, 2025 Connectivity Issues Impacting Routes Across Multiple Countries 1h 22m North America, Latin America

Started Jul 30, 2025, 12:05 PM UTC· resolved Jul 30, 2025, 01:28 PM UTC

  1. investigating Jul 30, 2025, 12:05 PM UTC

    BEES Support is investigating an issue with route connectivity and portal functionality that is impacting BEES Deliver operations in multiple countries. More information will be shared in 30 minutes or as the situation unfolds. Ticket for reference: BEESOE-228319

  2. monitoring Jul 30, 2025, 12:42 PM UTC

    The impact has been mitigated and BEES specialists are now monitoring closely.

  3. resolved Jul 30, 2025, 01:28 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 29, 2025 Application Intermittency 3h 34m North America, Latin America, Africa

Started May 29, 2025, 04:17 PM UTC· resolved May 29, 2025, 07:51 PM UTC

  1. investigating May 29, 2025, 04:17 PM UTC

    BEES Support is investigating reports of intermittent errors impacting BEES Grow. More information will be shared in 30 minutes or as the situation unfolds.

  2. identified May 29, 2025, 04:41 PM UTC

    BEES Support continues to work on resolving the errors reported for Bees Grow. The root cause has been identified and the L3 teams are working towards the incident resolution. Updates to follow within the next hour.

  3. monitoring May 29, 2025, 07:41 PM UTC

    BEES support team completed mitigative actions and the platform is operational and stable. The team remains monitoring to ensure platform stability.

  4. resolved May 29, 2025, 07:51 PM UTC

    Following an extended monitoring period and successful validations by the technical teams, we confirm that the issue has been fully mitigated. The platform remains stable, and the incident is now officially considered resolved.

Read the full incident report →

Major February 4, 2025 General slowness in the application 36m Latin America, Latin America, Africa, Africa

Started Feb 04, 2025, 06:19 PM UTC· resolved Feb 04, 2025, 06:56 PM UTC

  1. investigating Feb 04, 2025, 06:19 PM UTC

    BEES Support is investigating a slowness issue impacting BEES Customer and BEES Grow in the Americas (excluding the US) and Africa. More information will be shared in 30 minutes or as the situation unfolds. Ticket for reference: BEESOE-205526

  2. investigating Feb 04, 2025, 06:27 PM UTC

    We are continuing to investigate this issue.

  3. investigating Feb 04, 2025, 06:27 PM UTC

    We are continuing to investigate this issue.

  4. monitoring Feb 04, 2025, 06:30 PM UTC

    The mitigating actions were effective, and services are stable. We will continue monitoring until full recovery is achieved.

  5. monitoring Feb 04, 2025, 06:39 PM UTC

    The mitigating actions were effective, and services are stable. We will continue monitoring until full recovery is achieved.

  6. monitoring Feb 04, 2025, 06:39 PM UTC

    We are continuing to monitor for any further issues.

  7. monitoring Feb 04, 2025, 06:39 PM UTC

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

  8. resolved Feb 04, 2025, 06:56 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical January 30, 2025 [BEES Customer][Multiple] - Data Ingestion is failing with an error 3h 16m Latin America, Africa

Started Jan 30, 2025, 09:01 AM UTC· resolved Jan 30, 2025, 12:17 PM UTC

  1. investigating Jan 30, 2025, 09:01 AM UTC

    BEES Support is investigating an issue with BEES Sync that is preventing any data ingestion to be processed. As a result, orders are likely to remain unprocessed. Multiple countries and Partners are affected. More information will be shared in 30 minutes or as the situation unfolds. Ticket for Reference: BEESOE-204898

  2. investigating Jan 30, 2025, 10:47 AM 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. monitoring Jan 30, 2025, 11:36 AM UTC

    The impact has been mitigated and BEES specialists are now monitoring it closely.

  4. resolved Jan 30, 2025, 12:17 PM UTC

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

Read the full incident report →

Critical December 16, 2024 [BEES Customer] Users can't log in 1h 4m Europe

Started Dec 16, 2024, 11:47 AM UTC· resolved Dec 16, 2024, 12:52 PM UTC

  1. investigating Dec 16, 2024, 11:47 AM UTC

    We are investigating an incident impacting European countries where BEES Customer is experiencing an intermittent issue with the login process (Mobile and Web). The case is under assessment, and actions are being taken as a priority.

  2. investigating Dec 16, 2024, 12:15 PM UTC

    The investigation is still ongoing, and the specialist teams are handling the case with the utmost priority. Updates will follow within 30 minutes. The support ticket for reference is BEESOE-199984.

  3. resolved Dec 16, 2024, 12:52 PM UTC

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

Read the full incident report →

Minor November 30, 2024 [BEES Grow][Multiple Countries] Slowness and performance intermittency 1h 6m Latin America

Started Nov 30, 2024, 03:50 PM UTC· resolved Nov 30, 2024, 04:56 PM UTC

  1. investigating Nov 30, 2024, 03:50 PM UTC

    A critical incident has been reported. BEES Operations Team is performing the initial analysis of the issue and will provide additional status update shortly. Ticket for reference: BEESOE-198183

  2. investigating Nov 30, 2024, 04:04 PM UTC

    BEES Support is investigating an issue with slowness and performance intermittency that is impacting Bees Grow in the Middle America Zone. More details will be provided within the next 20 minutes. Ticket for reference: BEESOE-198183

  3. investigating Nov 30, 2024, 04:21 PM UTC

    The impact has been mitigated and BEES specialists are now monitoring it closely. Further updates will be provided as events warrant.

  4. resolved Nov 30, 2024, 04:56 PM UTC

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

Read the full incident report →

Notice November 6, 2024 Momentary Intermittency/Slowness on the application 4h 24m

Started Nov 06, 2024, 03:00 PM UTC· resolved Nov 06, 2024, 07:25 PM UTC

  1. monitoring Nov 06, 2024, 04:12 PM UTC

    Between 15:00 and 15:32 UTC, users may have experienced an intermittency/slowness with the BEES Customer app impacting the Americas(except the US) and Africa. The teams are monitoring the application to confirm that the issue was mitigated.

  2. monitoring Nov 06, 2024, 04:15 PM UTC

    Following a period of stability, the system has begun to exhibit the same symptoms once again. Prompt mitigative measures have been implemented and the services are back to normal. The system is still under close observation.

  3. resolved Nov 06, 2024, 07:25 PM UTC

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

Read the full incident report →

Critical November 4, 2024 Application presents performance issues 20m Latin America, Africa

Started Nov 04, 2024, 04:24 PM UTC· resolved Nov 04, 2024, 04:44 PM UTC

  1. investigating Nov 04, 2024, 04:24 PM UTC

    The BEES Support team is investigating an instability issue affecting BEES customers in the Americas (excluding the US), Africa. We will provide more details within the next 30 minutes. Ticket for reference: BEESOE-194540.

  2. investigating Nov 04, 2024, 04:42 PM UTC

    A corrective action from the specialist team has just taken effect and the platforms recovered. The team remains monitoring the situation.

  3. resolved Nov 04, 2024, 04:44 PM UTC

    This incident has been resolved.

Read the full incident report →