# Small sample of delayed or Inaccurate Data in Charts, Experiments, and Data Exports for ~.2% of developers

- Provider: [RevenueCat](https://down.guide/revenuecat)
- Level: confirmed
- Impact: Degraded
- lasted 14h 25m
- started 2026-01-24 08:24 UTC
- Charts, Scheduled Data Exports
- id: DWN-f1f386aa1e
- Official page: https://stspg.io/kgbwqqq6d6v9

## Updates from RevenueCat
### 2026-01-24 08:24 UTC: investigating
We are investigating an issue affecting our analytics pipeline that is causing delayed or inaccurate data in Charts, Experiments, and Scheduled Data Exports. Deleted records are not being properly removed from these products. We are actively working to identify the root cause and will provide an update once we have more information.

### 2026-01-24 08:31 UTC: identified
We have identified the root cause of the issue affecting Charts, Experiments, and Scheduled Data Exports. A recent configuration change was preventing deleted records from being synced correctly. We are now deploying a fix and will continue to monitor the systems.

### 2026-01-24 09:40 UTC: monitoring
We have identified and fixed the issue preventing deleted records from syncing to our analytics products. Deletes are now flowing correctly. We are processing a backlog of data to ensure Charts, Experiments, and Scheduled Data Exports reflect accurate information.

### 2026-01-24 13:13 UTC: monitoring
We have resolved an issue that was preventing some deleted records from syncing to Charts, Experiments, and Scheduled Data Exports. The fix has been deployed and data is now flowing correctly. The vast majority of customers were not impacted. We are continuing to monitor the systems

### 2026-01-24 22:49 UTC: resolved
This incident has been resolved.

---
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://sazabi.com/?utm_source=down-guide&utm_medium=markdown).
