Iterable: API instability
Timeline of updates
- resolved
From 3:49PM UTC to 4:39PM UTC, 5:47PM UTC to 6:06PM UTC, our API machines suffered instability where you may've seen high latency or increased 5XX error codes. This was caused by a sudden influx of API calls that overloaded the user database, causing a high number of threads to be in a blocked state. As a result, this impacted other API calls, like email/target that does not require a database lookup. We've disabled the API key responsible for the influx of calls and we're working on an update to the API to reduce the number of database calls for the API. We're looking into the putting our API behind the Amazon API Gateway where we can route APIs that require low latency to dedicated machines.
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: none) posted by Iterable, started 2016-11-15 22:48 UTC, resolved after 0 min, 1 update(s).
- Title
- API instability
- Vendor
- Iterable
- Date
- URL
- https://rewindex.com/company/iterable/incidents/r8g5yj2bn5bl
Iterable profileRecent Iterable incidentsAll outages on November 15, 2016Iterable in November 2016MarkdownJSON