Etleap incident
Increased Pipeline Latencies due to Database Extractions Failing
Etleap experienced a major incident on December 22, 2025 affecting Pipelines and Pipelines, lasting 2h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Dec 22, 2025, 03:22 PM UTC
The issue has been identified and a fix is being implemented.
- identified Dec 22, 2025, 03:23 PM UTC
We are continuing to work on a fix for this issue.
- monitoring Dec 22, 2025, 03:37 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Dec 22, 2025, 04:05 PM UTC
The fix has been deployed across all environments. We are starting to see successful database extractions and expect all failing pipelines to catch up soon. We are continuing to monitor.
- resolved Dec 22, 2025, 05:23 PM UTC
This incident has been resolved - the majority of pipelines have caught up fully and the last few remaining pipelines show all extractions from database sources succeeding. The issue was an upgrade to our Spark library which is used in creating the extraction jobs for database sources. A networking configuration option in the upgraded library caused failures when submitting the extraction jobs. We reverted the upgrade to the library and have confirmed that extraction job submission is now successful. We apologise for any inconvenience caused.