All Systems Operational

Uptime over the past 90 days. View historical uptime.
Incode Omni Operational
90 days ago
99.98 % uptime
Today
Omni Australia Operational
90 days ago
100.0 % uptime
Today
Omni US Operational
90 days ago
99.93 % uptime
Today
Omni EU Operational
90 days ago
100.0 % uptime
Today
Omni Demo Operational
90 days ago
100.0 % uptime
Today
Omni Canada Operational
90 days ago
100.0 % uptime
Today
Omni Middle East Operational
90 days ago
100.0 % uptime
Today
SOR Data Sources Operational
90 days ago
100.0 % uptime
Today
México - CURP validation Operational
México - INE Facial Government Validation Operational
Argentina Government Validation Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Sep 4, 2026

No incidents reported today.

Sep 3, 2026

No incidents reported.

Sep 2, 2026

No incidents reported.

Sep 1, 2026

Elevated error rates
Resolved - Identity verification requests are operating normally. The issue has been resolved.
Sep 1, 16:02 UTC
Identified - 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.
Sep 1, 15:12 UTC
Update - 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.
Sep 1, 14:56 UTC
Investigating - 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.
Sep 1, 14:42 UTC

Aug 31, 2026

Degradation in SaaS US environment
Resolved - This incident has been resolved. The SaaS US environment is operating normally. We apologize for any disruption caused.
Aug 31, 23:18 UTC
Update - Service has been stable for the past 20 minutes. Our team continues to investigate and is monitoring closely to confirm full stability.
Aug 31, 23:05 UTC
Update - We are continuing to monitor for any further issues.
Aug 31, 22:55 UTC
Update - 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.
Aug 31, 22:47 UTC
Monitoring - 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.
Aug 31, 22:37 UTC
Investigating - We have detected a degradation in one of our environments; We are currently investigating.
Aug 31, 22:34 UTC

Aug 30, 2026

No incidents reported.

Aug 29, 2026

No incidents reported.

Aug 28, 2026

Elevated errors on ID processing
Resolved - 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
Aug 28, 21:40 UTC
Monitoring - The fix was applied and our system is gradually recovering, latency and error volume for multiple endpoints are becoming stable. We will continue monitoring.
Aug 28, 21:20 UTC
Update - We are continuing to investigate this issue.
Aug 28, 21:01 UTC
Investigating - 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
Aug 28, 20:59 UTC

Aug 27, 2026

No incidents reported.

Aug 26, 2026

No incidents reported.

Aug 25, 2026

SaaS US - Increased latency
Resolved - This incident is now resolved.
Aug 25, 17:54 UTC
Update - Fix has been implemented. We are still monitoring.
Aug 25, 17:45 UTC
Update - Fix has been implemented. We are still monitoring.
Aug 25, 17:25 UTC
Monitoring - Fix has been implemented. We are still monitoring.
Aug 25, 17:07 UTC
Identified - Issue has been being identified and fix is being deployed.
Aug 25, 17:03 UTC
Update - We are continuing to investigate. Current impact are high response times and increment in errors, mainly for endpoints: add/front, add/back, process/id, process/face.
Aug 25, 16:45 UTC
Investigating - We are currently investigating this case.
Aug 25, 16:39 UTC

Aug 24, 2026

Increased Latency
Resolved - Latency back not to normal levels. We are closing the incident.
Aug 24, 19:32 UTC
Update - Latency is decreasing. We are still monitoring.
Aug 24, 19:23 UTC
Update - We still see some increased latency, continuing to monitor the situation.
Aug 24, 18:58 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Aug 24, 18:36 UTC
Identified - The issue has been identified and we are working on the fix.
Aug 24, 18:33 UTC
Investigating - We are currently investigating this issue
Aug 24, 18:14 UTC

Aug 23, 2026

No incidents reported.

Aug 22, 2026

No incidents reported.

Aug 21, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage