Inaccurate Delivery Counts for some ReverseETL Sync Reports
Jan 26, 19:00 UTCJan 26, 19:00 UTC
Duration
0m
Impact
Informational
Root cause
Not disclosed
Segment, 90 days
11 incidents
Affected
Not listed by the vendor.
Final update
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.
Timeline
- Resolved · Jan 26, 19:00 UTC
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.
More from Segment
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 1619:40 UTC | Actions S3 is currently experience formatting issues with the delivered events | minor | 2h 10m |
| Sep 1014:28 UTC | SSO Login Issues with the Segment App | major | 1h 11m |
| Sep 318:30 UTC | Issue with Engage UI | major | 4h 11m |
| Sep 301:04 UTC | Segment App UI Issue with Profile Traits with no recent activity | minor | 21h 38m |
| Aug 1817:49 UTC | Intermittent Segment application login errors | major | 4h 13m |
| Aug 615:19 UTC | Google ads destination intermittent delivery failure | minor | 14h 44m |
Sources: vendors' own status pages, published postmortems and SEC 8-K Item 1.05 filings, read daily. Times as reported. Logos via logo.dev; trademarks belong to their owners.