Resolved on February 12, 2026.
Feb 12, 14:58 PST Resolved - This incident has been resolved. Feb 12, 12:58 PST Monitoring - 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. Feb 12, 12:29 PST Identified - We have identified another issue causing sync delays and are working on a solution. Feb 12, 10:45 PST Monitoring - 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. Feb 12, 10:13 PST Update - We are continuing to work on a fix for this issue. Feb 12, 10:13 PST Identified - 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.
Update timeline
- monitoring Feb 12, 2026, 10:58 PM UTC
Feb 12, 14:58 PST Resolved - This incident has been resolved. Feb 12, 12:58 PST Monitoring - 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. Feb 12, 12:29 PST Identified - We have identified another issue causing sync delays and are working on a solution. Feb 12, 10:45 PST Monitoring - 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. Feb 12, 10:13 PST Update - We are continuing to work on a fix for this issue. Feb 12, 10:13 PST Identified - 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.
Your product runs on more than Heap.io
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