Leading service provider for Transmission System Operators (TSOs) in the European electricity market.

1. TSO(s)*:

RTE-TSO

2. Identification of affected Long Term Transmission Rights:

FR-CH

3. Triggering event:

Curtailment to ensure operation remains within Operational Security Limits

4. Affected volume in MW / hour for each concerned period:

04-10-2026 00:00 - 01:00 370 MW

04-10-2026 01:00 - 02:00 370 MW

04-10-2026 02:00 - 03:00 370 MW

04-10-2026 03:00 - 04:00 370 MW

04-10-2026 04:00 - 05:00 370 MW

04-10-2026 05:00 - 06:00 370 MW

04-10-2026 06:00 - 07:00 370 MW

04-10-2026 07:00 - 08:00 370 MW

04-10-2026 08:00 - 09:00 370 MW

04-10-2026 09:00 - 10:00 370 MW

04-10-2026 10:00 - 11:00 370 MW

04-10-2026 11:00 - 12:00 370 MW

04-10-2026 12:00 - 13:00 370 MW

04-10-2026 13:00 - 14:00 370 MW

04-10-2026 14:00 - 15:00 370 MW

04-10-2026 15:00 - 16:00 370 MW

04-10-2026 16:00 - 17:00 370 MW

04-10-2026 17:00 - 18:00 370 MW

04-10-2026 18:00 - 19:00 370 MW

04-10-2026 19:00 - 20:00 370 MW

04-10-2026 20:00 - 21:00 370 MW

04-10-2026 21:00 - 22:00 370 MW

04-10-2026 22:00 - 23:00 370 MW

04-10-2026 23:00 - 24:00 370 MW

5. Amount of LTTR remaining after curtailment:

04-10-2026 00:00 - 01:00 0 MW

04-10-2026 01:00 - 02:00 0 MW

04-10-2026 02:00 - 03:00 0 MW

04-10-2026 03:00 - 04:00 0 MW

04-10-2026 04:00 - 05:00 0 MW

04-10-2026 05:00 - 06:00 0 MW

04-10-2026 06:00 - 07:00 0 MW

04-10-2026 07:00 - 08:00 0 MW

04-10-2026 08:00 - 09:00 0 MW

04-10-2026 09:00 - 10:00 0 MW

04-10-2026 10:00 - 11:00 0 MW

04-10-2026 11:00 - 12:00 0 MW

04-10-2026 12:00 - 13:00 0 MW

04-10-2026 13:00 - 14:00 0 MW

04-10-2026 14:00 - 15:00 0 MW

04-10-2026 15:00 - 16:00 0 MW

04-10-2026 16:00 - 17:00 0 MW

04-10-2026 17:00 - 18:00 0 MW

04-10-2026 18:00 - 19:00 0 MW

04-10-2026 19:00 - 20:00 0 MW

04-10-2026 20:00 - 21:00 0 MW

04-10-2026 21:00 - 22:00 0 MW

04-10-2026 22:00 - 23:00 0 MW

04-10-2026 23:00 - 24:00 0 MW

6. Information on exact operational security limit(s) that are expected to be violated in the absence of curtailment*:

04/10/2026

      00:00-01:00 Network Security

      01:00-02:00 Network Security

      02:00-03:00 Network Security

      03:00-04:00 Network Security

      04:00-05:00 Network Security

      05:00-06:00 Network Security

      06:00-07:00 Network Security

      07:00-08:00 Network Security

      08:00-09:00 Network Security

      09:00-10:00 Network Security

      10:00-11:00 Network Security

      11:00-12:00 Network Security

      12:00-13:00 Network Security

      13:00-14:00 Network Security

      14:00-15:00 Network Security

      15:00-16:00 Network Security

      16:00-17:00 Network Security

      17:00-18:00 Network Security

      18:00-19:00 Network Security

      19:00-20:00 Network Security

      20:00-21:00 Network Security

      21:00-22:00 Network Security

      22:00-23:00 Network Security

      23:00-24:00 Network Security

7. Why alternative measures are not sufficient to avoid the expected violation of operational security limit(s)*?

The available remedial actions were assessed as insufficient or ineffective to avoid the violation of operational security limits

*According to section 57.3 of the EU HAR, this field can be filled in within 24 hours after the initial publication

1. TSO(s)*:

RNP

2. Identification of affected Long Term Transmission Rights:

IF1-GB-FR

3. Triggering event:

Curtailment to ensure operation remains within Operational Security Limits

4. Affected volume in MW / hour for each concerned period:

16-10-2026 00:00 - 01:00 1299 MW

16-10-2026 01:00 - 02:00 1299 MW

16-10-2026 02:00 - 03:00 1299 MW

16-10-2026 03:00 - 04:00 1299 MW

16-10-2026 04:00 - 05:00 1299 MW

16-10-2026 05:00 - 06:00 1299 MW

16-10-2026 06:00 - 07:00 1299 MW

16-10-2026 07:00 - 08:00 1299 MW

16-10-2026 08:00 - 09:00 1299 MW

16-10-2026 09:00 - 10:00 1299 MW

16-10-2026 10:00 - 11:00 1299 MW

16-10-2026 11:00 - 12:00 1299 MW

16-10-2026 12:00 - 13:00 1299 MW

16-10-2026 13:00 - 14:00 1299 MW

16-10-2026 14:00 - 15:00 1299 MW

16-10-2026 15:00 - 16:00 1299 MW

16-10-2026 16:00 - 17:00 1299 MW

16-10-2026 17:00 - 18:00 1299 MW

16-10-2026 18:00 - 19:00 1299 MW

16-10-2026 19:00 - 20:00 1299 MW

16-10-2026 20:00 - 21:00 1299 MW

16-10-2026 21:00 - 22:00 1299 MW

16-10-2026 22:00 - 23:00 1299 MW

16-10-2026 23:00 - 24:00 1299 MW

5. Amount of LTTR remaining after curtailment:

16-10-2026 00:00 - 01:00 957 MW

16-10-2026 01:00 - 02:00 957 MW

16-10-2026 02:00 - 03:00 957 MW

16-10-2026 03:00 - 04:00 957 MW

16-10-2026 04:00 - 05:00 957 MW

16-10-2026 05:00 - 06:00 957 MW

16-10-2026 06:00 - 07:00 957 MW

16-10-2026 07:00 - 08:00 957 MW

16-10-2026 08:00 - 09:00 957 MW

16-10-2026 09:00 - 10:00 957 MW

16-10-2026 10:00 - 11:00 957 MW

16-10-2026 11:00 - 12:00 957 MW

16-10-2026 12:00 - 13:00 957 MW

16-10-2026 13:00 - 14:00 957 MW

16-10-2026 14:00 - 15:00 957 MW

16-10-2026 15:00 - 16:00 957 MW

16-10-2026 16:00 - 17:00 957 MW

16-10-2026 17:00 - 18:00 957 MW

16-10-2026 18:00 - 19:00 957 MW

16-10-2026 19:00 - 20:00 957 MW

16-10-2026 20:00 - 21:00 957 MW

16-10-2026 21:00 - 22:00 957 MW

16-10-2026 22:00 - 23:00 957 MW

16-10-2026 23:00 - 24:00 957 MW

6. Information on exact operational security limit(s) that are expected to be violated in the absence of curtailment*:

Thermal limits

7. Why alternative measures are not sufficient to avoid the expected violation of operational security limit(s)*?

Capacity limitation due to planned maintenance

*According to section 57.3 of the EU HAR, this field can be filled in within 24 hours after the initial publication

1. TSO(s)*:

CGES

2. Identification of affected Long Term Transmission Rights:

ME-IT

3. Triggering event:

Curtailment to ensure operation remains within Operational Security Limits

4. Affected volume in MW / hour for each concerned period:

04-10-2026 09:00 - 10:00 400 MW

04-10-2026 10:00 - 11:00 400 MW

04-10-2026 11:00 - 12:00 400 MW

04-10-2026 12:00 - 13:00 400 MW

04-10-2026 13:00 - 14:00 400 MW

04-10-2026 14:00 - 15:00 400 MW

04-10-2026 15:00 - 16:00 400 MW

04-10-2026 16:00 - 17:00 400 MW

5. Amount of LTTR remaining after curtailment:

04-10-2026 09:00 - 10:00 0 MW

04-10-2026 10:00 - 11:00 0 MW

04-10-2026 11:00 - 12:00 0 MW

04-10-2026 12:00 - 13:00 0 MW

04-10-2026 13:00 - 14:00 0 MW

04-10-2026 14:00 - 15:00 0 MW

04-10-2026 15:00 - 16:00 0 MW

04-10-2026 16:00 - 17:00 0 MW

6. Information on exact operational security limit(s) that are expected to be violated in the absence of curtailment*:

HVDC Monita

7. Why alternative measures are not sufficient to avoid the expected violation of operational security limit(s)*?

During the CC process, all the remedial actions provided by the TSOs are already considered by the CCC

Please be informed that the day-ahead market coupling session is now completed

Please be aware that the publication of the preliminary SDAC Market Coupling Results is delayed until further notice.

The Market Coupling Results will be published as soon as they are available.

If needed, another delay message will be sent out.

Further information can be found in the Fallback Manual that is published on the websites of NEMO Committee and ENTSO-E.

Therefore, if relevant, we advise you to update your shadow bids at JAO eCAT platform before 14:10.

This release includes the following updates:

Improvements:

Italy North Monitoring is live

What changed:

We’ve added a dedicated monitoring filter for Italy North.

Impact:

Now you can track your data flows with precision and stay accountable without the guesswork.

Action required:

No action required.

Smart API Filtering for CNEC

What changed:

You can now filter the D-2 CNEC Information endpoint by "limiting" elements (true/false).

Impact:

It’s a small change that makes a big difference in reducing payload sizes and keeping your queries snappy.

Action required:

No action required.

API Speed Limits

What changed:

We are introducing a sensible cap on the "Take" parameter for API requests. "Take” will be limited to 100.000 starting from 15th of October.

Impact:

No more accidental million-row queries slowing down the database for everyone. Just fast and efficient data retrieval.

Action required:

You can find our best Practice Guide here to prepare to this change: Publication tool | JAO S.A. Leading service provider for TSOs (https://www.jao.eu/page-api/publication-tool)

Better Data Mapping

What changed:

We’ve mapped three additional columns (F_ref, F0core, and R_amr%) across the Final Domain Merging, Domain Splitting, and Final FB Computation pages.

Impact:

To give you the full picture.

Action required:

No action required.

Streamlined Filters

What changed:

The timestamp filter on the Border Data Overview page has been disabled where it wasn't adding value.

Impact:

Keeping your workspace clutter-free.

Action required:

No action required.

MarketGraph Insights

What changed:

We’ve investigated and fixed the Core MarketGraphs.

Impact:

To ensure data from LT-147 and LT-148 flows is actually visible when you need it.

Action required:

No action required.

Bug Fixes (if any):

The "Version 0" Logic

What was fixed:

We fixed a bug where initial "Forecasted" files (version 0) were failing if no prior version existed. Now, the system is smart enough to know that everyone has to start somewhere.

ZIP Processing Reliability

What was fixed:

Resolved an issue where the Core file processor would skip valid files inside F413 ZIP packages due to versioning confusion. Your files should now process fully and correctly.

Intraday Monitoring Sync

What was fixed:

Fixed a bug where intraday monitoring entries would stay "Pending" even after successful publication. The status lights should now accurately reflect reality.

SFTP Ingestion Fix

What was fixed:

We tracked down why some files were getting stuck in the "Success" folder without appearing on the website. Everything is now flowing through to the UI as expected.

For questions or assistance regarding these updates, please contact JAO Support Hub.

1. TSO(s)*:

National Grid and Stattnet

2. Identification of affected Long Term Transmission Rights:

NSL-GB-N2

3. Triggering event:

Curtailment to ensure operation remains within Operational Security Limits

4. Affected volume in MW / hour for each concerned period:

03-10-2026 19:00 - 20:00 50 MW

03-10-2026 20:00 - 21:00 50 MW

03-10-2026 21:00 - 22:00 50 MW

5. Amount of LTTR remaining after curtailment:

03-10-2026 19:00 - 20:00 38 MW

03-10-2026 20:00 - 21:00 0 MW

03-10-2026 21:00 - 22:00 0 MW

6. Information on exact operational security limit(s) that are expected to be violated in the absence of curtailment*:

7. Why alternative measures are not sufficient to avoid the expected violation of operational security limit(s)*?

*According to section 57.3 of the EU HAR, this field can be filled in within 24 hours after the initial publication