Segment: Duplicate Google Analytics Data
Timeline of updates
- resolved
Approximately 12.7% of events were duplicated for Google Analytics server-side integrations between 4pm and 9pm Pacific time on 6/29, which will cause overall traffic numbers to be inflated. No other integrations or warehouses were affected. We've fully resolved the incident and will be following up with affected customers via email tomorrow along with a more thorough post-mortem.
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-06-30 07:44 UTC, resolved after 0 min, 1 update(s).
- Title
- Duplicate Google Analytics Data
- Vendor
- Segment
- Date
- URL
- https://rewindex.com/company/segment/incidents/rlg3y245p4b5
Segment profileRecent Segment incidentsAll outages on June 30, 2017Segment in June 2017MarkdownJSON