Iterable: Degraded Back-end Processing Performance
Timeline of updates
- resolved
One of our messaging servers ran out of memory and needed to be upgraded, causing the queues for certain projects to be backed up. The incident is resolved.
From Iterable’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
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.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.iterable.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Iterable, started 2017-07-27 17:31 UTC, resolved after 1.4 h, 1 update(s).
- Title
- Degraded Back-end Processing Performance
- Vendor
- Iterable
- Date
- URL
- https://rewindex.com/company/iterable/incidents/5n6wq66twtnj
Iterable profileRecent Iterable incidentsAll outages on July 27, 2017Iterable in July 2017MarkdownJSON