Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Talend Cloud AWS EU Scheduled Outage: Starting Tues 26 May 21:00 CEST with expected completion Wed 27 May 01:00 CEST
Sonja_Bauernfeind
Digital Support
Digital Support

Update March 4th, 2026: added link to How to get Talend Management Console task schedules and pause and resume during a maintenance window using the API article
Updated April 24th, 2026: added impact on APIs (all down) and additional clarification on why tasks must be stopped and the impact on remote engines
Updated May 7th, 2026: added additional information on how to address Remote Engine impact
Updated May 12th, 2026: the anticipated impact for the remaining maintenance window has increased from 30 minutes to 90 minutes

Talend Cloud and Talend Management Console will undergo scheduled maintenance in MarchApril, and MayThis infrastructure modernization is a key step in unifying the Talend ecosystem with Qlik.

The alignment paves the way for a more seamless experience across both platforms. Over the coming months, you will gain access to integrated features that bridge data integration and analytics, enabling unified governance and a streamlined management experience across your entire data lifecycle.

The maintenance windows will occur per region, during off-peak hours, and are expected to have a maximum of 90 minutes of effective downtime. 

 

What is the expected impact?

A full outage of Talend Cloud and Talend Management Console for a duration of up to 90 minutes within a preplanned 4-hour window.

The following applications will not be accessible: 

  • Talend Management Console (TMC)
  • Talend Data Stewardship (TDS)
  • Talend Data Preparation (TDP)
  • Talend Data Inventory (TDC)
  • Talend Pipeline Designer (TPD)
  • Talend API Designer and Tester
  • Talend Studio
  • Talend Cloud Engines

All APIs for Talend Cloud will not be available during the outage. APIs impacted:

 

In detail:

  • Cloud engines will not be available, and executions running on Cloud Engines will be terminated.
  • Talend Studio users may be disconnected from their session, and it will not be possible to open a new Talend Studio session except in local mode.
  • Executions that are already in progress during the outage will terminate correctly except on cloud engines, but all tasks or plans scheduled to start during those periods will be skipped.
  • Skipped executions will not be tagged as failed, since they were never started. For this reason, check the execution status of your tasks and plans to ensure that all important ones are not skipped, or start them manually if necessary. See What do I need to do to prepare? further down in this blog post.
  • Static IP addresses for Cloud Engines corresponding to Disaster Recovery regions will change during maintenance. See What follow-up actions are required? further down in this blog post.

 

What do I need to do to prepare?

 

What follow-up actions are required?

  • After the maintenance window, check and monitor the execution status of tasks and plans, as well as the status of your Remote Engines.
    In some instances, Remote Engines might require a restart if marked as unavailable in the Talend Management Console or if tasks cannot be executed as expected.

    If restarting the Remote Engine does not resolve the complication, follow the pairing instructions in Pairing Remote Engines using a dedicated web service to reset the key and re-pair the Remote Engine.

    If your Remote Engine Gen2 is unavailable or cannot execute tasks, then:

    1. Upgrade your Remote Engine Gen2 to the latest 2026-04 release: Updating the Remote Engine Gen2 when installed using the execution script)
    2. And re-establish the pairing: Re-establish the pairing of Remote Engine Gen2

  • If you use a predefined static IP on Cloud Engine, you will need to allow the new Disaster Recovery Region's IP addresses, which will have changed at this point. While this does not immediately affect production, it will impact any potential Disaster Recovery process.

    After the maintenance window, check your static IPs (Disaster Recovery) as documented in Using predefined static IP addresses for execution containers and update your firewalls accordingly.

    No change is required for the active region's IP addresses. They will be migrated and will work as of today, ensuring no production interruption.

 

When will the maintenance take place?

Each region will undergo maintenance for 4 hours during off-peak hours, with a maximum of 90 minutes of effective downtime.

 

Region Maintenance Start Maintenance End
Talend Cloud - AWS - Asia Pacific (Sydney)

au.cloud.talend.com


Wednesday 25 March 2026
 
22:00 AEDT (Sydney)

UTC: 25/03/26 - 11:00


Thursday 26 March 2026
 
02:00 AEDT (Sydney)

UTC: 25/03/26 - 15:00

Talend Cloud - AWS - Asia Pacific (Tokyo)

ap.cloud.talend.com


Monday 20 April
2026 
22:00 JST (Tokyo)

UTC: 20/04/26 - 13:00


Tuesday 21 April
2026 
02:00 JST (Tokyo)

UTC: 20/04/26 - 17:00

Talend Cloud - AWS - US East (N. Virginia)

us.cloud.talend.com


Monday 27 April 2026
 
02:00 EDT

UTC: 27/04/26 - 6:00


Monday 27 April
2026 
06:00 EDT

UTC: 27/04/26 - 10:00

Talend Cloud - AWS - Europe (Frankfurt)

eu.cloud.talend.com


Tuesday 26 May
2026 
21:00 CEST

UTC: 26/05/26 - 19:00


Wednesday 27 May
2026 
01:00 CEST

UTC: 26/05/26 - 23:00

To identify which region your tenant is affected by, cross-reference Accessing Talend Cloud applications.

To track further updates during the scheduled Qlik Cloud Maintenance, please visit our Qlik Cloud Status page. This blog post will be updated with additional information where necessary. 

 

Thank you for choosing Qlik,
Qlik Support

26 Comments
Sonja_Bauernfeind
Digital Support
Digital Support

Hello @durantepj 

Let me reach out internally and get an answer for you.

Hello @yfujioka 通訳してくれる人を探します。(Google Translate used)

All the best,
Sonja

0 Likes
661 Views
Sonja_Bauernfeind
Digital Support
Digital Support

Hello @durantepj 

The APIs will be down for the announced window, meaning requests may time out.

All the best,
Sonja

0 Likes
654 Views
Sonja_Bauernfeind
Digital Support
Digital Support

@yfujioka 

Talend CloudおよびTalend Management Consoleでは、3月4月5月にメンテナンスを予定しております。
本メンテナンスは、Talend のエコシステムを Qlik と統合していくための重要なステップとして、インフラのモダナイゼーションを行うものです。

この取り組みにより、両プラットフォームをまたいだ、よりシームレスな利用体験の実現を目指しております。
今後数か月の間に、データ統合と分析をつなぐ統合機能が順次利用可能となり、データライフサイクル全体にわたって、ガバナンスの一元化と管理の効率化が可能となる予定です。

631 Views
frankk2024
Contributor
Contributor

Will this affect on-prem Remote engines?

551 Views
Ed6
Contributor III
Contributor III

We are a 24x7 operation and don't have the luxury of a 4-hour outage to our operations. We will be exploring alternative options to TMC if these kind of outages become normal.

0 Likes
428 Views
Sonja_Bauernfeind
Digital Support
Digital Support

Hello @frankk2024 

Yes, it does. We've updated the blog post to clarify the situation better. 

However, tasks triggered before the maintenance window will complete, but no new task runs will start in the remote engines. Tasks that run during the maintenance window may not have an accurate status post migration, which is why we recommend pausing.

Restart of the remote engine is more likely required if it is not turned off during maintenance.

 

419 Views
Ed6
Contributor III
Contributor III

We are at 45 minutes of outage. Is there an eta? We're determining if we need to start contingency operations.

0 Likes
399 Views
durantepj
Contributor
Contributor

Hardly understandable why Talend would not have duplication of servers to avoid such a lengthy outage window, but even with that a defined time that the actual unavailability of the TMC is needed.

We are 24/7 shop that relies on Talend for Health and Safety needs and having a "4-hour" outage isn't sustainable.

385 Views
Sonja_Bauernfeind
Digital Support
Digital Support

Hello @Ed6 @durantepj 

I fully understand your concerns and have forwarded your feedback to the relevant teams. As for the current maintenance window, stay up to date by subscribing to (or otherwise monitoring) our status page - and do not hesitate to contact support if you're looking for more direct assistance.

All the best,
Sonja

0 Likes
378 Views
Ed6
Contributor III
Contributor III

As a follow up, no updates were posted to the status page during or after the maintenance. No acknowledgement was made to the cause of the extended window. Right now, any assurances we receive from Qlik regarding maintenance windows are not something we can treat as fact. If this were an open source project, that would be understandable. But this is not.

0 Likes
209 Views