Rewindex

ChangesBrevoElevated error on public API

Brevo: Incident updated: Elevated error on public API

Incident updateNot classified yetChanged status.brevo.com (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what Brevo removed; blue is what they added. Muted text is unchanged context.

ChangedStatus#1
Before: investigating
After: resolved
AddedResolved time#2
Before: not present
After: 2026-10-19 15:06 UTC
AddedUpdatemonitoring#3
Before: not present
After: 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.
AddedUpdateresolved#4
Before: not present
After: 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.

Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).

Archive proof

Rewindex commits each version of an incident to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Rewindex captured this after the last checkpoint; the next run (00:41 UTC) commits it.

History of this incident

TodayMonday, October 19Mon, Oct 19

1 incident change

All Brevo changesBrevo profileMarkdownJSON