Brevo Outage History

Started Apr 17, 2026, 06:58 AM UTC· resolved Apr 17, 2026, 07:48 AM UTC

1. investigating Apr 17, 2026, 06:58 AM UTC

   We’ve detected an issue affecting transactional email sending, and as a result, clients may be experiencing disruptions when sending transactional emails. 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.

2. identified Apr 17, 2026, 07:11 AM 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 Apr 17, 2026, 07:19 AM 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 Apr 17, 2026, 07:48 AM 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.

Read the full incident report →

Started Apr 08, 2026, 05:16 PM UTC· resolved Apr 08, 2026, 06:29 PM UTC

1. investigating Apr 08, 2026, 05:16 PM UTC

   A limited number of clients may experience delays in SMS campaign delivery, as campaigns with URL shortening enabled may encounter processing delays. 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.

2. monitoring Apr 08, 2026, 05:49 PM UTC

   The impact has been mitigated, and no errors are currently observed across the affected services. We continue to monitor our systems closely to ensure stability. An update will be provided once the issue is fully resolved.

3. resolved Apr 08, 2026, 06:29 PM 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.

Read the full incident report →

Started Apr 01, 2026, 05:26 PM UTC· resolved Apr 01, 2026, 07:06 PM UTC

1. investigating Apr 01, 2026, 05:26 PM UTC

   We are currently experiencing an issue affecting the campaign listing page and email sending functionality. As a result, some customers may encounter disruptions while using these features. 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 provide further updates as more information becomes available.

2. investigating Apr 01, 2026, 06:13 PM UTC

   We are continuing to work on a fix to resolve the issue. Our team remains actively engaged, and we will provide an update once the issue has been fully resolved.

3. identified Apr 01, 2026, 06:34 PM UTC

   We have identified the cause of the issue affecting the campaign listing page and have mitigated the impact. The campaign listing page is now loading correctly. Our team is currently working on resolving the remaining issues impacting email sending functionality. We will provide a further update once we confirm the issue has been fully resolved.

4. resolved Apr 01, 2026, 07:06 PM 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.

Read the full incident report →

Started Mar 30, 2026, 10:47 AM UTC· resolved Mar 30, 2026, 11:27 AM UTC

1. investigating Mar 30, 2026, 10:47 AM UTC

   We’ve detected an issue affecting the track events functionality within the Automation service, 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.

2. identified Mar 30, 2026, 10:56 AM 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 Mar 30, 2026, 11:07 AM UTC

   I have skipped the client and let me monitor

4. monitoring Mar 30, 2026, 11:08 AM 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 Mar 30, 2026, 11:27 AM 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.

Read the full incident report →

Started Mar 26, 2026, 12:03 PM UTC· resolved Mar 26, 2026, 01:12 PM UTC

1. investigating Mar 26, 2026, 12:03 PM UTC

   We are currently experiencing an issue affecting SMS replies, which may result in some customers facing disruptions in receiving replies to SMS messages. Our team is actively investigating the root cause and working to resolve the issue as quickly as possible. We sincerely apologize for the inconvenience and will share further updates as more information becomes available.

2. identified Mar 26, 2026, 12:31 PM UTC

   We have identified the cause of the issue affecting the SMS REPLIES. 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 Mar 26, 2026, 12:46 PM 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 Mar 26, 2026, 01:12 PM UTC

   The issue has been resolved, and all affected services are now operating normally. Timeframe: Beginning 19th March, 8:00 AM (Paris time) What Was Impacted: During this period, a small fraction of Unsubscribe and SMS Reply Events may not have been processed. We sincerely thank you for your patience and understanding while we worked to resolve this issue.

Read the full incident report →

Started Mar 20, 2026, 08:03 PM UTC· resolved Mar 20, 2026, 08:58 PM UTC

1. investigating Mar 20, 2026, 08:03 PM UTC

   We’ve identified an issue impacting campaign sending, which may cause campaign sending delays for some customers. Our team is actively investigating the root cause and working to resolve it as quickly as possible. We apologize for the inconvenience and will share further updates as soon as more information is available.

2. identified Mar 20, 2026, 08:36 PM UTC

   We have identified the cause of the issue affecting campaign sending service. 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 Mar 20, 2026, 08:56 PM 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 Mar 20, 2026, 08:58 PM 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.

Read the full incident report →

Started Mar 10, 2026, 03:42 PM UTC· resolved Mar 10, 2026, 05:23 PM UTC

1. investigating Mar 10, 2026, 03:42 PM UTC

   We are currently investigating an issue affecting the Meetings feature, where users may experience difficulties booking, rescheduling, or canceling meetings. 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.

2. investigating Mar 10, 2026, 04:09 PM UTC

   We are still working to identify the root cause and will provide another update as soon as more information becomes available

3. identified Mar 10, 2026, 04:20 PM 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. monitoring Mar 10, 2026, 05:09 PM 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 Mar 10, 2026, 05:23 PM 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.

Read the full incident report →

Started Feb 26, 2026, 04:15 PM UTC· resolved Feb 26, 2026, 04:30 PM UTC

1. investigating Feb 26, 2026, 04:15 PM UTC

   We’ve detected an issue affecting contacts history timeline, 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.

2. monitoring Feb 26, 2026, 04:25 PM 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 Feb 26, 2026, 04:30 PM 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.

Read the full incident report →

Started Feb 25, 2026, 09:58 AM UTC· resolved Feb 25, 2026, 11:00 AM UTC

1. investigating Feb 25, 2026, 09:58 AM UTC

   We’ve detected an issue affecting custom objects operation, and as a result, some customers may be experiencing delays in object insertion and updation. 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.

2. resolved Feb 25, 2026, 11:00 AM 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.

Read the full incident report →

Started Feb 23, 2026, 02:19 PM UTC· resolved Feb 23, 2026, 05:06 PM UTC

1. investigating Feb 23, 2026, 02:19 PM UTC

   We are currently investigating an issue impacting Notifications, Transactional Email, and Account Management services. Customers may experience delays in notification delivery, issues with transactional emails delivery, and intermittent errors when accessing account management features. Our engineering teams are actively working to identify the root cause and restore full service as quickly as possible. We will provide further updates as more information becomes available. Thank you for your patience.

2. identified Feb 23, 2026, 02:37 PM UTC

   We have identified the root cause of the issue affecting some services as a network disruption with one of our hosting providers. Our engineering team is actively coordinating with the provider to restore full service as quickly as possible. We will continue to share timely updates as we make progress toward full resolution.

3. identified Feb 23, 2026, 02:47 PM UTC

   Recovery is currently in progress, and services are being restored back to normal operation. Our teams are actively monitoring the platform to ensure stability and to confirm that all systems are fully operational. We will provide another update once recovery is complete. Thank you for your continued patience.

4. identified Feb 23, 2026, 03:17 PM UTC

   Recovery is still in progress. Our teams are actively monitoring the platform to ensure stability and to confirm that all systems are fully operational. We will provide our next update in 30 minutes, or sooner if additional information becomes available. Thank you for your continued patience.

5. identified Feb 23, 2026, 03:47 PM UTC

   Recovery is still in progress. Our teams are actively monitoring the platform to ensure stability and to confirm that all systems are fully operational. We will provide our next update in 30 minutes, or sooner if additional information becomes available. Thank you for your continued patience.

6. identified Feb 23, 2026, 04:03 PM UTC

   Account Management, Marketing and Transactional email link Tracking, and Contact Creation and Update services have now returned to normal operation. We are continuing to recover the remaining impacted services and are closely monitoring overall platform stability. We will provide our next update in 30 minutes, or sooner if additional information becomes available. Thank you for your continued patience.

7. monitoring Feb 23, 2026, 04:18 PM UTC

   Most impacted services have now returned to normal operation. We are currently observing delays in Marketing email delivery due to a temporary backlog. As the queue continues to process, delivery times are steadily improving, and newly sent emails are being processed as capacity is restored. Our teams are actively monitoring progress to ensure a full return to normal performance. We will provide our next update in 30 minutes, or sooner if additional information becomes available. Thank you for your continued patience and understanding.

8. monitoring Feb 23, 2026, 04:42 PM UTC

   All previously impacted services have returned to normal operation and are functioning as expected. We are still observing minor delays in Marketing Test email delivery due to a temporary backlog. The queue is actively being processed, and delivery times are improving as capacity continues to stabilize. Our teams are closely monitoring the situation to ensure it is fully resolved. We will provide our next update in 30 minutes, or sooner if additional information becomes available. Thank you for your continued patience and understanding.

9. monitoring Feb 23, 2026, 05:05 PM UTC

   All services are now functioning normally and working as expected. Our teams continue to monitor the platform to ensure ongoing stability and performance.

10. resolved Feb 23, 2026, 05:06 PM 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.

Read the full incident report →

Started Feb 20, 2026, 03:31 AM UTC· resolved Feb 20, 2026, 04:30 AM UTC

1. investigating Feb 20, 2026, 03:31 AM UTC

   We’ve detected an issue affecting the Public API's and the Automation Workflows Execution, 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.

2. identified Feb 20, 2026, 03:48 AM 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 Feb 20, 2026, 03:49 AM 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 Feb 20, 2026, 04:30 AM 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.

Read the full incident report →

Started Feb 20, 2026, 12:53 AM UTC· resolved Feb 20, 2026, 01:32 AM UTC

1. investigating Feb 20, 2026, 12:53 AM UTC

   We’ve detected an issue affecting the sending of the Marketing Email Campaigns and the Transactional Emails and as a result, some customers may be experiencing delays in the delivery of the emails. 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.

2. identified Feb 20, 2026, 01:07 AM UTC

   We have identified the cause of the issue affecting the sending of Marketing Email Campaigns and Transactional Emails. 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 Feb 20, 2026, 01:26 AM UTC

   We have mitigated the impact and are seeing a reduction in errors across the affected services. System performance has returned to normal levels, and pending messages are now being processed as expected. We will continue to monitor the systems closely to ensure ongoing stability. We’ll provide an update once we confirm the issue is fully resolved.

4. resolved Feb 20, 2026, 01:32 AM 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.

Read the full incident report →

Started Jan 29, 2026, 12:30 PM UTC· resolved Jan 29, 2026, 02:39 PM UTC

1. investigating Jan 29, 2026, 12:30 PM UTC

   We are currently experiencing issues affecting multiple services. Our team is assessing the impact and 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.

2. identified Jan 29, 2026, 01:02 PM 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. identified Jan 29, 2026, 01:34 PM UTC

   We have implemented a fix to mitigate the issue, and most services are now operating normally. Our team is continuing to work on restoring one remaining affected service to fully resolve the issue. We are actively monitoring all services to ensure stability while remediation continues. Thank you for your patience and understanding. We will provide the next update within 30 minutes, or sooner if additional information becomes available.

4. identified Jan 29, 2026, 02:04 PM UTC

   We are continuing to work on implementing a fix for the remaining issue and are closely monitoring the situation. Thank you for your patience and understanding. We will provide the next update within 30 minutes, or sooner if additional information becomes available.

5. monitoring Jan 29, 2026, 02:16 PM 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.

6. monitoring Jan 29, 2026, 02:26 PM UTC

   All impacted services are now operating normally. We are still observing delays in marketing email delivery and outbound webhooks for marketing email events. While we are seeing continued improvement and a reduction in processing lag, new email traffic may temporarily add to the delay. Our team is actively monitoring the situation to ensure continued recovery. We will provide the next update within 30 minutes, or sooner if additional information becomes available.

7. resolved Jan 29, 2026, 02:39 PM 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.

Read the full incident report →

Started Jan 28, 2026, 06:15 PM UTC· resolved Jan 28, 2026, 07:23 PM UTC

1. investigating Jan 28, 2026, 06:15 PM UTC

   We’ve detected an issue affecting our Transactional SMS API V3 endpoint, and as a result, some cutomers 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.

2. investigating Jan 28, 2026, 06:44 PM UTC

   We are continuing to investigate the issue to identify the root cause. Our engineering team is actively working on it, and we will provide an update within the next 30 minutes or sooner as more information becomes available. Thank you for your patience and understanding.

3. identified Jan 28, 2026, 07:14 PM 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. monitoring Jan 28, 2026, 07:17 PM 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 Jan 28, 2026, 07:23 PM 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.

Read the full incident report →

Started Jan 19, 2026, 11:19 AM UTC· resolved Jan 19, 2026, 11:28 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Jan 15, 2026, 10:58 AM UTC· resolved Jan 15, 2026, 11:16 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Jan 13, 2026, 04:40 PM UTC· resolved Jan 13, 2026, 05:17 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Jan 07, 2026, 03:46 PM UTC· resolved Jan 07, 2026, 03:54 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Jan 07, 2026, 08:23 AM UTC· resolved Jan 07, 2026, 09:12 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Dec 18, 2025, 10:34 AM UTC· resolved Dec 19, 2025, 10:33 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Dec 12, 2025, 06:49 AM UTC· resolved Dec 12, 2025, 06:58 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Nov 27, 2025, 01:19 PM UTC· resolved Nov 27, 2025, 01:29 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Nov 26, 2025, 01:48 PM UTC· resolved Nov 26, 2025, 02:52 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →