Brevo incident

Delay in event processing

Minor Resolved View vendor source →

Brevo experienced a minor incident on May 17, 2026 affecting Workflows and Transactional SMS, lasting —. The incident has been resolved; the full update timeline is below.

Started
May 17, 2026, 06:44 PM UTC
Resolved
May 17, 2026, 06:44 PM UTC
Duration
Detected by Pingoru
May 17, 2026, 06:44 PM UTC

Affected components

WorkflowsTransactional SMS

Update timeline

  1. investigating May 17, 2026, 04:59 PM UTC

    Status: Investigating We’ve detected an issue affecting segmentation and automation and as a result, some customers may be experiencing disruptions while using it. Our team is actively investigating the root cause and working to resolve the issue as quickly as possible. We apologize for the inconvenience and will share further updates as soon as we have more information. Affected components Workflows (Degraded performance)

  2. identified May 17, 2026, 05:23 PM UTC

    Status: Identified We have identified the cause of the issue affecting some services. Our team is working on implementing a fix to mitigate the impact. We will continue to share updates as we progress toward resolution. Affected components Workflows (Degraded performance) Transactional SMS (Degraded performance)

  3. monitoring May 17, 2026, 05:30 PM UTC

    Status: Monitoring All the delayed events have been processed successfully, event processing lag has been resolved except for a single missing node. We’ll provide an update once we confirm the issue is fully resolved. Affected components Workflows (Degraded performance) Transactional SMS (Degraded performance)

  4. resolved May 17, 2026, 06:44 PM UTC

    Status: Resolved The issue has been resolved, and all affected services are now functioning normally. Thank you for your patience while we worked to address the issue. Affected components Workflows (Operational) Transactional SMS (Operational)