- Detected by Pingoru
- Apr 30, 2026, 07:46 AM UTC
- Resolved
- Apr 30, 2026, 08:02 AM UTC
- Duration
- 16m
Affected: Finnish Bank eIDs (FTN)
Timeline · 2 updates
-
monitoring Apr 30, 2026, 07:54 AM UTC
An incident is currently affecting FTN- Op Our eID connection towards this 3rd party service is running but is not functioning properly as a result of their incident. We are monitoring their progression towards resolution.
-
resolved Apr 30, 2026, 01:19 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 29, 2026, 08:00 PM UTC
- Resolved
- Apr 29, 2026, 08:43 PM UTC
- Duration
- 43m
Affected: DigiDDigiD CombiConnect
Timeline · 3 updates
-
monitoring Apr 29, 2026, 08:21 PM UTC
An incident is currently affecting DigiD Our eID connection towards this 3rd party service is running but is not functioning properly as a result of their incident. We are monitoring their progression towards resolution.
-
monitoring Apr 29, 2026, 08:27 PM UTC
We are continuing to monitor for any further issues.
-
resolved Apr 29, 2026, 08:43 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 28, 2026, 01:32 PM UTC
- Resolved
- Apr 28, 2026, 02:25 PM UTC
- Duration
- 52m
Affected: DigiDDigiD CombiConnect
Timeline · 3 updates
-
monitoring Apr 28, 2026, 01:32 PM UTC
An incident is currently affecting DigID. Our eID connection towards this 3rd party service is running but is not functioning properly as a result of their incident. We are monitoring their progression towards resolution.
-
monitoring Apr 28, 2026, 01:55 PM UTC
DigID has returned to normal traffic. DigID CombiConnect still shows degraded performance. We are continuing to monitor for further issues.
-
resolved Apr 28, 2026, 02:25 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 26, 2026, 11:40 AM UTC
- Resolved
- Apr 26, 2026, 01:09 PM UTC
- Duration
- 1h 29m
Affected: eIDV Provider: Signicat PaperBankID AMLOnboarding API - eIDVOpenID ConnectDSF NorwayReuseID APIPortal and Portal APISign API v2Audkenni App.beIDEnterprise Sign APIeIDV Provider: OnfidoBrønnøysundOnboarding API - eID HubSAML 2.0DVV FinlandAssure APIUniversal APIBuypassExpress Signature APIeIDV Provider: ReadIDFolkeregisteretOnboarding API - SigningAuthentication APISPAR SwedeneIDV Provider: Signicat VideoIDDocuments GatewayInfotorgQualified Timestamps (QTSA)TrapetsMobileIDCzech Bank iDIdentity GatewayeIDV Provider: FaceTecDigiDDocumentServiceKamer Van Koophandel (KvK)PictureIDDocuments APIPasskeysPackagingServiceVideoIDSurePayDigiD CombiConnectIdentity APIData VerificationArchiveServiceeHerkenningSmileIDAssure APICreditsafeeParakstsEmail OTPWebIDDun & Bradstreet (formerly Bisnode)Estonian ID CardOpenRegisters (Kausate)SignatureID AESFinnish Bank eIDs (FTN)MobileIDSignatureID QESFreja eIDDigital Evidence ManagementSignicat Identity BrokerID-PorteniDINitsmeOwnIdPMitIDMy SignicatSignicat dashboardMobileID (OIDC)mojeIDNorwegian BankIDPersonalausweisSamleikinSithsSK Mobile-IDSmart-IDSMS OTPSPIDSwedish BankIDSuomi.fi e-identification
Timeline · 6 updates
-
investigating Apr 26, 2026, 11:51 AM UTC
We are currently observing degraded performance from our provider Google Cloud, possibly affecting services on DTP. Incident response has been initiated and we are working on determining if there is any impact.
-
investigating Apr 26, 2026, 11:54 AM UTC
We are continuing to investigate this issue.
-
investigating Apr 26, 2026, 11:57 AM UTC
We are continuing to investigate this issue.
-
investigating Apr 26, 2026, 12:24 PM UTC
We are seeing issues with several services. We are in touch with Google support, and they are investigating on their side.
-
monitoring Apr 26, 2026, 12:49 PM UTC
We see improvement and services are restored. We will continue monitoring to see if systems are stable.
-
resolved Apr 26, 2026, 01:09 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 24, 2026, 06:31 PM UTC
- Resolved
- Apr 25, 2026, 10:29 AM UTC
- Duration
- 15h 57m
Affected: Sign API v2Enterprise Sign APIExpress Signature API
Timeline · 2 updates
-
monitoring Apr 24, 2026, 06:31 PM UTC
An incident is currently affecting Norwegian BankID CSC Signing Our eID connection towards this 3rd party service is running but is not functioning properly as a result of their incident. We are monitoring their progression towards resolution.
-
resolved Apr 25, 2026, 10:29 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 24, 2026, 11:56 AM UTC
- Resolved
- Apr 27, 2026, 11:46 AM UTC
- Duration
- 2d 23h
Affected: Data Verification
Timeline · 7 updates
-
investigating Apr 24, 2026, 11:56 AM UTC
We are currently observing degraded performance with Data Verification data-source DK-CPR, affecting integrations on api.signicat.com endpoints. Incident response has been initiated and we are actively investigating the issue and working to restore normal operations.
-
investigating Apr 24, 2026, 12:31 PM UTC
We are continuing to investigate this issue.
-
investigating Apr 24, 2026, 01:20 PM UTC
We are continuing to investigate this issue in cooperation with the technicians at CPR.
-
investigating Apr 25, 2026, 10:14 AM UTC
Incident with source DK-CPR is not expected to be resolved until Monday 27th of April, due to lack of available support with the third party DK-CPR provider during the weekend.
-
investigating Apr 27, 2026, 09:31 AM UTC
Incident with source DK-CPR is still ongoing. DK-CPR technicians are working on resolving the issue as quickly as possible.
-
monitoring Apr 27, 2026, 11:02 AM UTC
A fix has been implemented, and we are currently monitoring the results.
-
resolved Apr 27, 2026, 11:46 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 24, 2026, 10:29 AM UTC
- Resolved
- Apr 24, 2026, 10:55 AM UTC
- Duration
- 26m
Affected: Portal and Portal API
Timeline · 3 updates
-
investigating Apr 24, 2026, 10:29 AM UTC
We are currently experiencing issues with the Dokobit Portal and are working on a fix.
-
monitoring Apr 24, 2026, 10:41 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Apr 24, 2026, 10:55 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 22, 2026, 03:43 PM UTC
- Resolved
- Apr 22, 2026, 04:16 PM UTC
- Duration
- 32m
Affected: eIDV Provider: Onfido
Timeline · 3 updates
-
monitoring Apr 22, 2026, 04:14 PM UTC
An incident is currently affecting Onfido Our eID connection towards this 3rd party service is running but is not functioning properly as a result of their incident. We are monitoring their progression towards resolution.
-
monitoring Apr 22, 2026, 04:16 PM UTC
The situation seems to have improved. We will continue to monitor for any further issues.
-
resolved Apr 22, 2026, 04:16 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 21, 2026, 03:16 PM UTC
- Resolved
- Apr 21, 2026, 06:39 PM UTC
- Duration
- 3h 23m
Affected: WebID
Timeline · 2 updates
-
monitoring Apr 22, 2026, 07:25 AM UTC
An incident is currently affecting WebID Our eID connection towards this 3rd party service is running but is not functioning properly as a result of their incident. We are monitoring their progression towards resolution.
-
resolved Apr 22, 2026, 07:25 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 21, 2026, 07:48 AM UTC
- Resolved
- Apr 22, 2026, 11:14 AM UTC
- Duration
- 1d 3h
Affected: Express Signature API
Timeline · 9 updates
-
investigating Apr 21, 2026, 07:48 AM UTC
We are currently observing degraded performance with no_bankid and no_bankid_netcentric on Express sign, affecting integrations on api.signicat.com and signicat.io endpoints. Incident response has been initiated and we are actively investigating the issue and working to restore normal operations.
-
investigating Apr 21, 2026, 08:59 AM UTC
We are continuing to investigate this issue.
-
investigating Apr 21, 2026, 10:46 AM UTC
We are continuing to investigate this issue.
-
investigating Apr 21, 2026, 01:16 PM UTC
We are continuing to investigate this issue.
-
identified Apr 21, 2026, 02:00 PM UTC
The issue has been identified and a fix is being implemented.
-
identified Apr 21, 2026, 05:59 PM UTC
We expect a fix for this issue to be ready tomorrow (22.04.2026) We will come back with an update at 09:00 CEST.
-
identified Apr 22, 2026, 07:25 AM UTC
We are continuing to work on a fix for this issue.
-
monitoring Apr 22, 2026, 10:43 AM UTC
A fix has been implemented and we are seeing a climb in successrate. We will continue to montior
-
resolved Apr 22, 2026, 11:14 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 20, 2026, 07:25 AM UTC
- Resolved
- Apr 20, 2026, 07:59 AM UTC
- Duration
- 34m
Affected: itsme
Timeline · 2 updates
-
monitoring Apr 20, 2026, 08:04 AM UTC
An incident is currently affecting itsme Our eID connection towards this 3rd party service is running but is not functioning properly as a result of their incident. We are monitoring their progression towards resolution.
-
resolved Apr 20, 2026, 08:04 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 16, 2026, 01:59 PM UTC
- Resolved
- Apr 16, 2026, 03:26 PM UTC
- Duration
- 1h 27m
Affected: Finnish Bank eIDs (FTN)
Timeline · 2 updates
-
monitoring Apr 16, 2026, 01:59 PM UTC
An incident is currently affecting FTN Danskebank Our eID connection towards this 3rd party service is running but is not functioning properly as a result of their incident. We are monitoring their progression towards resolution.
-
resolved Apr 16, 2026, 03:26 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 15, 2026, 03:25 PM UTC
- Resolved
- Apr 15, 2026, 05:29 PM UTC
- Duration
- 2h 3m
Affected: Sign API v2
Timeline · 4 updates
-
investigating Apr 15, 2026, 03:25 PM UTC
We are currently observing a service disruption with Sign API v2. Incident response has been initiated and we are actively investigating the issue and working to restore normal operations.
-
investigating Apr 15, 2026, 04:24 PM UTC
We are continuing to investigate this issue.
-
monitoring Apr 15, 2026, 04:55 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Apr 15, 2026, 05:29 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 15, 2026, 10:22 AM UTC
- Resolved
- Apr 15, 2026, 11:03 AM UTC
- Duration
- 40m
Affected: eHerkenning
Timeline · 2 updates
-
monitoring Apr 15, 2026, 10:22 AM UTC
An incident is currently affecting eHerkenning KPN and Reconi Our eID connection towards this 3rd party service is running but is not functioning properly as a result of their incident. We are monitoring their progression towards resolution.
-
resolved Apr 15, 2026, 11:03 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 15, 2026, 09:40 AM UTC
- Resolved
- Apr 15, 2026, 10:20 AM UTC
- Duration
- 39m
Affected: Creditsafe
Timeline · 2 updates
-
monitoring Apr 15, 2026, 09:40 AM UTC
An incident is currently affecting Data Verification source: Creditsafe Our connection towards this 3rd party service is running but is not functioning properly as a result of their incident. We are monitoring their progression towards resolution.
-
resolved Apr 15, 2026, 10:20 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 13, 2026, 01:02 PM UTC
- Resolved
- Apr 14, 2026, 08:07 AM UTC
- Duration
- 19h 5m
Affected: Creditsafe
Timeline · 6 updates
-
investigating Apr 13, 2026, 01:02 PM UTC
We are currently observing degraded performance with Data Verification - Creditsafe, affecting integrations on api.signicat.com endpoints. Incident response has been initiated and we are actively investigating the issue and working to restore normal operations.
-
monitoring Apr 13, 2026, 01:27 PM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Apr 13, 2026, 01:54 PM UTC
We are continuing to monitor for any further issues.
-
identified Apr 13, 2026, 04:43 PM UTC
Parts of our source with Creditsafe is working, but service has not yet been fully restored. We have identified the issue and is working towards an resolution.
-
identified Apr 14, 2026, 07:53 AM UTC
Parts of our source with Creditsafe is working, but service has not yet been fully restored. We have identified the issue and is working towards an resolution.
-
resolved Apr 14, 2026, 08:07 AM UTC
The incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 13, 2026, 10:28 AM UTC
- Resolved
- Apr 13, 2026, 01:34 PM UTC
- Duration
- 3h 5m
Affected: eHerkenning
Timeline · 4 updates
-
monitoring Apr 13, 2026, 10:28 AM UTC
An incident is currently affecting eHerkenning Our eID connection towards this 3rd party service is running but is not functioning properly as a result of their incident. We are monitoring their progression towards resolution.
-
monitoring Apr 13, 2026, 11:45 AM UTC
We are continuing to monitor for any further issues.
-
monitoring Apr 13, 2026, 01:00 PM UTC
We are seeing the method having recovered. We will continue to monitor for a bit before resolving.
-
resolved Apr 13, 2026, 01:34 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 11, 2026, 09:25 PM UTC
- Resolved
- Apr 12, 2026, 09:20 AM UTC
- Duration
- 11h 54m
Affected: Finnish Bank eIDs (FTN)
Timeline · 2 updates
-
monitoring Apr 11, 2026, 09:25 PM UTC
An incident is currently affecting FTN OP Our eID connection towards this 3rd party service is running but is not functioning properly as a result of their incident. We are monitoring their progression towards resolution.
-
resolved Apr 12, 2026, 09:20 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 09, 2026, 10:01 PM UTC
- Resolved
- Apr 10, 2026, 02:27 PM UTC
- Duration
- 16h 25m
Affected: MitID
Timeline · 2 updates
-
investigating Apr 10, 2026, 03:04 PM UTC
We are currently observing degraded performance with MitID Private for Business, affecting integrations on id.signciat.com and api.signicat.com endpoints. Incident response has been initiated and we are actively investigating the issue and working to restore normal operations.
-
resolved Apr 10, 2026, 03:05 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 05, 2026, 03:17 PM UTC
- Resolved
- Apr 05, 2026, 04:51 PM UTC
- Duration
- 1h 33m
Affected: DigiDDigiD CombiConnect
Timeline · 2 updates
-
monitoring Apr 05, 2026, 03:17 PM UTC
An incident is currently affecting DigiD and DigiD app. Our eID connection towards this 3rd party service is running but is not functioning properly as a result of their incident. We are monitoring their progression towards resolution.
-
resolved Apr 05, 2026, 04:51 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 03, 2026, 08:21 AM UTC
- Resolved
- Apr 03, 2026, 10:22 AM UTC
- Duration
- 2h 1m
Affected: eHerkenning
Timeline · 4 updates
-
monitoring Apr 03, 2026, 08:21 AM UTC
An incident is currently affecting eHerkenningen Our eID connection towards this 3rd party service is running but is not functioning properly as a result of their incident. We are monitoring their progression towards resolution.
-
monitoring Apr 03, 2026, 09:49 AM UTC
We are continuing to monitor for any further issues.
-
monitoring Apr 03, 2026, 10:04 AM UTC
We are seeing a return to Operational status. We will continue to monitor to ensure stability.
-
resolved Apr 03, 2026, 10:22 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 01, 2026, 09:57 AM UTC
- Resolved
- Apr 01, 2026, 04:04 PM UTC
- Duration
- 6h 6m
Affected: Data Verification
Timeline · 5 updates
-
investigating Apr 01, 2026, 09:57 AM UTC
We are currently observing degraded performance with Data Verification data-source DK-CPR, affecting integrations on api.signicat.com endpoints. Incident response has been initiated and we are actively investigating the issue and working to restore normal operations.
-
investigating Apr 01, 2026, 09:58 AM UTC
Some of the customers are impacted due to partial outage of CPR connection and we are working with CPR support team to fix this issue.
-
identified Apr 01, 2026, 10:48 AM UTC
The issue has been identified and a fix is being implemented.
-
identified Apr 01, 2026, 12:25 PM UTC
Signicat and CPR Developer-team is working to address this issue.
-
resolved Apr 01, 2026, 04:04 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 31, 2026, 09:05 AM UTC
- Resolved
- Mar 31, 2026, 09:25 AM UTC
- Duration
- 20m
Affected: Creditsafe
Timeline · 2 updates
-
monitoring Mar 31, 2026, 09:05 AM UTC
An incident is currently affecting Data verification source: Creditsafe. Our eID connection towards this 3rd party service is running but is not functioning properly as a result of their incident. We are monitoring their progression towards resolution.
-
resolved Mar 31, 2026, 09:25 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 31, 2026, 08:30 AM UTC
- Resolved
- Mar 31, 2026, 09:10 AM UTC
- Duration
- 39m
Affected: Finnish Bank eIDs (FTN)
Timeline · 3 updates
-
monitoring Mar 31, 2026, 08:40 AM UTC
An incident is currently affecting FTN - OP Our eID connection towards this 3rd party service is running but is not functioning properly as a result of their incident. We are monitoring their progression towards resolution.
-
monitoring Mar 31, 2026, 08:45 AM UTC
We are continuing to monitor for any further issues.
-
resolved Mar 31, 2026, 09:10 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 31, 2026, 06:58 AM UTC
- Resolved
- Mar 31, 2026, 12:15 PM UTC
- Duration
- 5h 17m
Affected: MitID
Timeline · 6 updates
-
monitoring Mar 31, 2026, 06:58 AM UTC
An incident is currently affecting MitID Our eID connection towards this 3rd party service is running but is not functioning properly as a result of their incident. We are monitoring their progression towards resolution.
-
monitoring Mar 31, 2026, 07:50 AM UTC
We are continuing to monitor for any further issues.
-
monitoring Mar 31, 2026, 09:12 AM UTC
We are continuing to monitor for any further issues.
-
monitoring Mar 31, 2026, 10:45 AM UTC
We are continuing to monitor for any further issues.
-
monitoring Mar 31, 2026, 11:46 AM UTC
Issue has been resolved. We will continue to monitor.
-
resolved Mar 31, 2026, 12:15 PM UTC
This incident has been resolved.
Read the full incident report →