Iterable: Sends Outage/Delays Across all Mediums
Timeline of updates
- resolved
US Data Center Sends Cluster Outage
Summary: Between 12:14 AM and 12:55 AM EDT, our US Data Center's sends cluster experienced a critical outage, effectively preventing message delivery. All publishes during this period were safely backed up to our secondary queues.
Resolution: We initiated recovery efforts at 12:55 AM EDT, working through the accumulated backlog of unsent messages. During this time, sends were delayed but actively processing. By approximately 1:48 AM EDT, the backlog was cleared, and the sends cluster in the US Data Center was fully recovered.
Current Status: We are fully recovered and do not anticipate any further issues related to this incident. All messages are now being sent without delay.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
00dbb1e133247085…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Iterable, started 2025-06-06 04:15 UTC, resolved after 0 min, 1 update(s).
- Title
- Sends Outage/Delays Across all Mediums
- Vendor
- Iterable
- Date
- URL
- https://rewindex.com/company/iterable/incidents/kyls54lynldl
Iterable profileRecent Iterable incidentsAll outages on June 6, 2025Iterable in June 2025MarkdownJSON