# Inaccurate Delivery Counts for some ReverseETL Sync Reports

- Provider: [Segment](https://down.guide/providers/segment)
- Confidence: Confirmed
- Impact: Operational
- lasted 0m
- started 2026-01-26 19:00 UTC
- id: DWN-48e58b844e
- Official page: https://stspg.io/l20949h8mxnt

## Updates from Segment
### 2026-01-26 19:00 UTC: 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.

From the builder: does your app depend on Segment? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=segment) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention Segment.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-48e58b844e), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.