Brevo experienced a minor incident on January 28, 2026 affecting Messaging API, lasting —. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jan 28, 2026, 06:15 PM UTC
Status: Investigating 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. Affected components Messaging API (Degraded performance)
- investigating Jan 28, 2026, 06:44 PM UTC
Status: Investigating 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. Affected components Messaging API (Degraded performance)
- identified Jan 28, 2026, 07:14 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 Messaging API (Degraded performance)
- monitoring Jan 28, 2026, 07:17 PM UTC
Status: Monitoring 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. Affected components Messaging API (Operational)
- resolved Jan 28, 2026, 07:23 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 Messaging API (Operational)