# Delayed transactional email delivery

- Provider: [Brevo](https://down.guide/providers/brevo)
- Confidence: Confirmed
- Impact: Operational
- lasted 2m
- started 2026-10-05 07:18 UTC
- Brevo states the impact was 2026-10-05 07:00 to 07:08 UTC (8m)
- id: DWN-e582b6377c
- Official page: https://status.brevo.com/incidents/01M45EV7F26Y57NHTPEM6BTACJ

## Updates from Brevo
### 2026-10-05 07:18 UTC: investigating
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 connectivity was restored — no messages were lost. Delivery latency has returned to normal.

### 2026-10-05 07:19 UTC: 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.

### 2026-10-05 07:20 UTC: 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.

From the builder: does your app depend on Brevo? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=brevo) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention Brevo.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-e582b6377c), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.