All Systems Operational
E-Ident
Operational
E-Ident
Operational
ID Verifier
Operational
E-Signing
Operational
E-Signing
Operational
Archive
Operational
DocArc
Operational
E-Archive
Operational
Meldingsarkiver
Operational
e-Nett
Operational
IDP’s 3rd Party Dependencies
Operational
MitID
Operational
FTN Aktia
Operational
FTN Danske Bank
Operational
FTN Nordea
Operational
FTN Oma SP
Operational
FTN OP
Operational
FTN Pop Pankki
Operational
FTN S-Pankki
Operational
FTN Mobiilivarmenne
Operational
Swedish BankID
Operational
Norwegian BankID
Operational
Smart-ID
Operational
Mobile-ID
Operational
Buypass
Operational
Ausweis
Operational
Beligan eID
Operational
ID-Rights
Operational
ID-Rights
Operational
Experian
Operational
Virre
Operational
TrustPortal
Operational
e-Consent
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Scheduled Maintenance
Belgian eID - new version of Trust1 Connector upcoming Jun 30, 2026 00:00-01:00 CEST
Trust1 had carried out a major update to Trust1Connector. You can find detailed information on blog (https://www.trust1team.com/post/trust1connecter-release-3-8-10) and in GitBook (https://t1t.gitbook.io/t1c-js-guide-v3/release-notes/v3.8.10). The blog is aimed at the less technically minded folks.
It’s important to note that a MANDATORY SDK update MUST be carried out.
The update to version 3.8.10 is also mandatory, as this is a prerequisite for supporting the upcoming changes to the Belgian eID.
It is expected that the version 3.8.10 will be published on the Distribution Server by the end of the month.
Posted on Jun 22, 2026 - 09:38 CEST
It’s important to note that a MANDATORY SDK update MUST be carried out.
The update to version 3.8.10 is also mandatory, as this is a prerequisite for supporting the upcoming changes to the Belgian eID.
It is expected that the version 3.8.10 will be published on the Distribution Server by the end of the month.
Posted on Jun 22, 2026 - 09:38 CEST
Update: Swedish BankID - UI and Flow Enhancements Jul 1, 2026 13:00-15:00 CEST
We are updating our Swedish BankID integration to deliver a more modern, streamlined user experience. This release introduces a refreshed UI design alongside optimized authentication and signing flows. The update is available in preprod. The rollout to production will happen on 01-Jul-2026. The official release notes for full visual and technical details are as below:
https://doc.ingroupe.com/developer/release-note-se_bankid-update-ui-page-and-flow
Posted on May 29, 2026 - 09:17 CEST
https://doc.ingroupe.com/developer/release-note-se_bankid-update-ui-page-and-flow
Posted on May 29, 2026 - 09:17 CEST
3rd party maintenance on MitID Denmark Jul 1, 2026 13:00-15:00 CEST
THIS NOTIFICATION APPLIES TO:
Customers using MitID Denmark (OIDC/Identity Token integration)
DESCRIPTION:
MitID Denmark will undergo a release to include the MitID transaction ID (mitid_uuid) in all returned ID tokens.
This update ensures the transaction ID is present directly in the ID token for all MitID authentication, signing flows and will also be available in userinfo endpoint. . Please follow the below release notes for more details:
https://doc.ingroupe.com/developer/inclusion-of-mitid-transaction-id-for-all-returned-id-token
CONSEQUENCE:
Customers are advised to ensure their token parsers handle the addition of the new mitid_uuid claim without issues. Ideally this should not be an issue as we are including new claim in idToken for MitID private identifications
NOTE:
Questions can be directed to support.esecurity@nets.eu
Posted on Jun 01, 2026 - 14:55 CEST
Customers using MitID Denmark (OIDC/Identity Token integration)
DESCRIPTION:
MitID Denmark will undergo a release to include the MitID transaction ID (mitid_uuid) in all returned ID tokens.
This update ensures the transaction ID is present directly in the ID token for all MitID authentication, signing flows and will also be available in userinfo endpoint. . Please follow the below release notes for more details:
https://doc.ingroupe.com/developer/inclusion-of-mitid-transaction-id-for-all-returned-id-token
CONSEQUENCE:
Customers are advised to ensure their token parsers handle the addition of the new mitid_uuid claim without issues. Ideally this should not be an issue as we are including new claim in idToken for MitID private identifications
NOTE:
Questions can be directed to support.esecurity@nets.eu
Posted on Jun 01, 2026 - 14:55 CEST
Scheduled Change: Enhanced Validation of OIDC Request Parameters Oct 1, 2026 13:00-15:00 CEST
Update -
We will be undergoing scheduled maintenance during this time.
Jun 26, 2026 - 10:55 CEST
Jun 26, 2026 - 10:55 CEST
Scheduled -
Status: Upcoming Change
We are going to enforce additional validation checks for OIDC authorization requests. As part of this update, requests that do not fully comply with the OIDC specification or contain inconsistencies between top-level request parameters and the signed request object may be rejected.
Impact
Customers using our authentication services may experience failed login or consent flows if their integrations submit invalid or non-compliant OIDC request parameters.
Action Required
We recommend that all integrators review their OIDC implementation and verify.
Expected Outcome
No impact is expected for integrations that already adhere to the documented OIDC requirements. Customers with non-compliant requests may need to update their implementation to avoid authentication failures.
Please find the release note at: https://doc.ingroupe.com/developer/more-validations-added-for-oidc-request-parameters
Please reach out to our support in case of any questions:
https://ingroupe.com/in-trust-services-support-contact-page/
Jun 25, 2026 - 14:33 CEST
We are going to enforce additional validation checks for OIDC authorization requests. As part of this update, requests that do not fully comply with the OIDC specification or contain inconsistencies between top-level request parameters and the signed request object may be rejected.
Impact
Customers using our authentication services may experience failed login or consent flows if their integrations submit invalid or non-compliant OIDC request parameters.
Action Required
We recommend that all integrators review their OIDC implementation and verify.
Expected Outcome
No impact is expected for integrations that already adhere to the documented OIDC requirements. Customers with non-compliant requests may need to update their implementation to avoid authentication failures.
Please find the release note at: https://doc.ingroupe.com/developer/more-validations-added-for-oidc-request-parameters
Please reach out to our support in case of any questions:
https://ingroupe.com/in-trust-services-support-contact-page/
Jun 25, 2026 - 14:33 CEST