Etleap Outage History

Etleap is up right now

Pingoru has recorded 51 incidents for Etleap: 41 in the last 12 months and 8 in the last 90 days.

Source: status.etleap.com

51incidents recorded
41last 12 months
8last 90 days
3 hourstypical duration
Incidents per month
048AprMayJunJulAugSepOct1
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct1%
Pingoru began tracking Etleap in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 2026723 of 720 (3%)
May 2026515 of 744 (2%)
June 2026613 of 720 (2%)
July 202600 of 744 (0%)
August 202628 of 744 (1%)
September 2026513 of 720 (2%)
October 202613 of 589 (1%)

Incidents, newest first

Minor February 25, 2026 Pipeline Latencies 47m Pipelines, Pipelines, Pipelines

Started Feb 25, 2026, 12:17 PM UTC· resolved Feb 25, 2026, 01:04 PM UTC

  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 10m UI, Pipelines, API, Event Streams and 1 more

Started Jan 30, 2026, 11:34 AM UTC· resolved Jan 30, 2026, 11:45 AM UTC

  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 1h 2m Event Streams

Started Jan 02, 2026, 12:22 PM UTC· resolved Jan 02, 2026, 01:25 PM UTC

  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 59m Pipelines

Started Dec 31, 2025, 08:09 AM UTC· resolved Dec 31, 2025, 09:09 AM UTC

  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 2h Pipelines, Pipelines

Started Dec 22, 2025, 03:22 PM UTC· resolved Dec 22, 2025, 05:23 PM UTC

  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 1h 38m Pipelines

Started Dec 18, 2025, 11:36 AM UTC· resolved Dec 18, 2025, 01:15 PM UTC

  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 5h 40m Pipelines, Pipelines, Pipelines

Started Dec 16, 2025, 10:36 AM UTC· resolved Dec 16, 2025, 04:16 PM UTC

  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 30m Pipelines

Started Dec 16, 2025, 09:58 AM UTC· resolved Dec 16, 2025, 10:29 AM UTC

  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 →

Major November 18, 2025 Hosted US Etleap UI and API are currently experiencing intermittent errors 5h 27m UI, API

Started Nov 18, 2025, 01:05 PM UTC· resolved Nov 18, 2025, 06:33 PM UTC

  1. monitoring Nov 18, 2025, 01:05 PM UTC

    This is due to the on-going Cloudflare outage. You may experience intermittent 500 and CORS errors when using the UI and API. Only the UI and API for Etleap's hosted platform in the US are affected. Pipelines and dbt schedules are all operating normally. We are monitoring the situation closely. Further updates to the Cloudflare outage can be found here: https://www.cloudflarestatus.com/

  2. resolved Nov 18, 2025, 06:33 PM UTC

    This incident has been resolved.

Read the full incident report →

Major November 12, 2025 Pipeline activities page failing to load 5h 36m UI, UI

Started Nov 12, 2025, 10:44 AM UTC· resolved Nov 12, 2025, 04:20 PM UTC

  1. investigating Nov 12, 2025, 10:44 AM UTC

    The pipeline activities page is failing to load across all environments.

  2. identified Nov 12, 2025, 12:27 PM UTC

    We have identified the issue and are currently building the fixed version.

  3. identified Nov 12, 2025, 12:32 PM UTC

    We have identified the issue and are currently building the fixed version. The front-end has reverted to an older version, so new features in the last 10 months are not accessible (e.g. DbtEditor)

  4. monitoring Nov 12, 2025, 01:54 PM UTC

    The front-end has been redeployed, we are currently checking that all affected UI functionality have been resolved.

  5. resolved Nov 12, 2025, 04:20 PM UTC

    This incident has been resolved.

Read the full incident report →

Major November 5, 2025 Extractions failing for Redshift sources 1h 32m Pipelines, Pipelines, Pipelines

Started Nov 05, 2025, 05:51 PM UTC· resolved Nov 05, 2025, 07:23 PM UTC

  1. identified Nov 05, 2025, 05:51 PM UTC

    Many extractions for Redshift sources are failing in all environments. We have identified the issue and are working on a fix.

  2. monitoring Nov 05, 2025, 07:16 PM UTC

    We have deployed the fix and have confirmed that extractions are starting to succeed for affected Redshift sources. We will continue to monitor all affected pipelines.

  3. resolved Nov 05, 2025, 07:23 PM UTC

    We have confirmed that all affected Redshift source pipelines have now recovered.

Read the full incident report →

Major October 20, 2025 Increased latency for pipelines in Hosted environment 11h 28m UI, Pipelines, Pipelines, API and 2 more

Started Oct 20, 2025, 10:15 AM UTC· resolved Oct 20, 2025, 09:43 PM UTC

  1. monitoring Oct 20, 2025, 10:15 AM UTC

    AWS Outage Operational issues – Multiple services (N. Virginia) Outage first reported Mon 20 October 07:11am UTC (12:11am PTC) Outage has started recovering Mon 20 October 09:27am UTC (02:27am PTC)

  2. monitoring Oct 20, 2025, 11:29 AM UTC

    VPCs deployed in US East (N. Virginia) also affected

  3. monitoring Oct 20, 2025, 01:15 PM UTC

    We are continuing to monitor for any further issues.

  4. monitoring Oct 20, 2025, 01:22 PM UTC

    We are continuing to monitor for any further issues.

  5. monitoring Oct 20, 2025, 01:31 PM UTC

    We are continuing to monitor for any further issues.

  6. monitoring Oct 20, 2025, 01:41 PM UTC

    We were experiencing increased errors in both the UI and API in the US hosted environment due to a credentials error caused by the on-going AWS outage. We have implemented a fix and are seeing a decreased rate of errors in both the API and UI.

  7. monitoring Oct 20, 2025, 04:35 PM UTC

    The AWS outage in US East (N. Virginia) is still ongoing. They have identified the root cause to be an internal networking issues and have throttled requests for new EC2 instances. This is currently causing potential outages to the following Etleap components: - Pipelines - may become latent as EMR may fail to scale up for increases in demand. - dbt Schedules - may become latent as EMR may fail to scale up for increases in demand. - Event Streams - may fail to read from source as the autoscaling group that serves these connections fail to provision new instances. Our AI and UI components are currently fully operational.

  8. monitoring Oct 20, 2025, 05:41 PM UTC

    We were able to recover some capacity for our Event Stream endpoint; They are currently able to receive data, however request latencies are still high. We are working to provision extra capacity.

  9. monitoring Oct 20, 2025, 05:42 PM UTC

    We are continuing to monitor for any further issues.

  10. monitoring Oct 20, 2025, 05:46 PM UTC

    We are seeing pipeline and dbt schedule latencies recovering; We are continuing to monitor the overall recovery.

  11. monitoring Oct 20, 2025, 05:55 PM UTC

    We are seeing increased connectivity issues to our event streaming endpoints due to networking issues

  12. monitoring Oct 20, 2025, 06:17 PM UTC

    We are able to provision extra capacity for our event streaming endpoints, and we are seeing a reduction in error rates; We are continuing to monitor the situation.

  13. monitoring Oct 20, 2025, 07:43 PM UTC

    Events stream ingestion has fully recovered; We are continuing to monitor pipeline recovery

  14. monitoring Oct 20, 2025, 08:13 PM UTC

    We are seeing connectivity issues affecting our streaming endpoints; We are investigating the root cause.

  15. monitoring Oct 20, 2025, 08:36 PM UTC

    We have addressed capacity and networking issues for our streaming ingest endpoints.

  16. resolved Oct 20, 2025, 09:43 PM UTC

    We are seeing most pipelines and dbt schedules have recovered. For any remaining issues, Etleap Support has reached out directly to affected customers, and we are working on addressing the last remaining issues. For private deployments, Etleap Support has reached out if any remedial steps are required.

  17. postmortem Oct 21, 2025, 09:27 PM UTC

    On October 20, 2025, between 07:13 UTC and 22:25 UTC, we experienced a disruption affecting multiple services due to the widespread outage in the AWS `us-east-1` region which we operate our US deployment out of.. # **Pipeline Operations** From 07:13 UTC to 09:21 UTC, pipeline activities were unavailable due to outages in several dependent AWS services, including DynamoDB, SQS, SNS, and Glue. Between 07:30 UTC and 08:28:48 UTC, we were unable to send SNS notifications for completed activities. Beginning at 09:21 UTC, new activities could be initiated; however, recovery was delayed as EC2 instance provisioning was throttled, limiting our ability to restore capacity promptly. Full recovery of all pipeline activities was achieved by 18:40 UTC. Throughout the course of the day, we observed certain source and destination connections either failing to be extracted from or failing to be loaded to do to their own use of AWS infrastructure. For more information, we recommend reviewing the status pages for these third parties. # **Webhook/Event Stream Services** Between 08:20 UTC and 17:35 UTC, webhook \(event stream\) endpoints were unable to receive events. This was caused by insufficient EC2 capacity and networking issues between our load balancer and EC2 targets. Recovery began at 17:35 UTC, with intermittent connectivity issues persisting until 22:25 UTC, at which point all services and capacity were fully restored. During this period, some webhook calls were responded with a 502. Depending on how the sender is configured, these may have been retried until the events were processed successfully. # **Customer Impact** During the outage, the webhook endpoints returned HTTP 502 responses. Any messages that received this response should be retried. Any SNS notifications for activities completed between 07:30 UTC and 08:28:48 UTC were not sent.

Read the full incident report →

Major August 27, 2025 We are increased latencies for some MySQL CDC pipelines 2h 23m Pipelines

Started Aug 27, 2025, 04:48 PM UTC· resolved Aug 27, 2025, 07:12 PM UTC

  1. investigating Aug 27, 2025, 04:48 PM UTC

    We are currently investigating the issue.

  2. monitoring Aug 27, 2025, 05:37 PM UTC

    We have identified the root cause and applied the fix. We are monitoring the recovery.

  3. resolved Aug 27, 2025, 07:12 PM UTC

    This incident has been resolved.

Read the full incident report →

Major August 4, 2025 Increased Rate of Extraction Errors for Facebook Ads Pipeliens 6h 8m Integrations

Started Aug 04, 2025, 04:53 PM UTC· resolved Aug 04, 2025, 11:02 PM UTC

  1. investigating Aug 04, 2025, 04:53 PM UTC

    We are seeing increased extraction error rates for Facebook Ads Pipelines. We are currently investigating.

  2. identified Aug 04, 2025, 07:04 PM UTC

    We have identified the root cause, and we are working on fix.

  3. monitoring Aug 04, 2025, 10:08 PM UTC

    We have deployed a fix, and we are currently monitoring.

  4. monitoring Aug 04, 2025, 10:20 PM UTC

    We are seeing pipelines starting to recover. We are continuing to monitor until all affected pipelines have fully recovered.

  5. resolved Aug 04, 2025, 11:02 PM UTC

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

Read the full incident report →

Major July 30, 2025 Increased latency for pipelines in Hosted EU environment 3h 44m Pipelines

Started Jul 30, 2025, 09:53 AM UTC· resolved Jul 30, 2025, 01:38 PM UTC

  1. identified Jul 30, 2025, 09:54 AM UTC

    Pipeline in the Hosted EU environment are experiencing increased latencies due to an infrastructure issue; We are implementing a fix for the issue now.

  2. monitoring Jul 30, 2025, 11:03 AM UTC

    We have addressed the issue and it has now recovered, and we are continuing to monitor the situation.

  3. resolved Jul 30, 2025, 01:38 PM UTC

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

Read the full incident report →

Minor July 18, 2025 Delayed loads in US Hosted 19m Pipelines

Started Jul 18, 2025, 01:05 PM UTC· resolved Jul 18, 2025, 01:25 PM UTC

  1. monitoring Jul 18, 2025, 01:05 PM UTC

    We are seeing delayed load activities across all pipelines in the US Hosted environment. This load delay has caused an additional hour of latency in the pipelines. We have identified the issue and implemented a fix, and are now monitoring the recovery.

  2. resolved Jul 18, 2025, 01:25 PM UTC

    All pipelines have now recovered.

Read the full incident report →

Minor July 2, 2025 Higher than usual latencies in US Hosted 7h 56m Pipelines

Started Jul 02, 2025, 05:46 AM UTC· resolved Jul 02, 2025, 01:43 PM UTC

  1. investigating Jul 02, 2025, 05:46 AM UTC

    We are seeing higher-than-usual latencies across pipelines in the US Hosted environment. We're investigating.

  2. monitoring Jul 02, 2025, 05:54 AM UTC

    We have identified the issue. A fix has been implemented, and we are seeing early signs of recovery. We are continuing to monitor.

  3. monitoring Jul 02, 2025, 08:30 AM UTC

    Many pipelines have recovered, and we are continuing to monitor.

  4. monitoring Jul 02, 2025, 12:03 PM UTC

    Most pipelines have now recovered, we expect the remaining few latent pipelines to catch up again shortly. We are continuing to monitor.

  5. resolved Jul 02, 2025, 01:43 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 26, 2025 We are increased processing times due to an infrastructure issue 1h 22m Pipelines, Pipelines, Pipelines

Started Jun 26, 2025, 06:48 PM UTC· resolved Jun 26, 2025, 08:11 PM UTC

  1. investigating Jun 26, 2025, 06:48 PM UTC

    We are currently investigating the issue.

  2. investigating Jun 26, 2025, 07:06 PM UTC

    We are continuing to investigate this issue.

  3. identified Jun 26, 2025, 07:06 PM UTC

    We have identified the root cause, and we are currently working on a fix.

  4. identified Jun 26, 2025, 07:35 PM UTC

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

  5. monitoring Jun 26, 2025, 08:00 PM UTC

    A fix has been implemented, and we are monitoring the recovery.

  6. monitoring Jun 26, 2025, 08:00 PM UTC

    We are continuing to monitor for any further issues.

  7. resolved Jun 26, 2025, 08:11 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 12, 2025 Google BigQuery and Cloud Storage connections are failing 3h 5m Integrations

Started Jun 12, 2025, 06:51 PM UTC· resolved Jun 12, 2025, 09:57 PM UTC

  1. monitoring Jun 12, 2025, 06:51 PM UTC

    Google BigQuery connections are currently down due to a global Google Cloud outage. You can monitor the situation here: https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW We'll monitor and provide updates as needed.

  2. monitoring Jun 12, 2025, 07:07 PM UTC

    Google Cloud Storage connections are impacted as well, due to the Global Cloud Outage. You can monitor the situation here: https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW We'll continue to monitor and provide updates as needed.

  3. monitoring Jun 12, 2025, 08:56 PM UTC

    We are seeing some BigQuery connections recovering across multiple accounts. We'll continue to monitor and provide updates as needed.

  4. resolved Jun 12, 2025, 09:57 PM UTC

    We are seeing affected connections and pipelines have recovered. This incident is now resolved.

Read the full incident report →

Minor June 1, 2025 Increased extraction failures 58m Pipelines

Started Jun 01, 2025, 12:32 PM UTC· resolved Jun 01, 2025, 01:31 PM UTC

  1. investigating Jun 01, 2025, 12:32 PM UTC

    We are seeing increased extraction failure rates for some database sourced pipelines. We are currently investigating.

  2. identified Jun 01, 2025, 12:46 PM UTC

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

  3. monitoring Jun 01, 2025, 01:18 PM UTC

    We have deployed a fix, and we are monitoring the recovery.

  4. resolved Jun 01, 2025, 01:31 PM UTC

    We are seeing extractions succeeding at the expected rate. This incident is now resolved, and all affected pipelines will recover shortly.

Read the full incident report →

Minor May 22, 2025 We are seeing increased pipeline latencies for EU Hosted 41m Pipelines

Started May 22, 2025, 07:25 PM UTC· resolved May 22, 2025, 08:07 PM UTC

  1. investigating May 22, 2025, 07:25 PM UTC

    We are currently investigating this issue.

  2. identified May 22, 2025, 07:30 PM UTC

    We are identified the issue to an infrastructure failure, and we are working on resolving it.

  3. monitoring May 22, 2025, 07:50 PM UTC

    The issue has been addressed, and we are currently monitoring the pipeline's recovery.

  4. resolved May 22, 2025, 08:07 PM UTC

    All pipelines have recovered.

Read the full incident report →