Key point · Article 17

Technical unavailability

When the platform is technically unavailable and the act cannot wait, the Regulation provides for alternative channels.

Start without complicating

Four practical actions.

  1. 01

    Confirm unavailability and urgency

  2. 02

    Consult the published official contacts

  3. 03

    Send by email or telephone

  4. 04

    Save confirmation and track later integration

Proof

Which should be recorded.

  • Log of unavailability
  • Message and attachments sent
  • Automatic receipt confirmation
  • Registration of integration or regularisation

Warning

Avoid common mistakes.

  • Do not use unconfirmed contacts.
  • Do not send sensitive information without adequate protection.
  • Do not postpone an urgent act without documenting the impediment.

Frequently Asked Questions

Two straight answers.

Does the email account as a valid submission?

In accordance with Article 17, it shall be deemed to be submitted at the time of receipt when the procedure for unavailability is used.

Can the information be encrypted?

Yes. The Regulation provides for the use of the PGP public key associated with the published official address.

Primary source

Regulation No. 756/2026 of 22 June

Information guide. Confirm the official text, notifications received and published technical instructions for the specific case.

Consult official act

Content and references checked on .

Continue route

Back to points of attention.

Compare the six rules and identify what requires immediate action or monitoring.

Back to six points