Issue Summary:
On Friday, 19 June 2026, Brevo experienced a temporary disruption to its transactional email service. During the incident, requests sent to the transactional email API and SMTP endpoints returned errors and could not be processed. The issue was identified, mitigated, and fully resolved by our engineering team within the same day.
Customer Impact:
For approximately 49 minutes, customers were unable to send transactional emails through the Brevo platform. The disruption affected the public transactional email API, SMTP relay, and any Brevo features that rely on transactional emails to function — including Conversations, Meetings, and chat-related notifications. Marketing campaigns and other platform features were not affected. No customer data was lost.
Timeline:
Incident Start: 19 June 2026 — 14:44 UTC
Detection Time: 19 June 2026 — 14:49 UTC
Mitigation Started: 19 June 2026 — 15:28 UTC
Resolution Time: 19 June 2026 — 15:39 UTC
Recovery Confirmed:19 June 2026 — 15:43 UTC
Root Cause:
The disruption was triggered by an infrastructure-level hardware incident at one of our third-party hosting providers, which temporarily affected part of the storage layer used to process incoming transactional email requests. As a protective measure, the impacted storage component automatically switched into a safe, read-only state to prevent any data loss, which in turn prevented Brevo from accepting new transactional email requests.
Resolution:
Our engineering and infrastructure teams quickly identified the impacted component, monitored the recovery of the underlying hardware, and performed a controlled recovery procedure to restore the storage layer to a fully operational state. Once the storage layer was restored, transactional email processing resumed automatically and traffic returned to normal levels. A status page update was published and kept up to date throughout the incident.