Heap: Heap Connect Syncs: Possibility Of Stale Data
Affected components: Heap Connect
Timeline of updates
- monitoring
We have identified and resolved an issue affecting upstream data sources for connect syncs.
While many syncs have automatically retried, some customers may still be observing stale data.
Upcoming scheduled syncs should resolve the staleness issue, and we expect complete resolution within 24 hours. - resolved
Our monitoring shows that all syncs are still operating normally,
and no remaining customer should observe staleness issues at this time.
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
2c0b4bf9892f9a25…
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: minor) posted by Heap, started 2026-08-28 13:42 UTC, resolved after 23 h, 2 update(s).
- Title
- Heap Connect Syncs: Possibility Of Stale Data
- Vendor
- Heap
- Date
- URL
- https://rewindex.com/company/heap/incidents/8874hgg7gpcc
Heap profileRecent Heap incidentsAll outages on August 28, 2026Heap in August 2026MarkdownJSON