Resolved after 4 hours 45 minutes, affecting Heap Connect, on February 12, 2026.
We have deployed a fix and are beginning to catchup delayed environments. We will post an update in two hours, or resolve the incident if all environments have recovered.
Affected components
Update timeline
- identified Feb 12, 2026, 06:13 PM UTC
Our engineering team has identified the root cause of the delayed syncs and is working on a solution. There is no data loss. We will post an update in one hour.
- identified Feb 12, 2026, 06:13 PM UTC
We are continuing to work on a fix for this issue.
- monitoring Feb 12, 2026, 06:45 PM UTC
We have deployed a fix and are beginning to catchup delayed environments. We will post an update in two hours, or resolve the incident if all environments have recovered.
- identified Feb 12, 2026, 08:29 PM UTC
We have identified another issue causing sync delays and are working on a solution.
- monitoring Feb 12, 2026, 08:58 PM UTC
We have deployed a fix and are beginning to catchup delayed environments. We will post an update in two hours, or resolve the incident if all environments have recovered.
- resolved Feb 12, 2026, 10:58 PM UTC
This incident has been resolved.
Your product runs on more than Heap
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services