Iterable: Delayed sends from 7am to 9am ET (retro-active)
Timeline of updates
- resolved
We experienced a period of delayed sends (including proofs) as well as errors in user updates from 7am to 9am ET. The issue has been resolved. Some delayed messages may still be processing and will be sent shortly. If customers received 500 responses to API requests, they should re-try those calls.
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
79e3a655925941ed…
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 2026-02-16 15:35 UTC, resolved after -215 min, 1 update(s).
- Title
- Delayed sends from 7am to 9am ET (retro-active)
- Vendor
- Iterable
- Date
- URL
- https://rewindex.com/company/iterable/incidents/m2gj10vtmnrl
Iterable profileRecent Iterable incidentsAll outages on February 16, 2026Iterable in February 2026MarkdownJSON