Incident History
Resolutions
- Status: Fully Recovered
- Date of Report: Dec 1, 2025
- Reported By: CERTIFY Health
Executive Summary:
Between 9:42 EST and 9:51 AM EST on 1 December 2025, we found out that the requested application connections for login were not completing.
During our analysis, the cause identified was one of our load balanced resource pool connection maxed out for new connections during the time window causing timeouts for the connections attempted during this window.
While the applications were running normal, the threshold on new connections was the actual issue.
We are also exploring ways to proactively identify this kind of issue and have them auto alerted in the status page
We have increased the threshold of connection resource pool to avoid this login timeout issue from occurring again.
- Status: Fully Recovered
- Date of Report: October 30, 2025
- Reported By: CERTIFY Health
Executive Summary:
Between 12:00 EST to 20:00 EST on 29 October 2025, Certify customers may have experienced network related errors.
The cause were identified as due to a wide spread downtime of Azure network services leading to increased latencies, timeouts, and connection errors.
The incident has now been resolved by Azure.
- Status: Fully Recovered
- Date of Report: October 17, 2025
- Reported By: CERTIFY Health
Executive Summary:
On 13th October 2025 , starting around 00:15 AM EST to 00:21 AM EST and from 07:19 AM EST to 07:21 AM EST, our engineers began investigating an issue where Facecheck APIs had connectivity issues and as a result could not complete the API calls.
The Facecheck error during these times were identified as caused by APIs non responsiveness due to issue from proxy services from Azure during these timeframes.
The incident has now been resolved, and we are working towards a connection policy for redirection which will avoid this type of rare issue in the future.