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

1. TSO(s)*:

RTE, REE

2. Identification of affected Long Term Transmission Rights:

ES-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 11:00 - 12:00 500 MW

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

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

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

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

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

5. Amount of LTTR remaining after curtailment:

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

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

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

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

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

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

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

   16/10/2026

      11:00-12:00 Dambron - Verger

      12:00-13:00 Dambron - Verger

      13:00-14:00 Dambron - Verger

      14:00-15:00 Dambron - Verger

      15:00-16:00 Dambron - Verger

      16:00-17:00 Dambron - Verger

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

1. TSO(s)*:

RTE, SWISSGRID

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:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

5. Amount of LTTR remaining after curtailment:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

   16/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

Dear Market Participants, 

We are pleased to announce the availability of Core IDCC(e) following the deployment of PUTO Release 1.7.0.
Core IDCC(e) provides market participants with the most recent flow-based capacity information for evening delivery hours, enabling more informed trading decisions closer to real-time operation.
By making the latest cross-border capacities available, this release supports a more efficient use of the European electricity grid and helps maximize market opportunities.
Kind regards,  JAO Support Team

Please be informed that the Price Spread and Congestion Income for the IBWT area for business day 14/10/2026 will be published later than planned on the PUTO platform.

We will make the information available as soon as possible.

Please be informed that the IDCC(e) data in Core ID CCR Publication Tool for business day 14/10/2026 will be published later than planned on the PUTO platform.

We will make the information available as soon as possible.

Please be informed that the IDCC(e) data in Core ID CCR Publication Tool for business day 14/10/2026 will be published later than planned on the PUTO platform.

We will make the information available as soon as possible.

Please be informed of the curtailment for IFA1 GB-FR covering the period 24th October 2026 to 26th November 2026 with an NTC of 1000 MW; from the 26th November 2026 to the 11^st of December 2026 with an NTC of 1500MW, and for the 11^st and 12nd of December 2026 with an NTC of 1500MW
 

Due to technical constraints, we will process the curtailment in the system as the relevant delivery dates approach and ensure that the requested NTC values are applied accordingly.
 

Best regards,

JAO Operation Team