This incident has been resolved.
Aug 12, 14:02 CEST
A fix has been implemented and we are monitoring the results.
Aug 12, 07:36 CEST
Since Friday, we have continued to work on further network setup changes. As soon as the changes are deployed - knowing what we know now, it will be Wednesday - we will perform tests internally to reaffirm the fix of the issue. These changes shall not have any downtime, but please watch out for additional notifications on it. Rest assured, our teams are working continuously to take appropriate steps to remediate.
Aug 8, 17:06 CEST
Last evening our data center provider upgraded the firmware on one of the central network load balancers, but we did not see any big improvement. During last day, we actively provided workarounds to many impacted customers, and many can continue to operate at normal levels.
As the situation stabilized, we will maintain this status during the weekend, and will not change or update systems.
Meanwhile, we are working with our data center provider, and execute additional changes on Monday onwards to resolve the issue.
These changes shall not have any downtime, but please watch out for additional notifications on it.
Aug 5, 11:40 CEST
We are continuing to work on a fix for this issue.
Aug 4, 15:01 CEST
We were able to reproduce the issue with our API and in order to fix it, our datacenter provider will upgrade the faulty load balancer today between 21:00 and 23:59 CET. The upgrade might cause disruptions in the traffic for 1 - 3 seconds.
Aug 4, 15:00 CEST
During our investigations today we managed to narrow down the problem to one load balancer which is handling all the traffic coming from outside. Our datacenter provider will upgrade the load balancers as fast as possible in the coming 36 hours. In the meantime we are working with all of our customers who still experience the problem on implementing a temporary work-around.
Aug 3, 18:44 CEST
We are working relentlessly with partners and consultants to solve the elevated api errors. With multiple trials, we could isolate the issue which at this moment, points to a load balancer with our data center provider and is used to receive traffic. While we continue to solve the issue completely, we have provided a workaround as a temporary solution for some affected customers, to be able to continue their daily Business. We are continuing to improve the situation and are taking appropriate steps to remediate. This issue is treated with highest priority and we will report with updates on status page regularly.
Aug 3, 16:39 CEST
We are continuing to investigate this issue.
Aug 3, 07:01 CEST
Our investigation regarding the elevated API errors is still ongoing. Over the last days, we have tried many settings and have worked closely with some of affected customers, but it did not yield the desired results. Please rest assured that our teams keep working hard to identify the root cause and appropriate steps to remediate. Of course, this issue remains on highest priority and multiple stakeholders including our datacenter provider, our firewall provider and additional networking consultants work on a solution.
The next planned action is to change firewall and system settings at 6AM to assess if this will improve the situation. We will provide a next update soon after to the affected customers.
Aug 2, 19:02 CEST
We are still investigating the API issues with our partners and are working on some potential fixes. The good news is that not all customers have been affected by this issue, but we would encourage customers to raise any similar issues with us via support channels. We, of course, are still treating this issue with the highest priority and will revert with an update as soon as we can.
Aug 1, 19:02 CEST
We're aware of an issue that is currently causing failures of API calls. We are working along with our data center provider Noris to identify the cause and appropriate steps to remediate. We will update the status page again as soon as we have a solution.
Thank you for being patient.
IDnow DevOps team
Jul 29, 15:33 CEST
We're experiencing an elevated level of API errors and are currently looking into the issue.
Jul 29, 10:53 CEST