Etleap had 46 outages in the last 2 years totaling 74h 55m of downtime — averaging 1.9 incidents per month.
There were 46 Etleap outages since May 17, 2025 totaling 74h 55m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are seeing increased latencies for Facebook Ads pipelines and are currently investigating
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
We're seeing Server errors from the TikTok API as well as asynchronous reports being unable to complete in a reasonable time.
We are continuing to investigate this issue.
We are continuing to investigate this issue.
This incident has been resolved.
The hosted App UI is currently unavailable. We are currently investigating the issue
This incident has been resolved.
We're seeing increased delays in pipeline activities due to a failure on the data processing cluster. This has already been replaced and we're investigating the root cause further. Pipelines should start seeing activities run again now.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently investigating an issue that is causing the scheduler job to keep crashing. This is impacting Pipeline Extraction, Transformation and Loads.
We have resolved the issue and the scheduler is now up and running. We will continue to monitor all pipelines until they have fully recovered.
All pipelines have now recovered.
Extractions are currently failing for Facebook Ads Sources as their API is currently experiencing an outage. More information can be found on their status page https://metastatus.com/ads-manager.
This incident has been resolved.
We are currently degraded performance for API sources. This is due to contention on an internal resource, we are currently working on a workaround.
We have implemented a workaround and are monitoring the recovery of affected pipelines
All affected pipelines have now recovered.
We are currently investigating the issue
We have identified the issue, and are working on a fix.
We have applied the fix, and we are monitoring pipeline recovery
This incident has been resolved and affected pipelines have recovered.
We are currently investigating an issue with our metrics service affecting pipelines in Hosted US
We have identified the issue, and we are currently working on a resolution.
The incident is currently impacting pipelines that load data into Iceberg. Both the UI, API and Pipelines are affected by this incident. Pipelines that load into Snowflake, Redshift, Databricks Delta Lake, and S3 Data Lake are unaffected by this incident, and are processing data normally. We are identified the root cause as an AWS service that's currently down for this environment. We are currently working with AWS to restore the service. We'll provide updates every 30 minutes, or sooner if required.
We are continuing to work with AWS to restore the service. We'll have another update in 30 minutes, or earlier if required.
The service has been recovered, and we are monitoring pipeline recovery.
This incident has been resolved.
The LinkedIn source API is experiencing elevated rates of timeouts and server errors for API calls, which is causing LinkedIn pipelines to experience latency. We are monitoring the situation.
The incident has been resolved.
Dbt Builds are currently failing in our hosted US environment, we have identified the issue and are currently working on a fix.
The issue has been resolved and Dbt Builds are beginning to succeed. We will continue to monitor all dbt schedules until they have recovered.
All Dbt Schedules have recovered
We are currently seeing an decreased rate of extractions and transformations that we are investigating.
This incident has been resolved.
Some pipelines using CDC sources are partially impaired. You may see parsing errors as a result of the DMS files produced during the earlier AWS outage that affected the eu-west-3 Paris region.
We have determined that the parsing errors are anomalous, i.e. that pipelines that are configured not to stop on parsing errors are unaffected by this issue. We are currently determining whether any pipelines are stopped as a result of these anomalous parsing errors.
Earlier today between approximately 10:57 UTC and 11:20 UTC, a power outage in an AWS data center caused all DMS tasks in our hosted EU environment to restart. The restart resulted in corrupted CDC files being written to S3 (zero-filled regions and partial records), as well as a small amount of data loss between the last good file and the first post-restart file. We have opened a dialog with the DMS team at AWS and are pushing for a post-mortem on their side. We have identified all potentially affected pipelines and notified the impacted customers directly with next steps. If you have not received a notification from us, your pipelines were not affected. We will be working with the DMS team to explore ways to guarantee that future power outages won't cause data integrity issues.
The UI is currently inaccessible and pipeline activities have stopped in the Hosted US environment. We are currently addressing the issue.
A workaround has been implemented while we investigate the root cause. The Etleap UI console is currently accessible again and we expect to see pipeline activities resume shortly. We are actively monitoring the situation.
The immediate issue has been resolved and a workaround is in place. The root cause has been identified and a full fix is being prioritised.
We have identified the cause and resolved the issue. Pipeline Extractions and Transformations should start processing as normal. We will continue monitoring all pipelines until they have fully recovered
This incident has been resolved.
We are currently investigating the issue.
We have identified the cause and resolved the issue. Pipeline Extractions and Transformations are processing as normal.
We are currently experiencing errors with extractions from Twitter Ad Reports in all environments. We've identified the issue to be on Twitter's API and are monitoring the situation. All report entities are currently affected.
This incident is caused by an upstream issue with X's API. We have filed a bug report [1], and notified all affected customers. We will continue to monitor until this incident is resolved on X's side. We will reach out directly to affected customers with any updates. [1]: https://devcommunity.x.com/t/api-stats-jobs-returning-empty-or-broken-data/262900
We are seeing increased pipeline latencies in the EU hosted environment. We are currently investigating.
US Hosted pipelines are also affected. We are continuing to investigate the issue.
We have identified the issue, and we are working towards a resolution.
We have deployed a fix, and we monitoring the recovery
Pipelines in the Hosted US environment have recovered; We are monitoring the recovery of pipelines in the Hosted EU environment.
This incident has been resolved, and all affected pipelines have recovered.
We are observing increased pipeline latencies in the hosted US environment. We are currently investigating the issue.
The issue has been identified and we are currently implementing a fix
A workaround has been implemented and we are seeing pipeline latencies beginning to recover. We are monitoring the extractions and transformations of delayed pipelines.
This incident has been resolved, and all affected pipelines have recovered.
We are currently experiencing extraction errors in Facebook Ads pipelines across all environments. We are currently investigating the issue.
Facebook Ads extractions were erroring because API calls were returning with bad requests. The issue on the source API has since been fixed as API requests are now succeeding. All affected pipelines have now recovered.
We are currently seeing JDBC extractions failing to start in our Hosted EU deployment. We are currently investigating the root cause of the issue.
We have identified the issue, and we working on a resolution.
We have performed mitigation actions, and we are monitoring the recovery.
We are seeing recovery across most pipelines. We are continuing to monitor until all affected pipelines recover.
This incident has been resolved.
We have identified an issue that are causing latencies in transformations being submitted. The issue has been resolved, however deployments may take some time to fully recover. We are continuing to monitor all environments until this is resolved
All environments have now recovered and pipeline operations should be fully operational.
We are currently investigating this issue.
This incident has been resolved.
The endpoints that accept webhook events for Event Stream source connections are currently down in the US hosted environment. We are not able to accept any events as a result. We are currently investigating the cause of the issue.
We have identified the root cause as an issue with Docker's package repository listing, which includes a version of containerd.io that does not exist. As the non-existent image cannot be pulled, the nodes that accept webhook events are failing to start. We are implementing a workaround to address the issue now.
A fix for the issue has been implemented and we are seeing the infrastructure recover. We are monitoring the metrics and the affected pipelines to ensure a full recovery.
100% of the webhook endpoint infrastructure is in a healthy state and we are seeing event stream pipelines processing data again.