All Systems Operational

Uptime over the past 90 days. View historical uptime.
E-Ident Operational
90 days ago
99.99 % uptime
Today
E-Ident Operational
90 days ago
99.99 % uptime
Today
ID Verifier Operational
90 days ago
100.0 % uptime
Today
E-Signing Operational
90 days ago
100.0 % uptime
Today
E-Signing Operational
90 days ago
100.0 % uptime
Today
Archive Operational
90 days ago
100.0 % uptime
Today
DocArc Operational
90 days ago
100.0 % uptime
Today
E-Archive Operational
90 days ago
100.0 % uptime
Today
Meldingsarkiver Operational
90 days ago
100.0 % uptime
Today
e-Nett Operational
90 days ago
100.0 % uptime
Today
IDP’s 3rd Party Dependencies Operational
90 days ago
99.97 % uptime
Today
MitID Operational
90 days ago
99.84 % uptime
Today
FTN Aktia Operational
90 days ago
100.0 % uptime
Today
FTN Danske Bank Operational
90 days ago
100.0 % uptime
Today
FTN Nordea Operational
90 days ago
100.0 % uptime
Today
FTN Oma SP Operational
90 days ago
100.0 % uptime
Today
FTN OP Operational
90 days ago
100.0 % uptime
Today
FTN Pop Pankki Operational
90 days ago
100.0 % uptime
Today
FTN S-Pankki Operational
90 days ago
99.93 % uptime
Today
FTN Telia Operational
90 days ago
99.98 % uptime
Today
Swedish BankID Operational
90 days ago
100.0 % uptime
Today
Norwegian BankID Operational
90 days ago
99.93 % uptime
Today
Smart-ID Operational
90 days ago
100.0 % uptime
Today
Mobile-ID Operational
90 days ago
100.0 % uptime
Today
Buypass Operational
90 days ago
100.0 % uptime
Today
ID-Rights Operational
90 days ago
99.98 % uptime
Today
ID-Rights Operational
90 days ago
100.0 % uptime
Today
Experian Operational
90 days ago
99.96 % uptime
Today
Virre Operational
90 days ago
100.0 % uptime
Today
TrustPortal Operational
90 days ago
100.0 % uptime
Today
e-Consent Operational
90 days ago
100.0 % uptime
Today
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.

No incidents or maintenance related to this downtime.

Scheduled Maintenance

TLS Certificate Update for arkiv.bbs.no – Action Required by February 2, 2026 Feb 2, 2026 09:00-09:02 CET

Dear Customer,

IN Groupe will update the TLS certificate used by arkiv.bbs.no. on February 2, 2026.

Please note that the new certificate will be issued by a different Certificate Authority (CA) than the one currently in use. To ensure uninterrupted and secure communication with arkiv.bbs.no. , all customers must verify that the new issuer certificate is added to the truststore used by their systems.

The new issuer certificate can be found and downloaded here:
https://doc.ingroupe.com/developer/release-note-29-10-2025

We strongly recommend updating your truststore before February 2, 2026 to avoid any disruption in service.

If you have any questions or require assistance, please contact our support team.
Posted on Nov 05, 2025 - 09:57 CET

TLS Certificate Update for arkiv.nets.no – Action Required by February 2, 2026 Feb 2, 2026 09:00-13:00 CET

Update - Dear Customer,

IN Groupe will update the TLS certificate used by arkiv.nets.no on February 2, 2026.

Please note that the new certificate will be issued by a different Certificate Authority (CA) than the one currently in use. To ensure uninterrupted and secure communication with arkiv.nets.no, all customers must verify that the new issuer certificate is added to the truststore used by their systems.

The new issuer certificate can be found and downloaded here:
https://doc.ingroupe.com/developer/release-note-29-10-2025

We strongly recommend updating your truststore before February 2, 2026 to avoid any disruption in service.

If you have any questions or require assistance, please contact our support team.
Oct 29, 2025 - 15:19 CET
Update - We will be undergoing scheduled maintenance during this time.
Oct 29, 2025 - 15:14 CET
Scheduled - Dear Customer,

IN Groupe will update the TLS certificate used by arkiv.nets.no on February 2, 2026.

Please note that the new certificate will be issued by a different Certificate Authority (CA) than the one currently in use. To ensure uninterrupted and secure communication with arkiv.nets.no, all customers must verify that the new issuer certificate is added to the truststore used by their systems.

The new issuer certificate can be found and downloaded here:
https://doc.ingroupe.com/developer/release-note-29-10-2025

We strongly recommend updating your truststore before February 2, 2026 to avoid any disruption in service.

If you have any questions or require assistance, please contact our support team.
Oct 29, 2025 - 15:13 CET

Important Notice: Action Required for Upcoming Changes to BankID Norway by April 1, 2026 Apr 1, 2026 12:00-14:00 CEST

This message serves as an important update to the information previously shared regarding the sunset of the Norwegian BankID Signing Service and the rollout of the new BankID signing solution. We have received an extension to continue using the current BankID Server Signing service until April 1, 2026. This means that the BankID Server will remain fully operational during this period, and all services will continue to function as they do today. This extension provides InGroupe’s customers with sufficient time to implement the necessary changes on their end and ensure a smooth transition to the new signing infrastructure.

BankID has informed us that non-qualified signing certificates will be issued for transitional use until the migration to the new eSign APIs is completed. During this interim period, such certificates will be temporarily issued via the new Stø certificate authority (CA). For you this means that BankID will produce Advanced Electronic Signatures (AES) using non-qualified certificates for such cases. It is important to note that today’s AES is issued with a qualified certificate.

Please review the following changes and actions required to ensure a smooth transition.

1. Modernized User Interfaces
• BankID will discontinue support for iframe-based integrations: Customers currently using iframe must update their integrations.
• SDO format will remain supported: IN Groupe will generate SDO documents, and customers may choose between SDO or PADES formats according to their needs.

2. New Certificate Infrastructure
• BankID certificates will now be issued by Stø, replacing banks as the formal issuers.
• This transition simplifies issuance and opens new opportunities, such as enabling BankID for individuals without a Norwegian bank account.
• All BankID merchants will require new certificates. IN Groupe will manage the replacement process, although some customer involvement may be necessary.
• The Norwegian National Identity Number (NNIN) will be included in the public certificate as a custom extension, using the following Object Identifier (OID): 2.16.578.1.61.2.4

3. Migration to new BankID signing services
• A new BankID must be issued to utilize the new BankID signing service from Stø.
• New client credentials must be created, ref the above issuance of a new BankID. This BankID will have a related client that must be correctly configured by Stø upon request from IN Groupe. If a new certificate is issued, merchants will notice that their signature/seal in SDO documents is associated with a different certificate.

4. Ordering New BankIDs from Stø
• Some customers will need to new BankIDs, IN Groupe will assist customers in this.
• IN Groupe will contact individual customers as needed.
• Further instructions for other customer groups will be shared shortly.


We would like to emphasize that these changes are being implemented in line with the official guidelines and decisions issued by Stø, and as such, they fall outside of IN Groupe’s direct control. Nevertheless, please rest assured that we are fully committed to supporting you throughout this transition and will take every possible step to ensure a smooth and seamless experience.

NOTE:
Questions can be directed to support.esecurity@nets.eu
Link to dev page - https://doc.ingroupe.com/developer/new-bankid-no-signing-service
Posted on Oct 28, 2025 - 14:52 CET

Sunset of Norwegian BankID Signing Service & introducing new BankID signing solution Apr 1, 2026 12:00-14:00 CEST

Update - We will be undergoing scheduled maintenance during this time.
Dec 19, 2025 - 13:42 CET
Scheduled - THIS NOTIFICATION APPLIES TO:
Customers of E-Signing

TIMELINE FOR CHANGE:
From: 31.12.2025

DESCRIPTION:
Norwegian BankID BankAxept AS is introducing a new BankID signing service, phasing out the current signing service based on the old ‘BankID Server’ technology. The solution supports signing multiple documents simultaneously and meets the strictest EU requirements for digital signing, qualified signing. IN Groupe is currently implementing this update in collaboration with Norwegian BankID.

CONSEQUENCES:
Customers will need to request a new BankID. All customers will be contacted directly by IN Groupe’s Customer Success team. Importantly, this update will not impact the signing process; customers will continue to experience the same signing flow and receive the same signature output - SDO.

NOTE:
Questions can be directed to support.esecurity@nets.eu
May 16, 2025 - 13:43 CEST

Sunset of BankID Open B2B service Apr 1, 2026 14:10-16:10 CEST

This notification applies to customers using BankID Open B2B service.

DESCRIPTION:
BankID Open B2B service will be discontinued and replaced by BankID B2B Signing on 1st April 2026.

CONSEQUENCE:
Customers will be required to generate a key pair, submit the corresponding public key in JWK format to IN Groupe Customer Success team, and integrate towards BankID B2B Signing.

Migration Plan for the customers:
• Deadline to submit the JWK securely to IN Groupe’s Customer Success team: 15th February’ 2026
IN Groupe will request a BankID client for BankID B2B Signing service using the provided JWK. Customers will receive confirmation once the JWK has been successfully registered.

• Testing & Verification: as soon as possible
Perform test transactions using BankID B2B Signing to verify successful integration: 1st March’ 2026. Report any issues to IN Groupe’s Customer Success team for resolution.

NOTE:
Questions can be directed to support.esecurity@nets.eu.
Link to developer pages for BankID Signing B2B: https://developer.bankid.no/bankid-esign-provider/apis/b2b/v0/B2B-Bankid-Signer/
Posted on Dec 22, 2025 - 14:55 CET
Jan 10, 2026

No incidents reported today.

Jan 9, 2026

No incidents reported.

Jan 8, 2026

No incidents reported.

Jan 7, 2026
Additional Claims in BankID NO ID Tokens
Completed - The scheduled maintenance has been completed.
Jan 7, 14:00 CET
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 7, 12:00 CET
Scheduled - We would like to inform you that we are adding additional claims to the ID tokens generated for BankID NO identifications. This enhancement is designed to provide more comprehensive information and to improve integration with your systems. Please find details on additional claims below:

acr: Appended new values to the existing acr claim using comma separation. Example- urn:eident:cert:eidas:high;urn:bankid:bid;LOA=4
azp: Added as a new claim under the openid scope.
originator: Represented using the existing claim issuing_authority, available under the profile scope.
updated_at: Represented using the existing claim issue_date, available under the profile scope.

Sample ID Token After Update:
{
"sub" : "no_bankid:9578-6000-4-237729",
"birthdate" : "02.12.1921",
"amr" : [ "no_bankid" ],
"iss" : "https://www-ident-test.nets.no/oidc",
"pid" : "9578-6000-4-237729",
"no_bid_pid" : "9578-6000-4-237729",
"given_name" : "Haider",
"nonce" : "nonce22/12/2025",
"no_ssn" : "02122134760",
"ssn" : "02122134760",
"aud" : "MER2",
"acr" : "urn:eident:cert:eidas:high;urn:bankid:bid;LOA=4",
"issue_date" : "1758613431",
"ssn_issuing_country" : "NO",
"azp" : "sis_nets-bankid-current",
"issuing_authority" : "CN=BankID - TestBank1 - Bank CA 3,OU=123456789,O=TestBank1 AS,C=NO;OrginatorId=9980;OriginatorName=BINAS;OriginatorId=9980",
"name" : "Test, Haider",
"exp" : 1766401188,
"iat" : 1766400288,
"family_name" : "Test",
"jti" : "26e28a1b42184ca48e9bbb4d5a944695"
}

These changes ensure consistency while providing additional information for improved integration and compliance.

NOTE:
Questions can be directed to support.esecurity@nets.eu.
Link to developer pages for E-Ident: BankID (NO)
Dec 22, 13:58 CET
Jan 6, 2026

No incidents reported.

Jan 5, 2026

No incidents reported.

Jan 4, 2026

No incidents reported.

Jan 3, 2026

No incidents reported.

Jan 2, 2026

No incidents reported.

Jan 1, 2026

No incidents reported.

Dec 31, 2025
Traficom requirement to use digitally signed authentication request
Completed - The scheduled maintenance has been completed.
Dec 31, 12:00 CET
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Dec 31, 10:00 CET
Scheduled - This is to inform you that we have received Traficom regulation regrading requirement to use digitally signed authentication request (also called request-object in the OIDC protocol). It is described that the providers of identification broker services must require their customers to use digitally signed authentication request (the so-called request-object in the OIDC protocol).

This means that the digital signature of authentication request is verified and only approved requests are forwarded to provider of the electronic identification means.

Existing e-services must check that the authentication requests comply with the obligations of the Regulation and, if necessary, fix the implementation if the signing of identification requests has not been implemented by 31st December’ 2025.

CONSEQUENCE:
IN Groupe is already compliant with this update. We recommend our customers to ensure that the digital signature of authentication request is verified, and only approved requests are forwarded to us for electronic identification. We, therefore, request you to check that the authentication requests you are sending to us should comply with the obligations of the Regulation and, if necessary, fix this by 31 December 2025.

NOTE:
Questions can be directed to support.esecurity@nets.eu.
Link to developer pages for E-Ident: BankID (NO)
Jun 26, 15:14 CEST
Customer action needed: Update on Traficom requirement for customers on Finnish Trust Network (FTN)
Completed - The scheduled maintenance has been completed.
Dec 31, 12:00 CET
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Dec 31, 10:00 CET
Scheduled - This is to inform you that we have received an update to Traficom regulation with a new requirement affecting all customers on (Finnish Trust Network) FTN. The new requirement makes the use of signed authentication requests mandatory. The signed authentication requests is also called Signed Request Object in the OIDC specification.

Consequence for IN Groupe:
IN Groupe, as a provider of identification broker services, must require customers to use digitally signed authentication requests. The digital signature of authentication request must be verified, and only approved requests shall be accepted and forwarded to provider of the electronic identification means.

Consequence for Customers:
Customers not already complying with the obligations of the Traficom regulation must update their service accordingly. Customers must make sure all authentication requests are signed. The signature key must be submitted to IN Groupe to ensure proper configuration. The format of the key must be either i) JWK or ii) URL to JWKS, with KID if required. The update must be in place no later than 31 December 2025.

Note:
Questions can be directed to support.esecurity@nets.eu.
Link to FTN documentation: https://doc.ingroupe.com/developer/finnish-bank-id
Please note that this is an update to the notification sent earlier on 26th June' 2025.
Aug 1, 12:00 CEST
Dec 30, 2025

No incidents reported.

Dec 29, 2025

No incidents reported.

Dec 28, 2025

No incidents reported.

Dec 27, 2025

No incidents reported.

← Incident History Powered by Atlassian Statuspage