ID Dataweb had 14 outages in the last 2 years totaling 31h 24m of downtime — averaging 0.6 incidents per month.
There were 14 ID Dataweb outages since March 20, 2025 totaling 31h 24m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are seeing increased error rates with device profiling. We are monitoring this closely and will update the status of this issue as it becomes available.
This incident has been resolved.
We are observing elevated error rates on KBA services in production. We are monitoring this closely and will update the status of this issue as it becomes available.
We are seeing signs of recovery from our internal monitoring tools. We will update status once we confirm full recovery
All KBA services have returned to normal
We are observing elevated error rates on BiogovID services in production. We are monitoring closely, more details available here: https://status.incode.com/
The service has stabilized and returned to normal
Starting around 1045am ET, ID Dataweb observed spikes in latency in our production environment. As a result, we have rolled back last night's deployment, which has returned stability to our production environment. We will continue to monitor throughout the day, and will provide an updated plan next week regarding the application upgrade.
As of 5pm ET, we are observing higher than average latency / timeouts in production across transactions. Our system automatically failed over to our secondary region, which has restored API traffic. Gateway traffic is being rerouted currently. This should restore all connections to baseline. Once done, the team will investigate the underlying issue and determine next steps. We will post updates here in real time.
Gateway (hosted) traffic has been successfully routed to our secondary region, and is stable. The team is now turning their attention to the underlying issue in US EAST 1. Updates will be provided in real time.
The underlying issue has been identified and addressed in US EAST 1, and all traffic has been routed back. Traffic remains normal. We will continue to actively monitor as the team further evaluates the root cause. An RCA will be made available in the coming days.
We are aware of an intermittent cosmetic UI issue where “Demo App” text may appear in production and are working with the upstream provider to resolve it.
This incident has been resolved.
We are observing latency and errors with Experian Precise ID. This may be impacting any service which relies on SSN validation. We are in touch with the vendor, and will update here in real time.
Experian services have been restored. We will continue to actively monitor into the evening.
Our GovID verification partner is currently experiencing issues due to the ongoing Cloudflare outage. We are in touch with the vendor, and will update as we get more information. More information can be found at the following links: - https://www.cloudflarestatus.com/ - https://status.incode.com/
Cloudflare has deployed a solution, which has addressed the issues with our GovID vendor. We are continuing to monitor closely.
All systems have remained operational since the last update. We will continue to actively monitor throughout the day.
We are observing increased latency and timeouts on Experian services. We are in touch with the vendor, and will provide updates in real time.
Experian services have returned to normal performance levels. We will continue to actively monitor to ensure no further impact.
Experian remains fully operational. The team will continue to actively monitor throughout the day.
We are investigating increased latency on the ID Dataweb system. We are observing 3rd party API calls failing, including Experian. Our team is evaluating, and will provide updates in real time.
We are observing traffic returning to normal levels within the last hour. We are following up with 3rd party providers to get more details into the issue. Once more information is obtained, ID Dataweb will provide an RCA to affected parties.
Our primary BiogovID vendor is currently experiencing performance issues relating to the ongoing AWS Outage, leading to transaction failures. We are closely monitoring the situation. Status updates for GovID users can be followed here: https://status.incode.com/
Update - The BiogovID service has been restored, per https://status.incode.com/. We are observing all BiogovID traffic returning to a normal state. We will provide an RCA from the vendor when available.
We are experiencing issues relating to the current AWS outage. As of earlier this morning, ID Dataweb successfully failed over to US EAST 2, which mitigated the issue. Now - we are seeing increased latency, likely caused by 3rd party services being affected by the same issues. We are investigating, and will post updates in real time.
Our DevOps team has identified and resolved an issue relating to 3rd party services affected by the current AWS Outage, and we are seeing traffic return to normal. We are running regression and monitoring closely. Customers should see traffic returning to normal. More updates to come.
All systems have appeared operational since ~9:30am ET. We are continue to closely monitor, as the broader AWS outage remains ongoing. We will continue to provide live updates here until all 3rd party systems are restored.
Our Application Performance Monitoring tools indicate that ID Dataweb systems remain fully operational, in spite of the ongoing AWS issues, since roughly 9:30am ET. We will keep this incident in "monitoring" state until AWS fully closes the incident on their side.
AWS has restored the affected systems that caused the outage in the US-EAST-1 region. All ID DataWeb services are operating normally. We are marking this incident as resolved.
We are observing a second incident with BiogovID Services provided by Incode, which is partially affecting production traffic. Incode has opened a second issue (https://status.incode.com/#). We are in touch with the appropriate support & operations teams, and will provide updates as they become available.
We are observing full restoration of Incode services at this time. Our team will continue to monitor throughout the evening.
This incident has been resolved.
We are rapidly investigating an infrastructure issue affecting our PreProduction and Production environments and will provide updates shortly. The majority of traffic is currently believed to be affected including access to the admin console.
We are continuing to investigate this issue.
Service has been partially restored and the team is monitoring the relevant infrastructure changes.
Service has been restored for Gateway customers and remains unavailable for API customers; we are actively resolving the issue and scaling back up relevant infrastructure.
We are continuing to investigate this issue.
An issue with one of our Production clusters in US-East-1 (AWS) resulted in a partial failover to US-East-2; our team has identified the issue with the failover instance and is working on the fix. Services remain unavailable to API customers and degraded for Gateway customers; access to the admin console also remains degraded at this time. We will provide updates within every hour until resolution. We understand the impact of this incident and appreciate your patience. Please contact [email protected] with any questions or concerns.
Our team has fully resolved the related infrastructure issues and all services are fully operational for all customers at this time. We will continue to monitor performance and follow-up directly with a RCA. Incident Start: 03/20/2025, 11:50 AM EST Incident End: 03/20/2025, 01:30 PM EST Incident Duration: 1h 40m You can check this page (status.iddataweb.com) regularly or subscribe to its updates per your preference. Please contact [email protected] with any additional questions or concerns.
This incident has been resolved and an RCA will be provided as soon as possible.