Segment: Inaccurate Delivery Counts for some ReverseETL Sync Reports
Timeline of updates
- resolved
We identified an issue where some destinations, for a subset of customers, in ReverseETL were not accurately reporting their delivery counts. We're currently backfilling the observability data, and all new runs for the affected ReverseETL should now display the correct counts.
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
ae6523043500b917…
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 Segment, started 2026-01-26 19:00 UTC, resolved after 0 min, 1 update(s).
- Title
- Inaccurate Delivery Counts for some ReverseETL Sync Reports
- Vendor
- Segment
- Date
- URL
- https://rewindex.com/company/segment/incidents/y8cjm60109vd
Segment profileRecent Segment incidentsAll outages on January 26, 2026Segment in January 2026MarkdownJSON