Etleap Outage History

The LinkedIn source API experienced elevated timeout and server error rates, causing latency issues for LinkedIn data pipelines in Etleap's integration service. The incident affected data extraction processes for approximately 4.9 hours before being resolved through monitoring and remediation efforts.

Dbt Builds were failing in Etleap's hosted US environment for 3.4 hours, preventing scheduled data transformation processes from completing successfully. The engineering team identified and resolved the underlying issue, restoring normal functionality to all Dbt schedules. All affected Dbt Builds have since recovered and are operating normally.

Etleap's Hosted-EU region experienced decreased extraction and transformation rates, causing increased latency for data pipelines. The performance degradation affected pipeline processing speeds for 2.9 hours. The incident was resolved after investigation and remediation efforts.

A power outage in an AWS data center caused all DMS tasks in Etleap's hosted EU environment to restart, resulting in corrupted CDC files and parsing errors for some pipelines using CDC sources. The incident also caused a small amount of data loss between the last good file and the first post-restart file. Etleap identified all affected pipelines, directly notified impacted customers with next steps, and is working with AWS DMS team to prevent future data integrity issues during power outages.

Etleap's Hosted US environment experienced a major outage where the UI became completely inaccessible and all pipeline activities stopped for 31 minutes. The incident affected both the user interface and data pipeline operations across the service. The issue was resolved with a workaround implementation, and the team identified the root cause for a permanent fix.

Etleap experienced an increased failure rate affecting pipeline extractions and transformations for 51 minutes. The engineering team identified and resolved the underlying cause, restoring normal processing functionality. All pipelines were monitored until full recovery was confirmed.

Etleap experienced an increased failure rate for transformations that affected pipeline operations for 45 minutes. The issue impacted the Pipelines component, preventing normal processing of extractions and transformations. The cause was identified and resolved, with all pipeline operations returning to normal functionality.

Etleap's X (Twitter) Ads Reports pipelines experienced extraction failures across all environments for 4.4 hours due to an upstream issue with X's API affecting all report entities. The company identified the root cause as being on Twitter's side, filed a bug report with X, and notified all affected customers. The incident was resolved once X fixed their API issue.

Etleap experienced increased pipeline latencies affecting both EU and US hosted environments for 1.5 hours. The issue impacted pipeline performance across both regions, with US pipelines recovering first followed by EU pipelines. The incident was resolved after the team identified the root cause and deployed a fix.

Etleap experienced increased pipeline latencies in their US hosted environment for 2.3 hours, affecting data pipeline processing speeds. The engineering team identified the root cause and implemented a workaround that restored normal pipeline performance. All affected pipelines have since recovered to normal operation.