Is Incode down?

We are currently investigating this issue.

Since 10:54 UTC, some customers have been seeing elevated error rates on Omni API endpoints; our team is actively working on a fix.

We are seeing the recovery of systems across the board. The number of errors has returned to normal.

This incident has been resolved.

We are currently investigating an issue regarding the elevated number of errors in faceDB.

A recent infrastructure change caused a temporary service disruption. Recovery is underway, and some users may continue to experience intermittent issues.

This incident has been resolved.

We are currently investigating elevated error rates affecting identity verification requests. Some users may experience failures when capturing a selfie or an ID document. Our engineering team is actively investigating. We will provide an update within 30 minutes.

Identity verification requests have recovered and now completing successfully. We are continuing to monitor the environment closely and are working to restore full stability. We will provide a further update within 60 minutes, or sooner if the situation changes.

A fix has been applied and identity verification requests in our Canada environment are completing normally. We are now monitoring the environment to confirm full stability. We will post a final update once monitoring is complete.

Identity verification requests are operating normally. The issue has been resolved.

We have detected a degradation in one of our environments; We are currently investigating.

On August 31, 2026, beginning at 15:58 CST, the Incode SaaS US platform experienced a period of service degradation. Elevated response times in a backend component triggered automatic protection mechanisms, resulting in intermittent HTTP 503 errors affecting access to the SaaS US Dashboard and calls to the /omni/start and /omni/internal/dashboard/flow endpoints. Service partially recovered between 16:05 and 16:22 CST before degrading again, with full recovery confirmed at 16:31 CST. Sessions initiated during the impact window may not have completed and would require a retry. The environment remains under active monitoring while our engineering team completes its investigation; a formal root cause analysis will follow.

We are currently investigating intermittent periods of elevated latency affecting the SaaS US environment. Some requests may take longer than usual to complete or return an error, and the behavior may be intermittent rather than continuous. Our engineering team is actively investigating and working to restore normal performance.

We are continuing to monitor for any further issues.

Service has been stable for the past 20 minutes. Our team continues to investigate and is monitoring closely to confirm full stability.

This incident has been resolved. The SaaS US environment is operating normally. We apologize for any disruption caused.

We are investigating an increase in error rates affecting document processing. Some sessions may return an error or complete without OCR data, and some requests may be temporarily rejected with a "service under increased load" response. Our engineering team has identified the affected component and is working to restore full capacity

We are continuing to investigate this issue.

The fix was applied and our system is gradually recovering, latency and error volume for multiple endpoints are becoming stable. We will continue monitoring.

We confirmed full recovery of the platform, endpoints below don't present any latency nor elevated error rate. POST /omni/process/id POST /omni/add/front-id POST /omni/add/back-id/v2