Etleap Outage History

Etleap is up right now

Etleap had 49 outages in the last 2 years totaling 67h 38m of downtime — averaging 2 incidents per month.

There were 49 Etleap outages since March 13, 2025 totaling 67h 38m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.etleap.com

Critical June 17, 2026

Pipeline Activity Outage

Detected by Pingoru
Jun 17, 2026, 11:56 AM UTC
Resolved
Jun 17, 2026, 01:35 PM UTC
Duration
1h 39m
Affected: Pipelines
Timeline · 3 updates
  1. investigating Jun 17, 2026, 11:56 AM UTC

    We are currently investigating an issue that is causing the scheduler job to keep crashing. This is impacting Pipeline Extraction, Transformation and Loads.

  2. monitoring Jun 17, 2026, 12:48 PM UTC

    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.

  3. resolved Jun 17, 2026, 01:35 PM UTC

    All pipelines have now recovered.

Read the full incident report →

Major June 12, 2026

Facebook Ads Extractions Failing

Detected by Pingoru
Jun 12, 2026, 02:58 PM UTC
Resolved
Jun 12, 2026, 06:45 PM UTC
Duration
3h 46m
Affected: PipelinesPipelinesPipelines
Timeline · 2 updates
  1. identified Jun 12, 2026, 02:58 PM UTC

    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.

  2. resolved Jun 12, 2026, 06:45 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 11, 2026

Degraded Performance for API Sources

Detected by Pingoru
Jun 11, 2026, 01:19 PM UTC
Resolved
Jun 11, 2026, 03:39 PM UTC
Duration
2h 19m
Affected: Pipelines
Timeline · 3 updates
  1. identified Jun 11, 2026, 01:19 PM UTC

    We are currently degraded performance for API sources. This is due to contention on an internal resource, we are currently working on a workaround.

  2. monitoring Jun 11, 2026, 01:49 PM UTC

    We have implemented a workaround and are monitoring the recovery of affected pipelines

  3. resolved Jun 11, 2026, 03:39 PM UTC

    All affected pipelines have now recovered.

Read the full incident report →

Minor May 30, 2026

We are seeing increased pipeline latencies

Detected by Pingoru
May 30, 2026, 04:13 AM UTC
Resolved
May 30, 2026, 05:57 AM UTC
Duration
1h 43m
Affected: Pipelines
Timeline · 4 updates
  1. investigating May 30, 2026, 04:13 AM UTC

    We are currently investigating the issue

  2. identified May 30, 2026, 05:07 AM UTC

    We have identified the issue, and are working on a fix.

  3. monitoring May 30, 2026, 05:29 AM UTC

    We have applied the fix, and we are monitoring pipeline recovery

  4. resolved May 30, 2026, 05:57 AM UTC

    This incident has been resolved and affected pipelines have recovered.

Read the full incident report →

Major May 27, 2026

API, UI and Pipelines are currently down for Iceberg pipelines

Detected by Pingoru
May 27, 2026, 04:10 PM UTC
Resolved
May 27, 2026, 06:48 PM UTC
Duration
2h 37m
Affected: UIPipelinesAPI
Timeline · 6 updates
  1. investigating May 27, 2026, 04:10 PM UTC

    We are currently investigating an issue with our metrics service affecting pipelines in Hosted US

  2. identified May 27, 2026, 05:21 PM UTC

    We have identified the issue, and we are currently working on a resolution.

  3. identified May 27, 2026, 05:35 PM UTC

    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.

  4. identified May 27, 2026, 06:09 PM UTC

    We are continuing to work with AWS to restore the service. We'll have another update in 30 minutes, or earlier if required.

  5. monitoring May 27, 2026, 06:33 PM UTC

    The service has been recovered, and we are monitoring pipeline recovery.

  6. resolved May 27, 2026, 06:48 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 20, 2026

LinkedIn Pipeline Extraction Latencies

Detected by Pingoru
May 20, 2026, 01:48 PM UTC
Resolved
May 20, 2026, 06:38 PM UTC
Duration
4h 49m
Affected: Integrations
Timeline · 2 updates
  1. identified May 20, 2026, 01:48 PM UTC

    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.

  2. resolved May 20, 2026, 06:38 PM UTC

    The incident has been resolved.

Read the full incident report →

Critical May 6, 2026

Dbt Builds failing

Detected by Pingoru
May 06, 2026, 10:47 AM UTC
Resolved
May 06, 2026, 02:10 PM UTC
Duration
3h 23m
Affected: dbt Schedules
Timeline · 3 updates
  1. identified May 06, 2026, 10:47 AM UTC

    Dbt Builds are currently failing in our hosted US environment, we have identified the issue and are currently working on a fix.

  2. monitoring May 06, 2026, 11:08 AM UTC

    The issue has been resolved and Dbt Builds are beginning to succeed. We will continue to monitor all dbt schedules until they have recovered.

  3. resolved May 06, 2026, 02:10 PM UTC

    All Dbt Schedules have recovered

Read the full incident report →

Notice May 1, 2026

Hosted-EU increased latency for pipelines

Detected by Pingoru
May 01, 2026, 04:41 PM UTC
Resolved
May 01, 2026, 07:33 PM UTC
Duration
2h 51m
Affected: Pipelines
Timeline · 2 updates
  1. investigating May 01, 2026, 04:41 PM UTC

    We are currently seeing an decreased rate of extractions and transformations that we are investigating.

  2. resolved May 01, 2026, 07:33 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 27, 2026

Hosted-EU CDC pipelines impaired

Detected by Pingoru
Apr 27, 2026, 05:05 PM UTC
Resolved
Apr 28, 2026, 06:04 AM UTC
Duration
12h 59m
Affected: Pipelines
Timeline · 3 updates
  1. identified Apr 27, 2026, 05:05 PM UTC

    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.

  2. identified Apr 28, 2026, 12:33 AM UTC

    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.

  3. resolved Apr 28, 2026, 06:04 AM UTC

    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.

Read the full incident report →

Critical April 23, 2026

UI inaccessible and pipeline latencies in Hosted US

Detected by Pingoru
Apr 23, 2026, 10:37 AM UTC
Resolved
Apr 23, 2026, 11:05 AM UTC
Duration
28m
Affected: UIPipelines
Timeline · 3 updates
  1. identified Apr 23, 2026, 10:37 AM UTC

    The UI is currently inaccessible and pipeline activities have stopped in the Hosted US environment. We are currently addressing the issue.

  2. monitoring Apr 23, 2026, 10:38 AM UTC

    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.

  3. resolved Apr 23, 2026, 11:05 AM UTC

    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.

Read the full incident report →

Notice April 20, 2026

We are seeing an increased failure rate for extractions and transformations

Detected by Pingoru
Apr 20, 2026, 06:09 PM UTC
Resolved
Apr 20, 2026, 06:59 PM UTC
Duration
50m
Affected: Pipelines
Timeline · 2 updates
  1. monitoring Apr 20, 2026, 06:09 PM UTC

    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

  2. resolved Apr 20, 2026, 06:59 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 20, 2026

We are seeing an increased failure rate for transformations

Detected by Pingoru
Apr 20, 2026, 04:39 PM UTC
Resolved
Apr 20, 2026, 05:22 PM UTC
Duration
43m
Affected: Pipelines
Timeline · 2 updates
  1. investigating Apr 20, 2026, 04:39 PM UTC

    We are currently investigating the issue.

  2. resolved Apr 20, 2026, 05:22 PM UTC

    We have identified the cause and resolved the issue. Pipeline Extractions and Transformations are processing as normal.

Read the full incident report →

Minor April 15, 2026

X (Twitter) Ads Reports Pipelines Failing Extractions

Detected by Pingoru
Apr 15, 2026, 05:51 PM UTC
Resolved
Apr 15, 2026, 10:09 PM UTC
Duration
4h 18m
Affected: Integrations
Timeline · 2 updates
  1. identified Apr 15, 2026, 05:51 PM UTC

    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.

  2. resolved Apr 15, 2026, 10:09 PM UTC

    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

Read the full incident report →

Minor April 14, 2026

Increased pipeline latencies

Detected by Pingoru
Apr 14, 2026, 09:03 PM UTC
Resolved
Apr 14, 2026, 10:27 PM UTC
Duration
1h 24m
Affected: PipelinesPipelines
Timeline · 6 updates
  1. investigating Apr 14, 2026, 09:03 PM UTC

    We are seeing increased pipeline latencies in the EU hosted environment. We are currently investigating.

  2. investigating Apr 14, 2026, 09:32 PM UTC

    US Hosted pipelines are also affected. We are continuing to investigate the issue.

  3. identified Apr 14, 2026, 09:36 PM UTC

    We have identified the issue, and we are working towards a resolution.

  4. monitoring Apr 14, 2026, 09:54 PM UTC

    We have deployed a fix, and we monitoring the recovery

  5. monitoring Apr 14, 2026, 10:02 PM UTC

    Pipelines in the Hosted US environment have recovered; We are monitoring the recovery of pipelines in the Hosted EU environment.

  6. resolved Apr 14, 2026, 10:27 PM UTC

    This incident has been resolved, and all affected pipelines have recovered.

Read the full incident report →

Minor April 3, 2026

Increased latencies in US Hosted environment

Detected by Pingoru
Apr 03, 2026, 03:06 PM UTC
Resolved
Apr 03, 2026, 05:20 PM UTC
Duration
2h 13m
Affected: Pipelines
Timeline · 4 updates
  1. investigating Apr 03, 2026, 03:06 PM UTC

    We are observing increased pipeline latencies in the hosted US environment. We are currently investigating the issue.

  2. identified Apr 03, 2026, 03:50 PM UTC

    The issue has been identified and we are currently implementing a fix

  3. monitoring Apr 03, 2026, 04:03 PM UTC

    A workaround has been implemented and we are seeing pipeline latencies beginning to recover. We are monitoring the extractions and transformations of delayed pipelines.

  4. resolved Apr 03, 2026, 05:20 PM UTC

    This incident has been resolved, and all affected pipelines have recovered.

Read the full incident report →

Major March 12, 2026

Facebook Ads Pipeline Extraction Latencies

Detected by Pingoru
Mar 12, 2026, 11:23 AM UTC
Resolved
Mar 12, 2026, 02:01 PM UTC
Duration
2h 38m
Affected: PipelinesPipelinesPipelines
Timeline · 2 updates
  1. investigating Mar 12, 2026, 11:23 AM UTC

    We are currently experiencing extraction errors in Facebook Ads pipelines across all environments. We are currently investigating the issue.

  2. resolved Mar 12, 2026, 02:01 PM UTC

    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.

Read the full incident report →

Minor February 27, 2026

Pipeline Latencies in Hosted EU

Detected by Pingoru
Feb 27, 2026, 03:49 PM UTC
Resolved
Feb 27, 2026, 09:49 PM UTC
Duration
6h
Affected: Pipelines
Timeline · 5 updates
  1. investigating Feb 27, 2026, 03:49 PM UTC

    We are currently seeing JDBC extractions failing to start in our Hosted EU deployment. We are currently investigating the root cause of the issue.

  2. identified Feb 27, 2026, 06:10 PM UTC

    We have identified the issue, and we working on a resolution.

  3. monitoring Feb 27, 2026, 07:55 PM UTC

    We have performed mitigation actions, and we are monitoring the recovery.

  4. monitoring Feb 27, 2026, 08:27 PM UTC

    We are seeing recovery across most pipelines. We are continuing to monitor until all affected pipelines recover.

  5. resolved Feb 27, 2026, 09:49 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 25, 2026

Pipeline Latencies

Detected by Pingoru
Feb 25, 2026, 12:17 PM UTC
Resolved
Feb 25, 2026, 01:04 PM UTC
Duration
47m
Affected: PipelinesPipelinesPipelines
Timeline · 2 updates
  1. monitoring Feb 25, 2026, 12:17 PM UTC

    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

  2. resolved Feb 25, 2026, 01:04 PM UTC

    All environments have now recovered and pipeline operations should be fully operational.

Read the full incident report →

Critical January 30, 2026

Etleap US (app.etleap.com) is Not Accessible

Detected by Pingoru
Jan 30, 2026, 11:34 AM UTC
Resolved
Jan 30, 2026, 11:45 AM UTC
Duration
10m
Affected: UIPipelinesAPIEvent Streamsdbt Schedules
Timeline · 2 updates
  1. investigating Jan 30, 2026, 11:34 AM UTC

    We are currently investigating this issue.

  2. resolved Jan 30, 2026, 11:45 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical January 2, 2026

Event stream endpoints failing in hosted US

Detected by Pingoru
Jan 02, 2026, 12:22 PM UTC
Resolved
Jan 02, 2026, 01:25 PM UTC
Duration
1h 2m
Affected: Event Streams
Timeline · 4 updates
  1. investigating Jan 02, 2026, 12:22 PM UTC

    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.

  2. identified Jan 02, 2026, 12:47 PM UTC

    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.

  3. monitoring Jan 02, 2026, 01:18 PM UTC

    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.

  4. resolved Jan 02, 2026, 01:25 PM UTC

    100% of the webhook endpoint infrastructure is in a healthy state and we are seeing event stream pipelines processing data again.

Read the full incident report →

Minor December 31, 2025

Increased pipeline latency for US hosted pipelines

Detected by Pingoru
Dec 31, 2025, 08:09 AM UTC
Resolved
Dec 31, 2025, 09:09 AM UTC
Duration
59m
Affected: Pipelines
Timeline · 3 updates
  1. investigating Dec 31, 2025, 08:09 AM UTC

    We are seeing increased latencies for US hosted pipelines and are currently investigating.

  2. monitoring Dec 31, 2025, 08:19 AM UTC

    We have found the issue and deployed a fix, and we are seeing early signs of latencies improving. We will continue to monitor.

  3. resolved Dec 31, 2025, 09:09 AM UTC

    This incident has been resolved.

Read the full incident report →

Major December 22, 2025

Increased Pipeline Latencies due to Database Extractions Failing

Detected by Pingoru
Dec 22, 2025, 03:22 PM UTC
Resolved
Dec 22, 2025, 05:23 PM UTC
Duration
2h
Affected: PipelinesPipelines
Timeline · 5 updates
  1. identified Dec 22, 2025, 03:22 PM UTC

    The issue has been identified and a fix is being implemented.

  2. identified Dec 22, 2025, 03:23 PM UTC

    We are continuing to work on a fix for this issue.

  3. monitoring Dec 22, 2025, 03:37 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. 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.

  5. 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.

Read the full incident report →

Major December 18, 2025

High rate of CDC connection failures in the Hosted EU environment

Detected by Pingoru
Dec 18, 2025, 11:36 AM UTC
Resolved
Dec 18, 2025, 01:15 PM UTC
Duration
1h 38m
Affected: Pipelines
Timeline · 4 updates
  1. investigating Dec 18, 2025, 11:36 AM UTC

    We are investigating a high number of failed CDC connections in the Hosted EU environment. We are currently investigating the cause of the issue.

  2. identified Dec 18, 2025, 12:21 PM UTC

    The issue is limited to CDC connections that connect via SSH tunnels. A bad permission change caused the SSH tunnel creation to fail. We are implementing a fix for this currently.

  3. monitoring Dec 18, 2025, 12:35 PM UTC

    The permission change was made this morning as part of a regularly scheduled upgrade to the environment. The upgrade has been rolled back and we are seeing creation of SSH tunnels succeed again. We are in the process of resuming all affected CDC connections and will monitor the recovery of the connections and their pipelines.

  4. resolved Dec 18, 2025, 01:15 PM UTC

    The incident has been resolved. All affected connections are back up and operating normally.

Read the full incident report →

Major December 16, 2025

Increased rate of Snowflake load errors due to Snowflake outage

Detected by Pingoru
Dec 16, 2025, 10:36 AM UTC
Resolved
Dec 16, 2025, 04:16 PM UTC
Duration
5h 40m
Affected: PipelinesPipelinesPipelines
Timeline · 4 updates
  1. identified Dec 16, 2025, 10:36 AM UTC

    Etleap pipelines are currently failing to load to Snowflake destinations due to an outage on Snowflake's side. We are currently unable to execute the queries required to load to the destination due to this outage. Snowflake connections hosted in the following regions are affected: - us-west-2 (Oregon) - eu-west-1 (Ireland) - ap-south-1 (Mumbai) More information and further updates can be found here: https://status.snowflake.com/incidents/xdxj4klf7sc5

  2. monitoring Dec 16, 2025, 02:25 PM UTC

    We are continuing to monitor updates from Snowflake and are monitoring the affected pipelines on our side. https://status.snowflake.com/incidents/xdxj4klf7sc5

  3. monitoring Dec 16, 2025, 03:10 PM UTC

    Snowflake loads are succeeding again, and most pipelines have now recovered fully. We are continuing to monitor the last remaining pipelines and are awaiting the resolution of the incident on Snowflake's side. https://status.snowflake.com/incidents/xdxj4klf7sc5

  4. resolved Dec 16, 2025, 04:16 PM UTC

    The incident now appears to be resolved on Snowflake's side for instances deployed in AWS.

Read the full incident report →

Minor December 16, 2025

We are seeing increased pipeline latencies in our Hosted US deployment

Detected by Pingoru
Dec 16, 2025, 09:58 AM UTC
Resolved
Dec 16, 2025, 10:29 AM UTC
Duration
30m
Affected: Pipelines
Timeline · 4 updates
  1. investigating Dec 16, 2025, 09:58 AM UTC

    We are currently investigating this issue.

  2. investigating Dec 16, 2025, 09:58 AM UTC

    We are continuing to investigate this issue.

  3. monitoring Dec 16, 2025, 10:09 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Dec 16, 2025, 10:29 AM UTC

    This incident has been resolved.

Read the full incident report →