Iterable: API ingestion delays for a subset of customers
GitHub outage, Apr 21, 2020 · 12 vendors, 14 incidents
Iterable’s incident started in the same window without naming GitHub (timing only, not evidence of a link). (timing only, posted −1 h 20 min vs GitHub’s own post)
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["GitHub<br/>posted 15:45 UTC"]:::root
h1["Within an hour<br/>4 vendors, 4 blamed GitHub<br/>v0, Vercel, Travis CI, Sentry"]:::blames
root --> h1
me["Iterable (this incident)<br/>posted −1 h 20 min"]:::me
root -.->|"same window"| meFull event: timeline, evidence and all vendors →
Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.
Timeline of updates
- resolved
We are resolving this incident as there are no further delays. Thank you for your patience as we worked through this today. Please contact us at support@iterable.com for any questions or concerns.
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).