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

We would like to inform you that as per TSOs request, the 2026 Auction Calendar has been updated on the corridor NSL.

For more details please refer to the Auction Calendar on our webpage http://www.jao.eu/auctions#/calendar/table to find its latest version.

Please be informed that a scheduled maintenance will be performed on the Market Data API, This API is responsible for providing information to the website’s market data.

Maintenance window:
28 September, 22:15 – 29 September, 03:00 CET

During this maintenance window, the Market Data API service will be fully unavailable and unreachable. As a result, market data provided through the API will not be available during this period.

The service is expected to be restored as soon as possible.

We apologise for any inconvenience this may cause and thank you for your understanding.

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:

26-09-2026 10:00 - 11:00 400 MW

26-09-2026 11:00 - 12:00 400 MW

26-09-2026 12:00 - 13:00 400 MW

26-09-2026 13:00 - 14:00 400 MW

26-09-2026 14:00 - 15:00 400 MW

26-09-2026 15:00 - 16:00 400 MW

26-09-2026 16:00 - 17:00 400 MW

5. Amount of LTTR remaining after curtailment:

26-09-2026 10:00 - 11:00 0 MW

26-09-2026 11:00 - 12:00 0 MW

26-09-2026 12:00 - 13:00 0 MW

26-09-2026 13:00 - 14:00 0 MW

26-09-2026 14:00 - 15:00 0 MW

26-09-2026 15:00 - 16:00 0 MW

26-09-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

1. TSO(s)*:

TERNA

2. Identification of affected Long Term Transmission Rights:

SI-IT

3. Triggering event:

Curtailment to ensure operation remains within Operational Security Limits

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

25-09-2026 00:00 - 01:00 227 MW

25-09-2026 01:00 - 02:00 227 MW

25-09-2026 02:00 - 03:00 227 MW

25-09-2026 18:00 - 19:00 227 MW

25-09-2026 19:00 - 20:00 227 MW

25-09-2026 20:00 - 21:00 227 MW

25-09-2026 21:00 - 22:00 227 MW

25-09-2026 22:00 - 23:00 227 MW

25-09-2026 23:00 - 24:00 227 MW

5. Amount of LTTR remaining after curtailment:

25-09-2026 00:00 - 01:00 177 MW

25-09-2026 01:00 - 02:00 177 MW

25-09-2026 02:00 - 03:00 177 MW

25-09-2026 18:00 - 19:00 184 MW

25-09-2026 19:00 - 20:00 184 MW

25-09-2026 20:00 - 21:00 184 MW

25-09-2026 21:00 - 22:00 184 MW

25-09-2026 22:00 - 23:00 184 MW

25-09-2026 23:00 - 24:00 165 MW

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

Expected violation of operational security limits of physical transmission assets

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

1. TSO(s)*:

TERNA

2. Identification of affected Long Term Transmission Rights:

AT-IT

3. Triggering event:

Curtailment to ensure operation remains within Operational Security Limits

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

25-09-2026 18:00 - 19:00 202 MW

25-09-2026 19:00 - 20:00 202 MW

25-09-2026 20:00 - 21:00 202 MW

5. Amount of LTTR remaining after curtailment:

25-09-2026 18:00 - 19:00 154 MW

25-09-2026 19:00 - 20:00 154 MW

25-09-2026 20:00 - 21:00 154 MW

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

Expected violation of operational security limits of physical transmission assets

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 the Auction data page on JAO website is available again. We are still investigating the root cause.

1. TSO(s)*:

RTE-TSO

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:

25-09-2026 20:00 - 21:00 1119 MW

25-09-2026 21:00 - 22:00 1119 MW

5. Amount of LTTR remaining after curtailment:

25-09-2026 20:00 - 21:00 948 MW

25-09-2026 21:00 - 22:00 1057 MW

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

   25/09/2026

      20:00-21:00 Network Security

      21:00-22: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