Brevo

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-19 14:47 UTC

   We’ve identified an issue affecting public API requests to Corporate endpoints. As a result, some customers may be experiencing **5xx errors** when making requests to these endpoints. The impact is currently limited to Corporate endpoints, with other endpoints unaffected. Our...

2. monitoring 2026-10-19 15:04 UTC

   We have mitigated the impact and are seeing a reduction in errors across the affected services. We continue to monitor our systems closely to ensure stability. We’ll provide an update once we confirm the issue is fully resolved.

3. resolved 2026-10-19 15:06 UTC

   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.

Excerpts are shortened. Read the full incident on Brevo's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-15 23:00 UTC

   We’ve detected an issue affecting transactional and automation services, and as a result, some customers may be experiencing delays or disruptions while using these services. Our team is actively investigating the root cause, including elevated latency and event processing...

2. identified 2026-10-15 23:07 UTC

   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.

3. resolved 2026-10-15 23:10 UTC

   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.

Excerpts are shortened. Read the full incident on Brevo's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-15 04:34 UTC

   We’ve detected an issue affecting the Loyalty API, which may be causing disruptions for some customers using the service. 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...

2. identified 2026-10-15 04:40 UTC

   We have identified the root cause of the issue affecting the Loyalty API Endpoints, which may be causing disruptions for some customers using the service. Our team is actively working on implementing a fix to mitigate the impact and restore the service as quickly as possible. We...

3. monitoring 2026-10-15 04:45 UTC

   We have mitigated the impact of the issue affecting the Loyalty API and are seeing a reduction in errors across the affected services. Our team continues to monitor the systems closely to ensure stability and confirm that the issue is fully resolved. We will provide a further...

4. resolved 2026-10-15 04:46 UTC

   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.

Excerpts are shortened. Read the full incident on Brevo's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-14 16:14 UTC

   We’ve detected an issue affecting **Transactional Emails and Redirection Links**, which may be causing disruptions for some customers. In particular, some customers may experience **delays in the delivery of transactional emails**. Our team is actively investigating the root...

2. investigating 2026-10-14 16:30 UTC

   We would like to inform you that we are currently investigating an issue affecting multiple Brevo services. The impact includes **delays and errors affecting Transactional and Marketing email services, Redirection Links, and other related services such as SMS, Contacts, and...

3. monitoring 2026-10-14 16:34 UTC

   We have mitigated the impact and are seeing a reduction in errors across the affected services. We continue to monitor our systems closely to ensure stability. We’ll provide an update once we confirm the issue is fully resolved.

4. resolved 2026-10-14 16:47 UTC

   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.

Excerpts are shortened. Read the full incident on Brevo's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-14 08:26 UTC

   We’ve detected an issue affecting Transactional Email Delivery and Preview, which may be causing disruptions for some customers. Our team is actively investigating the root cause and working to resolve the issue as quickly as possible. We apologize for the inconvenience and...

2. monitoring 2026-10-14 08:28 UTC

   We have now mitigated the impact, and Transactional Email Delivery should be working as expected. However, there may still be some delays with Transactional Email Preview. We’re also seeing a reduction in errors across the affected services and continue to closely monitor our...

3. resolved 2026-10-14 08:32 UTC

   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.

Excerpts are shortened. Read the full incident on Brevo's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-07 15:37 UTC

   Since approximately 12:00 UTC on 7 October, our event processing pipeline has been experiencing delays. As a result: Automations triggered by events (e.g. email opens, clicks, transactional events) are running with a delay — triggers will fire late, but no events are lost and...

2. identified 2026-10-07 15:38 UTC

   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.

3. monitoring 2026-10-07 15:39 UTC

   We have mitigated the impact and are seeing a reduction in errors across the affected services. We continue to monitor our systems closely to ensure stability. We’ll provide an update once we confirm the issue is fully resolved.

4. resolved 2026-10-07 18:23 UTC

   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.

Excerpts are shortened. Read the full incident on Brevo's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-07 12:21 UTC

   We’ve detected an issue affecting Ecommerce orders, 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...

2. monitoring 2026-10-07 12:27 UTC

   We have mitigated the impact and are seeing a reduction in errors across the affected services. We continue to monitor our systems closely to ensure stability. We’ll provide an update once we confirm the issue is fully resolved.

3. resolved 2026-10-07 12:32 UTC

   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.

Excerpts are shortened. Read the full incident on Brevo's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-07 07:15 UTC

   We’ve detected an issue affecting sending emails. As a result, some customers may see emails delayed by 6 to 8 minutes. Our team is actively investigating and working to resolve the issue as quickly as possible. We apologize for the inconvenience and will share further updates...

2. monitoring 2026-10-07 07:37 UTC

   We have mitigated the impact and are seeing no delays now. We continue to monitor our systems closely to ensure stability. We’ll provide an update once we confirm the issue is fully resolved.

3. resolved 2026-10-07 12:03 UTC

   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.

Excerpts are shortened. Read the full incident on Brevo's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-06 07:47 UTC

   We have been investigating increased latency affecting email preview generation since approximately 04:30 UTC today. Email sending and delivery are operating normally — only previews are affected. As a result, image previews and "view in browser" (mirror) links may be slow to...

2. identified 2026-10-06 08:43 UTC

   We have identified the cause of the issue affecting Email Previews generation. Our team is currently working on implementing a fix to mitigate the impact. Email sending and delivery continue to operate normally. Email Previews and “View in browser” (mirror) links may still be...

3. monitoring 2026-10-06 10:18 UTC

   We have mitigated the impact and are seeing a reduction in errors across the affected services. We continue to monitor our systems closely to ensure stability. The lag is decreasing now and we will update once the issue is fully resolved . We’ll provide an update once we confirm...

4. resolved 2026-10-06 11:55 UTC

   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.

Excerpts are shortened. Read the full incident on Brevo's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: Network or DNS. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-05 07:18 UTC

   Between 07:00 UTC and 07:08 UTC transactional emails were delivered with a delay of approximately 8 minutes. The delay was caused by connectivity errors with an internal component of our transactional sending pipeline. Affected messages were queued and delivered once...

2. identified 2026-10-05 07:19 UTC

   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.

3. resolved 2026-10-05 07:20 UTC

   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.

Excerpts are shortened. Read the full incident on Brevo's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-10-02 09:38 UTC

   We’ve detected an issue affecting **SMS routing to Sweden**, 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...

2. monitoring 2026-10-02 10:55 UTC

   Our upstream provider for SMS to Sweden mitigated the impact and we are seeing a reduction in errors across the affected services. We continue to monitor our systems closely to ensure stability. We’ll provide an update once we confirm the issue is fully resolved.

3. resolved 2026-10-02 12:00 UTC

   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.

Excerpts are shortened. Read the full incident on Brevo's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-01 10:19 UTC

   We’ve detected an issue affecting our SMS service that is causing soft bounces, and as a result, some customers may be experiencing disruptions while sending SMS messages. Our team is actively investigating the root cause and working to resolve the issue as quickly as possible....

2. identified 2026-10-01 12:17 UTC

   We have identified the cause of the issue affecting our SMS services. Our team is currently working on implementing a fix to mitigate the impact. We will continue to share updates as we make progress toward resolving the issue.

3. resolved 2026-10-01 12:21 UTC

   The issue has been resolved, and all SMS campaigns and transactional SMS will now be processed without any issues. Thank you for your patience and cooperation while we worked to address the issue.

Excerpts are shortened. Read the full incident on Brevo's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-25 14:42 UTC

   We’ve detected an issue affecting **push notifications**, 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...

2. identified 2026-09-25 14:49 UTC

   We have identified the cause of the issue affecting push notifications. Our team is working on implementing a fix to mitigate the impact. We will continue to share updates as we progress toward resolution.

3. resolved 2026-09-25 14:57 UTC

   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.

Excerpts are shortened. Read the full incident on Brevo's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-25 06:32 UTC

   We’ve detected an issue affecting transactional emails, marketing emails, contacts services and events, 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...

2. monitoring 2026-09-25 06:42 UTC

   We have mitigated the impact and are seeing a reduction in errors across the affected services. We continue to monitor our systems closely to ensure stability. Clients may have observed a small delay of email deliveries during this time. We’ll provide an update once we confirm...

3. resolved 2026-09-25 06:59 UTC

   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.

Excerpts are shortened. Read the full incident on Brevo's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-21 09:44 UTC

   We have identified issue effecting our Phone and Conversations service. Some phone call history data is not complete, will be refilled soon Gmail and Outlook conversations emails are currently delayed or not delivered, both for incoming and outgoing messages. This issue affects...

2. monitoring 2026-09-21 10:16 UTC

   Phone services have been restored, and Conversations are currently processing. Email processing has also resumed. Due to the large volume of emails queued during the issue, processing will take some time. We are continuing to work through the backlog and are monitoring the...

3. resolved 2026-09-21 12:12 UTC

   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.

Excerpts are shortened. Read the full incident on Brevo's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-20 15:02 UTC

   We’ve detected an issue affecting the Transactional Platform Frontend, and as a result, some customers may be experiencing disruptions while checking the Transactional Email Logs and Statistics. Please be informed that only the frontend view is impacted; the underlying...

2. identified 2026-09-20 15:11 UTC

   We have identified the cause of the issue affecting the Transactional Platform Frontend. Our team is working on implementing a fix to mitigate the impact. We will continue to share updates as we progress toward resolution.

3. monitoring 2026-09-20 15:15 UTC

   We have mitigated the impact and are seeing a reduction in errors across the affected services. We continue to monitor our systems closely to ensure stability. We’ll provide an update once we confirm the issue is fully resolved.

4. resolved 2026-09-20 15:15 UTC

   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.

Excerpts are shortened. Read the full incident on Brevo's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-19 12:51 UTC

   We’ve detected an issue affecting contacts and import services, 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...

2. identified 2026-09-19 13:15 UTC

   We have identified the cause of the issue affecting Contacts and Import Services. Our team is currently working on implementing a fix to mitigate the impact. We will continue to monitor the situation closely and share further updates as we make progress toward resolution.

3. monitoring 2026-09-19 13:25 UTC

   We have mitigated the impact and are seeing a reduction in errors across the affected services. We continue to monitor our systems closely to ensure stability. We’ll provide an update once we confirm the issue is fully resolved.

4. resolved 2026-09-19 13:30 UTC

   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.

Excerpts are shortened. Read the full incident on Brevo's status page.

Failure mode: Security incident or emergency response to a vulnerability. Root cause: An external attack. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-09-14 21:00 UTC

   The issue has been resolved and all systems are safe. A post-mortem has been published.

Excerpts are shortened. Read the full incident on Brevo's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-17 09:20 UTC

   We’ve detected an issue affecting Transactional Email delivery and Redirection links for both Marketing Email Campaigns and Transactional Emails. As a result, some customers may be experiencing disruptions when using these services. Our team is actively investigating the root...

2. identified 2026-09-17 09:27 UTC

   We have identified the cause of the issue affecting Transactional Email delivery and Redirection links for Marketing Email Campaigns and Transactional Emails. Our team is currently working on implementing a fix to restore the affected services and mitigate the impact. We will...

3. identified 2026-09-17 09:57 UTC

   Our team continues to work on implementing the fix for the identified issue affecting Transactional Email delivery and Redirection links for Marketing Email Campaigns and Transactional Emails. We are actively monitoring the situation and working to restore full functionality as...

4. monitoring 2026-09-17 10:50 UTC

   We have mitigated the impact and are seeing a reduction in errors across the affected services. We continue to monitor our systems closely to ensure stability. We’ll provide an update once we confirm the issue is fully resolved.

5. resolved 2026-09-17 11:00 UTC

   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.

Excerpts are shortened. Read the full incident on Brevo's status page.

Failure mode: Security incident or emergency response to a vulnerability. Root cause: An external attack. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2026-09-10 08:30 UTC

   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.

Excerpts are shortened. Read the full incident on Brevo's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-10 10:29 UTC

   We’ve have an issue impacting SSO and SAML login , and as a result, some customers may be experiencing disruptions while using it. Our team is actively investigating the issue and working to resolve the issue as quickly as possible. We apologize for the inconvenience and will...

2. resolved 2026-09-10 10:50 UTC

   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.

Excerpts are shortened. Read the full incident on Brevo's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-08 16:31 UTC

   We’ve detected an issue affecting Links in emails, 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...

2. identified 2026-09-08 18:23 UTC

   We have identified the cause of the issue affecting the services. Our team is working on implementing a fix to mitigate the impact. We will continue to share updates as we progress toward resolution.

3. resolved 2026-09-08 19:35 UTC

   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.

Excerpts are shortened. Read the full incident on Brevo's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-31 16:08 UTC

   We’ve detected an issue affecting campaign reports and statistics, which may result in some clients seeing incorrect or inconsistent data in their campaign reports. Our team is actively investigating the root cause and working to resolve the issue as quickly as possible. We...

2. investigating 2026-08-31 16:46 UTC

   Our team is continuing to investigate the issue and identify the root cause. We’ll provide a further update as soon as we have more information.

3. identified 2026-08-31 17:12 UTC

   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.

4. resolved 2026-08-31 17:14 UTC

   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.

Excerpts are shortened. Read the full incident on Brevo's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-08-26 11:11 UTC

   We have identified the cause of the issue affecting some services. Our team is working on implementing a fix to mitigate the impact. What you may notice: - Errors or timeouts when accessing or updating contacts in the application and via the Contacts API - Campaign reports...

2. identified 2026-08-26 11:33 UTC

   We have implemented a fix and restored the affected database cluster. Contact operations in the application and API are back to normal, and transactional email delivery has caught up. Remaining queued events are now being processed: campaign open statistics and open-event...

3. identified 2026-08-26 12:23 UTC

   We have identified and stopped the cause of this incident, and our team is now working on fully restoring the affected systems. We currently expect this to complete within approximately the next hour. Until then, you may still notice: - Errors when creating or updating contacts...

4. monitoring 2026-08-26 13:58 UTC

   We have applied the required fix and all services have been restored. Contact operations, email sending (campaigns and transactional), campaign statistics, webhooks, and SMS status updates are back to normal, and any remaining queued events are catching up automatically. No data...

5. resolved 2026-08-26 14:08 UTC

   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.

Excerpts are shortened. Read the full incident on Brevo's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-12 12:44 UTC

   We’ve detected an issue affecting the Phone Application, and as a result, some customers may be experiencing disruptions when making or receiving calls through the Phone Application. Our team is actively investigating the root cause and working to resolve the issue as quickly as...

2. identified 2026-08-12 12:55 UTC

   We have identified the cause of the issue affecting the Phone Application services. Our team is working on implementing a fix to mitigate the impact. We will continue to share updates as we progress toward resolution.

3. monitoring 2026-08-12 12:57 UTC

   We have mitigated the impact and are seeing a reduction in errors across the affected services. We continue to monitor our systems closely to ensure stability. We’ll provide an update once we confirm the issue is fully resolved.

4. resolved 2026-08-12 13:11 UTC

   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.

Excerpts are shortened. Read the full incident on Brevo's status page.