Brevo Outage Degrades Email Delivery, Tracking Links and Contacts

Brevo suffered a broad incident on 6 November 2026 that hit email sending, tracking links and contact services at the same time. The first notice appeared on the Brevo status page at 14:05 UTC, reporting problems with Contact Services, redirection links and sending for both marketing campaigns and transactional emails. Brevo marked the incident resolved at 18:22 UTC, a little over four hours later, saying that "all affected services are now functioning normally".

Unlike the event delay Brevo reported on 2 November, this one touched delivery itself. The status page lists 15 affected components across six product areas, all marked as degraded performance, and also mentions delays in forms, automation, segmentation and event processing. Brevo has not published a root cause.

What happened

The opening update said Brevo had detected an issue affecting Contact Services, redirection links and sending for marketing campaigns and transactional emails, and that forms, automation, segmentation and event processing were delayed, disrupting some customers. At 14:52 UTC Brevo said it had found the cause and was implementing a fix.

By 15:18 UTC most services had recovered and the remaining ones were being restored. A further update at 15:58 UTC said the root cause had been identified and engineering was putting a mitigation in place. At 16:40 UTC the incident moved to monitoring, with errors falling across the affected services, and the resolution notice followed at 18:22 UTC.

The affected components

• Marketing: Marketing emails delivery, Marketing email tracking links, Statistics
• Transactional: Transactional emails delivery, Transactional emails tracking links
• Automations: Workflows, Brevo Tracker
• CRM: Contacts, Contact Management API, Sales CRM, Sales CRM API
• Conversations: Calls, Meetings
• Integrations: Outbound Webhooks

Why this one matters more than an event delay

When only an event pipeline falls behind, mail still goes out and the damage is late data. Here the delivery components themselves were degraded, along with the redirection service that powers tracked links. That opens three risks worth checking for the 14:05 to 18:22 UTC window.

Messages may have been late or not sent

Password resets, one-time codes and order confirmations sent through Brevo during the window may have arrived late. Campaigns scheduled in that window may have gone out behind schedule. The status page does not say whether any messages were dropped, so check your own logs rather than assume.

Tracked links may have failed for readers

With redirection links degraded, recipients who clicked a tracked link in that window could have hit an error or a slow redirect instead of your page. That costs clicks and conversions even on mail that was delivered normally, and those clicks may also be missing from your statistics.

Contacts and automations may be out of sync

Contacts, the Contact Management API, forms, segmentation and workflows were all affected. Sign-ups from forms, API contact updates and workflow steps that ran during the window are worth reconciling, especially unsubscribes and consent changes that must be honoured.

Action checklist

• Pull your sending logs for 14:05 to 18:22 UTC on 6 November and compare requests sent with messages delivered.
• Check critical transactional flows such as password resets and one-time codes, and let users request a new one rather than resending old codes in bulk.
• Review scheduled campaigns in the window: confirm they went out once, and do not resend just because statistics look low.
• Reconcile contacts created or updated through forms and the API during the window, starting with unsubscribes and consent changes.
• Audit workflows that were due to run in the window and look for contacts stuck or sent down the wrong branch.
• Treat click data with caution for that period, since tracking links and statistics were both degraded.
• Subscribe to the Brevo status page so the next incident reaches you before your support inbox does.

Two Brevo incidents in one week

This is the second Brevo incident SMTPedia has covered this month, after the delay in transactional email events on 2 November. Every provider has incidents. What it does show is that teams sending business-critical mail should know, in advance, how they would detect a provider problem and whether a second sending route is worth having. Our guide to transactional email services compares the options.

Sources

1. Brevo Status: Multiple services are impacted (primary source), updates of 6 November 2026

Related on SMTPedia

• Brevo delays transactional email events, webhooks and automations
• What is a transactional email? Definition, types and examples
• Best transactional email services in 2026