- Detected by Pingoru
- Oct 07, 2026, 07:26 AM UTC
- Resolved
- Oct 07, 2026, 07:57 AM UTC
- Duration
- 31m
Affected: Test System
Timeline · 3 updates
-
investigating Oct 07, 2026, 07:26 AM UTC
Currently the test system is unavailable. We are currently investigating the issue.
-
investigating Oct 07, 2026, 07:30 AM UTC
As part of our investigation, we identified that the test API endpoints are still operational. The web pages on test are currently not reachable.
-
resolved Oct 07, 2026, 07:57 AM UTC
We have identifed and resolved the issue. The test environment is available again.
Read the full incident report →
- Detected by Pingoru
- Aug 07, 2026, 11:33 AM UTC
- Resolved
- Aug 07, 2026, 12:14 PM UTC
- Duration
- 41m
Affected: IT Service Desk
Timeline · 4 updates
-
investigating Aug 07, 2026, 11:33 AM UTC
We are currently experiencing an outage affecting both the IT Service Desk and the Service Desk due to an service disruption at our external provider Atlassian. As a result, no new service tickets can currently be created and existing tickets cannot be processed. This does not affect emails sent to the relevant service departments. We are monitoring the situation and are awaiting restoration of the Atlassian services. Further updates will be provided as soon as additional information becomes available.
-
investigating Aug 07, 2026, 11:41 AM UTC
The incident is still under investigation. Further information and updates from our service provider Atlassian are available on the following Statuspage: https://jira-service-management.status.atlassian.com/incidents/vp78l99g1gzx
-
monitoring Aug 07, 2026, 11:48 AM UTC
Atlassian has implemented a fix. WebID IT Service Desk and Service Desk services are currently available again. We are monitoring the situation.
-
resolved Aug 07, 2026, 12:14 PM UTC
Incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 28, 2026, 04:39 PM UTC
- Resolved
- May 28, 2026, 05:03 PM UTC
- Duration
- 24m
Affected: VideoID
Timeline · 4 updates
-
investigating May 28, 2026, 01:43 PM UTC
We are currently experiencing limited availability of the web channel. Third-party applications that have integrated the WebID MobileSDK are not affected. Our team is investigating the issue with high priority.
-
identified May 28, 2026, 04:46 PM UTC
The root cause of the incident has been identified. Our service provider is working on a solution. We'll keep you updated.
-
monitoring May 28, 2026, 04:51 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved May 28, 2026, 05:03 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 18, 2026, 09:44 AM UTC
- Resolved
- May 18, 2026, 10:11 AM UTC
- Duration
- 26m
Affected: AccountIDSignIDSignID Direct
Timeline · 3 updates
-
investigating May 18, 2026, 09:44 AM UTC
Our TSP, Namirial, has informed us about degraded performance affecting document signing. All integration partners using Namirial Signing Service may be impacted. Namirial is currently working on the issue. We will keep you updated.
-
investigating May 18, 2026, 10:10 AM UTC
We are continuing to investigate this issue.
-
resolved May 18, 2026, 10:11 AM UTC
The Problem has been solved
Read the full incident report →
- Detected by Pingoru
- Feb 11, 2026, 12:37 PM UTC
- Resolved
- Feb 12, 2026, 01:19 PM UTC
- Duration
- 1d
Affected: AccountID
Timeline · 4 updates
-
investigating Feb 11, 2026, 12:37 PM UTC
Our team is currently investigating some issues in the AccountID process . We will keep you informed about further steps and measures taken.
-
identified Feb 11, 2026, 02:27 PM UTC
All transactions can be completed regularly by the user. The confirmation of successful money transfer check is impacted. Confirmations will be delayed until the problem is solved. Transaction from the past days may have to identify through VideoID.
-
monitoring Feb 12, 2026, 10:15 AM UTC
The issue has been fixed. The WebID team continues to monitor the process.
-
resolved Feb 12, 2026, 01:19 PM UTC
Incident is resolved
Read the full incident report →
- Detected by Pingoru
- Jan 26, 2026, 09:46 AM UTC
- Resolved
- Jan 26, 2026, 10:06 AM UTC
- Duration
- 19m
Affected: AccountIDAutoID
Timeline · 3 updates
-
identified Jan 26, 2026, 09:46 AM UTC
We have identified an issue with the biometric scan for our automated product. Due to a certificate change performed by our service provider, any requests to perform biometric checks are currently failing. We are working on a solution for this issue.
-
monitoring Jan 26, 2026, 09:53 AM UTC
A fix has been applied and biometric scan is working again. We are currently monitoring our systems.
-
resolved Jan 26, 2026, 10:06 AM UTC
Implemented fix is working. The issue has been resolved. All automated products using biometric scan are working again.
Read the full incident report →
Critical November 19, 2025 - Detected by Pingoru
- Nov 19, 2025, 07:44 AM UTC
- Resolved
- Nov 19, 2025, 07:54 AM UTC
- Duration
- 10m
Affected: Test System
Timeline · 2 updates
-
investigating Nov 19, 2025, 07:44 AM UTC
Our team is currently investigating an issue. We will keep you informed about further steps and measures taken.
-
resolved Nov 19, 2025, 07:54 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 06, 2025, 07:41 AM UTC
- Resolved
- Oct 06, 2025, 11:13 AM UTC
- Duration
- 3h 31m
Affected: AccountIDAutoIDavsIDeIDSignIDSignID DirectTrueIDVideoIDVisualID
Timeline · 6 updates
-
investigating Oct 06, 2025, 07:59 AM UTC
We are currently investigating this issue.
-
identified Oct 06, 2025, 08:14 AM UTC
We have identified the issue.
-
identified Oct 06, 2025, 08:40 AM UTC
Database cluster is currently being restarted.
-
identified Oct 06, 2025, 08:46 AM UTC
Database cluster restarted. We are currently monitoring the situation to ensure correct operation.
-
monitoring Oct 06, 2025, 08:48 AM UTC
We are still monitoring the situation to ensure correct operation.
-
resolved Oct 06, 2025, 11:13 AM UTC
The database cluster returned to normal operation at 10:48 a.m. The issue is resolved. We’re sorry for any inconvenience.
Read the full incident report →
- Detected by Pingoru
- Sep 29, 2025, 06:34 AM UTC
- Resolved
- Sep 29, 2025, 08:47 AM UTC
- Duration
- 2h 12m
Affected: VideoID
Timeline · 4 updates
-
investigating Sep 29, 2025, 07:24 AM UTC
Our team is currently investigating some isolated video quality performance issues at VSC Solingen site. We will keep you informed about further steps and measures taken.
-
identified Sep 29, 2025, 08:51 AM UTC
We have identified the issue and started to fix it.
-
monitoring Sep 29, 2025, 09:08 AM UTC
During the issue, high usage of our redundant network lines by the WebID QM team temporarily caused reduced bandwidth for video calls, resulting in decreased video quality for some isolated calls. The issue was resolved by canceling requests from individual QM computers. Performance returned to normal.
-
resolved Sep 29, 2025, 09:10 AM UTC
The issue is resolved. We’re sorry for any inconvenience.
Read the full incident report →
- Detected by Pingoru
- Sep 22, 2025, 08:10 AM UTC
- Resolved
- Sep 22, 2025, 09:21 AM UTC
- Duration
- 1h 11m
Affected: VideoID
Timeline · 3 updates
-
investigating Sep 22, 2025, 08:10 AM UTC
We have noticed degraded performance for our WebID video call centers. We are currently investigating the issue.
-
monitoring Sep 22, 2025, 08:32 AM UTC
A fix has been applied. The video call centers are currently working at normal performance again. We are monitoring the systems.
-
resolved Sep 22, 2025, 09:21 AM UTC
Issue has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 01, 2025, 05:15 AM UTC
- Resolved
- Sep 01, 2025, 05:15 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Sep 01, 2025, 05:46 AM UTC
Between 07:00 and 07:15 (CEST), VideoID operations experienced a partial disruption due to an ACD server service issue affecting queue visibility. The service was restarted and normal operations were fully restored. The impact was limited to a small number of agents, while the majority of agents continued operating as expected and identifications were successfully processed throughout the entire period.
Read the full incident report →
- Detected by Pingoru
- Aug 04, 2025, 12:00 PM UTC
- Resolved
- Aug 04, 2025, 12:00 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Aug 04, 2025, 12:19 PM UTC
Due to a major local power outage in Solingen, the WebID VideoID call center had to swap to UPS support. Power outage started at 14:00 CEST and power was completely restored at 14:10 CEST. Due to the UPS support, no interruption to the WebID VideoID call center occured.
Read the full incident report →
- Detected by Pingoru
- Jul 31, 2025, 02:49 PM UTC
- Resolved
- Jul 31, 2025, 02:59 PM UTC
- Duration
- 10m
Affected: AccountIDAutoIDavsIDeIDSignIDSignID DirectTrueIDVideoIDVisualID
Timeline · 2 updates
-
monitoring Jul 31, 2025, 02:49 PM UTC
Our team has identified an issue on one of our servers. Steps have been taken to fix the problem. All services are currently running. Team is monitoring the situation
-
resolved Jul 31, 2025, 02:59 PM UTC
Incident was resolved. All services are up-and-running.
Read the full incident report →
- Detected by Pingoru
- Jul 14, 2025, 08:26 AM UTC
- Resolved
- Jul 14, 2025, 11:37 AM UTC
- Duration
- 3h 10m
Affected: VideoIDVisualID
Timeline · 4 updates
-
investigating Jul 14, 2025, 08:40 AM UTC
We are currently investigating this issue.
-
identified Jul 14, 2025, 10:14 AM UTC
Initial investigations show that both redundant Internet Lines have failed and we are already working with Telekom technicians to resolve the issue.
-
monitoring Jul 14, 2025, 10:34 AM UTC
We have successfully restored the internet connectivity on both lines. Our team is currently monitoring the traffic to ensure everything remains stable. We will continue to observe the situation and provide updates if necessary. Thank you for your patience.
-
resolved Jul 14, 2025, 11:37 AM UTC
The issue has been fully resolved. Both internet lines remain stable, and no further irregularities have been observed. VideoID and VisualID services have been fully operational again since 12:34 at Solingen Site. A Root Cause Analysis (RCA) is currently being prepared. We apologize for the inconvenience and appreciate your understanding.
Read the full incident report →
- Detected by Pingoru
- Jul 10, 2025, 05:00 PM UTC
- Resolved
- Jul 10, 2025, 05:00 PM UTC
- Duration
- —
Timeline · 2 updates
-
resolved Jul 11, 2025, 08:42 AM UTC
Between 18:45 and 19:20, users experienced degraded performance and a partial outage. Investigation showed that one of the application servers was affected. Situation was back to normal after restarting that server.
-
postmortem Jul 11, 2025, 09:01 AM UTC
Investigation showed that updated maintenance jobs were using up too much system memory. This affected the application service. After restarting the server, we reviewed those jobs and fixed the memory issue.
Read the full incident report →
- Detected by Pingoru
- Jun 23, 2025, 08:13 AM UTC
- Resolved
- Jun 23, 2025, 08:32 AM UTC
- Duration
- 18m
Affected: AccountIDAutoIDavsIDeIDSignIDSignID DirectTrueIDVideoIDVisualID
Timeline · 3 updates
-
identified Jun 23, 2025, 08:13 AM UTC
We have identified an issue and are currently applying a fix to restore full service again.
-
monitoring Jun 23, 2025, 08:18 AM UTC
A fix has been applied. All services are opperational again. We are currently monitoring our services.
-
resolved Jun 23, 2025, 08:32 AM UTC
The issue is resolved now. All services are fully functional. We’re sorry for any inconvenience.
Read the full incident report →
- Detected by Pingoru
- May 19, 2025, 10:10 AM UTC
- Resolved
- May 19, 2025, 12:47 PM UTC
- Duration
- 2h 37m
Affected: VideoID
Timeline · 7 updates
-
investigating May 19, 2025, 11:19 AM UTC
Our team is currently investigating an issue. We will keep you informed about further steps and measures taken.
-
investigating May 19, 2025, 11:27 AM UTC
The VideoID service is currently operational without any anomalies. We are investigating isolated failures that currently indicate errors in the ACD.
-
investigating May 19, 2025, 11:31 AM UTC
Further investigations reveal isolated session interruptions in the ACD.
-
investigating May 19, 2025, 11:40 AM UTC
VideoID is operational, and we are currently investigating the cause of the brief interruptions in individual sessions.
-
identified May 19, 2025, 12:36 PM UTC
We have identified the issue and started to fix it.
-
monitoring May 19, 2025, 12:41 PM UTC
All redundant network components were restarted sequentially. We are currently monitoring the systems to ensure their continued correct operation.
-
resolved May 19, 2025, 12:47 PM UTC
The incident has been successfully resolved. As of 12:55 PM, all affected systems are fully operational again. Monitoring shows no further anomalies, and no additional actions are required at this time. During the incident, only isolated VideoID processes were impacted. Overall, continuous service operation was ensured throughout. We’re sorry for any inconvenience. Thank you for your patience and understanding.
Read the full incident report →
- Detected by Pingoru
- Apr 25, 2025, 05:00 AM UTC
- Resolved
- Apr 25, 2025, 10:19 PM UTC
- Duration
- 17h 18m
Affected: VideoID
Timeline · 4 updates
-
investigating Apr 25, 2025, 05:14 AM UTC
Our team is currently investigating an issue. We will keep you informed about further steps and measures taken.
-
identified Apr 25, 2025, 05:55 AM UTC
We have identified the issue and started to fix it. There has been an interruption in the connection between VSC Solingen and the data center.
-
monitoring Apr 25, 2025, 06:10 AM UTC
The affected route has been successfully reestablished, and all VideoID services are now fully operational again. We are currently monitoring the situation to ensure continued stability and performance. Further updates will be provided if necessary.
-
resolved Apr 25, 2025, 10:19 PM UTC
The routing issue impacting the Solingen site has been resolved. Network connectivity has been stable since the morning of April 25, 2025, and all affected routes were successfully re-established. Post-restoration monitoring has been completed without any further anomalies. No residual issues have been observed. The incident is now considered closed. We’re sorry for any inconvenience.
Read the full incident report →
- Detected by Pingoru
- Apr 23, 2025, 11:29 AM UTC
- Resolved
- Apr 23, 2025, 12:20 PM UTC
- Duration
- 51m
Affected: AccountIDAutoIDavsIDeIDSignIDSignID DirectTrueIDVideoIDVisualID
Timeline · 3 updates
-
investigating Apr 23, 2025, 11:29 AM UTC
Our team is currently investigating an issue. We will keep you informed about further steps and measures taken.
-
monitoring Apr 23, 2025, 11:34 AM UTC
Affected services were restarted. We are currently monitoring to ensure correct operation.
-
resolved Apr 23, 2025, 12:20 PM UTC
The issue is resolved. After five-minute interruption, some database services were restarted. There was no loss of data. During the outage, new transactions could not be created. We’re sorry for any inconvenience.
Read the full incident report →
- Detected by Pingoru
- Apr 17, 2025, 08:31 AM UTC
- Resolved
- Apr 17, 2025, 11:27 PM UTC
- Duration
- 14h 56m
Affected: AccountID
Timeline · 7 updates
-
investigating Apr 17, 2025, 08:31 AM UTC
Tink Germany is currently investigating a major outage for online banking and the X2SA banking interface. Our service provider Tink is currently investigating the incident. The incident has an impact to the WebID AccountID product. Updates on the incident will be published by Tink under the following URL: https://status.xs2a.com/incidents/r3d1zzm5wbq9
-
investigating Apr 17, 2025, 08:31 AM UTC
We are continuing to investigate this issue.
-
monitoring Apr 17, 2025, 08:54 AM UTC
TInk has identified and fixed the issue. The status is currently being monitored by Tink and WebID.
-
investigating Apr 17, 2025, 09:06 AM UTC
The previous fix did not solve the problem. Tink is still investigating
-
monitoring Apr 17, 2025, 10:27 AM UTC
Another fix was applied by Tink. Systems are currently being monitored by Tink and WebID
-
monitoring Apr 17, 2025, 10:45 PM UTC
Between 10:54 CET and 11:23 CET Tink has encountered a technical issue that impacted Payments products for multiple markets. The underlying root cause that caused the incident was resolved. We apologize for any problems this issue may have caused.
-
resolved Apr 17, 2025, 11:27 PM UTC
The issue is resolved. We’re sorry for any inconvenience.
Read the full incident report →
- Detected by Pingoru
- Dec 17, 2024, 11:32 AM UTC
- Resolved
- Dec 17, 2024, 04:04 PM UTC
- Duration
- 4h 32m
Affected: VideoID
Timeline · 5 updates
-
investigating Dec 17, 2024, 11:53 AM UTC
Our team is currently investigating an issue in the ACD. We will keep you informed about further steps and measures taken.
-
identified Dec 17, 2024, 12:11 PM UTC
We have identified the issue and started to fix it.
-
monitoring Dec 17, 2024, 12:13 PM UTC
A fix has been deployed. We are currently monitoring the fix to ensure the correct operation.
-
monitoring Dec 17, 2024, 01:40 PM UTC
We are continuing to monitor for any further issues.
-
resolved Dec 17, 2024, 04:18 PM UTC
We are pleased to inform you that the issue has been resolved. We apologize for any inconvenience this may have caused. Once the analysis is complete, we will provide an update on this incident with further details.
Read the full incident report →
Critical December 2, 2024 - Detected by Pingoru
- Dec 02, 2024, 03:05 PM UTC
- Resolved
- Dec 02, 2024, 05:47 PM UTC
- Duration
- 2h 42m
Affected: AccountIDAutoIDavsIDeIDSignIDSignID DirectTrueIDVideoIDVisualID
Timeline · 4 updates
Read the full incident report →