rewindex

CompaniesSegmentIncidents

Segment: Iterable Data Latency (resolved)

No impact listedStatus: resolvedStarted Resolved (0 min)1 updatestatus.segment.com (opens in new tab)

Timeline of updates

  1. resolved

    We experienced additional latency for the Iterable integration as our queues were backed up. They have since been flushed, and data is now being delivered in real-time.

From Segment’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.segment.com (opens in new tab).

Cite this

Status incident (vendor impact label: none) posted by Segment, started 2017-02-10 17:21 UTC, resolved after 0 min, 1 update(s).

Title
Iterable Data Latency (resolved)
Vendor
Segment
Date
URL
https://rewindex.com/company/segment/incidents/t02z18d8hwgx

Segment profileRecent Segment incidentsAll outages on February 10, 2017Segment in February 2017MarkdownJSON