Incode Outage History

Incode is up right now

Incode had 41 outages in the last 2 years totaling 49h 49m of downtime, averaging 1.7 incidents per month.

There were 41 Incode outages since December 15, 2025 totaling 49h 49m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: status.incode.com

Minor October 5, 2026

Elevated number of error 500s on several endpoints

Detected by Pingoru
Oct 05, 2026, 11:24 AM UTC
Resolved
Oct 05, 2026, 11:56 AM UTC
Duration
31m
Affected: Omni US
Timeline · 4 updates
  1. investigating Oct 05, 2026, 11:24 AM UTC

    We are currently investigating this issue.

  2. investigating Oct 05, 2026, 11:30 AM UTC

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

  3. monitoring Oct 05, 2026, 11:36 AM UTC

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

  4. resolved Oct 05, 2026, 11:56 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 15, 2026

Elevated number of errors faceDB

Detected by Pingoru
Sep 15, 2026, 08:47 AM UTC
Resolved
Sep 15, 2026, 10:15 AM UTC
Duration
1h 28m
Affected: Omni US
Timeline · 3 updates
  1. investigating Sep 15, 2026, 08:47 AM UTC

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

  2. identified Sep 15, 2026, 09:06 AM UTC

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

  3. resolved Sep 15, 2026, 10:15 AM UTC

    This incident has been resolved.

Read the full incident report →

Major September 1, 2026

Elevated error rates

Detected by Pingoru
Sep 01, 2026, 02:42 PM UTC
Resolved
Sep 01, 2026, 04:02 PM UTC
Duration
1h 20m
Affected: Omni Canada
Timeline · 4 updates
  1. investigating Sep 01, 2026, 02:42 PM UTC

    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.

  2. investigating Sep 01, 2026, 02:56 PM UTC

    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.

  3. identified Sep 01, 2026, 03:12 PM UTC

    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.

  4. resolved Sep 01, 2026, 04:02 PM UTC

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

Read the full incident report →

Minor August 31, 2026

Degradation in SaaS US environment

Detected by Pingoru
Aug 31, 2026, 10:34 PM UTC
Resolved
Aug 31, 2026, 11:18 PM UTC
Duration
44m
Affected: Omni US
Timeline · 6 updates
  1. investigating Aug 31, 2026, 10:34 PM UTC

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

  2. monitoring Aug 31, 2026, 10:37 PM UTC

    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.

  3. monitoring Aug 31, 2026, 10:47 PM UTC

    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.

  4. monitoring Aug 31, 2026, 10:55 PM UTC

    We are continuing to monitor for any further issues.

  5. monitoring Aug 31, 2026, 11:05 PM UTC

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

  6. resolved Aug 31, 2026, 11:18 PM UTC

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

Read the full incident report →

Major August 28, 2026

Elevated errors on ID processing

Detected by Pingoru
Aug 28, 2026, 08:59 PM UTC
Resolved
Aug 28, 2026, 09:40 PM UTC
Duration
41m
Affected: Omni US
Timeline · 4 updates
  1. investigating Aug 28, 2026, 08:59 PM UTC

    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

  2. investigating Aug 28, 2026, 09:01 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Aug 28, 2026, 09:20 PM UTC

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

  4. resolved Aug 28, 2026, 09:40 PM UTC

    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

Read the full incident report →

Major August 25, 2026

SaaS US - Increased latency

Detected by Pingoru
Aug 25, 2026, 04:39 PM UTC
Resolved
Aug 25, 2026, 05:54 PM UTC
Duration
1h 15m
Affected: Omni US
Timeline · 7 updates
  1. investigating Aug 25, 2026, 04:39 PM UTC

    We are currently investigating this case.

  2. investigating Aug 25, 2026, 04:45 PM UTC

    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.

  3. identified Aug 25, 2026, 05:03 PM UTC

    Issue has been being identified and fix is being deployed.

  4. monitoring Aug 25, 2026, 05:07 PM UTC

    Fix has been implemented. We are still monitoring.

  5. monitoring Aug 25, 2026, 05:25 PM UTC

    Fix has been implemented. We are still monitoring.

  6. monitoring Aug 25, 2026, 05:45 PM UTC

    Fix has been implemented. We are still monitoring.

  7. resolved Aug 25, 2026, 05:54 PM UTC

    This incident is now resolved.

Read the full incident report →

Minor August 24, 2026

Increased Latency

Detected by Pingoru
Aug 24, 2026, 06:14 PM UTC
Resolved
Aug 24, 2026, 07:32 PM UTC
Duration
1h 17m
Affected: Omni US
Timeline · 6 updates
  1. investigating Aug 24, 2026, 06:14 PM UTC

    We are currently investigating this issue

  2. identified Aug 24, 2026, 06:33 PM UTC

    The issue has been identified and we are working on the fix.

  3. monitoring Aug 24, 2026, 06:36 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. monitoring Aug 24, 2026, 06:58 PM UTC

    We still see some increased latency, continuing to monitor the situation.

  5. monitoring Aug 24, 2026, 07:23 PM UTC

    Latency is decreasing. We are still monitoring.

  6. resolved Aug 24, 2026, 07:32 PM UTC

    Latency back not to normal levels. We are closing the incident.

Read the full incident report →

Major August 18, 2026

Selfie submission issues

Detected by Pingoru
Aug 18, 2026, 03:46 PM UTC
Resolved
Aug 18, 2026, 04:22 PM UTC
Duration
35m
Affected: Omni US
Timeline · 3 updates
  1. investigating Aug 18, 2026, 03:46 PM UTC

    We are currently investigating this issue.

  2. monitoring Aug 18, 2026, 04:04 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Aug 18, 2026, 04:22 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 15, 2026

EU environment elevated number 500 Internal Server Error

Detected by Pingoru
Aug 15, 2026, 11:05 AM UTC
Resolved
Aug 15, 2026, 02:35 PM UTC
Duration
3h 30m
Affected: Omni EU
Timeline · 5 updates
  1. investigating Aug 15, 2026, 11:05 AM UTC

    We are currently investigating an issue regarding an elevated number of "500 Internal Server Error" errors regarding /omni/add/front-id/v2 endpoint.

  2. identified Aug 15, 2026, 12:43 PM UTC

    SaaS EU is experiencing intermittent failures in the Google OCR dependency. Google OCR service receives empty responses, resulting in HTTP 500 from /omni/add/front-id/v2.

  3. identified Aug 15, 2026, 01:50 PM UTC

    Our engineering team has identified the root cause of the issue and is actively working on a resolution. Some sessions may continue to experience degraded performance while the fix is being applied. We will post the next update within 30 minutes, or sooner if the status changes. We apologize for the inconvenience.

  4. monitoring Aug 15, 2026, 02:02 PM UTC

    A fix has been deployed and we are seeing a steady decline in error rates. We are continuing to monitor the system closely to confirm full recovery before marking this incident as resolved. The next update will follow within 30 minutes.

  5. resolved Aug 15, 2026, 02:35 PM UTC

    Error rates have remained at normal levels for 30 minutes following the deployment of the fix, and we consider this incident fully resolved. All services are operating normally. A detailed root cause analysis (RCA) will be shared with affected customers within 72 business hours. Thank you for your patience!

Read the full incident report →

Critical July 29, 2026

Elevated Errors – Face Recognition (Canada SaaS)

Detected by Pingoru
Jul 29, 2026, 02:19 PM UTC
Resolved
Jul 29, 2026, 03:39 PM UTC
Duration
1h 19m
Affected: Omni Canada
Timeline · 4 updates
  1. investigating Jul 29, 2026, 02:19 PM UTC

    We are currently investigating an issue affecting the face recognition service in our Canada SaaS environment. Some requests may be failing or returning errors. Our engineering team is actively investigating and working on a fix. We will provide updates as more information becomes available

  2. investigating Jul 29, 2026, 02:37 PM UTC

    We are still investigating the root cause of this issue and continuing to work toward a resolution. We will share our next update within 30 minutes. Thank you for your patience.

  3. monitoring Jul 29, 2026, 02:58 PM UTC

    A fix has been implemented and we have confirmed that the face recognition service is now working as expected. We are continuing to monitor the situation closely to ensure full stability. We will provide a final update once we're confident the issue is fully resolved.

  4. resolved Jul 29, 2026, 03:39 PM UTC

    This incident has been resolved. The face recognition service is fully operational and we have confirmed normal performance through monitoring. Thank you for your patience throughout this incident.

Read the full incident report →

Minor July 9, 2026

SAAS EU Degradation

Detected by Pingoru
Jul 09, 2026, 02:48 PM UTC
Resolved
Jul 09, 2026, 03:59 PM UTC
Duration
1h 10m
Affected: Omni EU
Timeline · 5 updates
  1. investigating Jul 09, 2026, 02:48 PM UTC

    We are currently investigating this issue.

  2. identified Jul 09, 2026, 02:58 PM UTC

    The problem has been identified: a degradation caused by a disruption in user service, resulting in failures across all API endpoints in the SaaS EU environment. Our internal team is continuing to investigate.

  3. identified Jul 09, 2026, 03:20 PM UTC

    We continue experiencing degraded performance on SaaS EU due to an issue affecting the user-service which may result in elevated response times or errors on API endpoints for SaaS EU. Impact: Degraded performance on user-service and dependent SaaS EU API endpoints. No major impact has been confirmed at this time.

  4. identified Jul 09, 2026, 03:30 PM UTC

    We are continuing to work on a fix for this issue.

  5. resolved Jul 09, 2026, 03:59 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical July 8, 2026

SAAS US Dashboard Unavailable

Detected by Pingoru
Jul 08, 2026, 06:38 PM UTC
Resolved
Jul 08, 2026, 07:01 PM UTC
Duration
22m
Affected: Omni US
Timeline · 5 updates
  1. investigating Jul 08, 2026, 06:38 PM UTC

    We are currently investigating this issue.

  2. monitoring Jul 08, 2026, 06:47 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. identified Jul 08, 2026, 06:48 PM UTC

    The issue has been identified and a fix is being implemented.

  4. monitoring Jul 08, 2026, 06:48 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Jul 08, 2026, 07:01 PM UTC

    The incident has been resolved. Affected services: Dashboard login Onboarding sessions

Read the full incident report →

Major July 6, 2026

SAAS US Degradation

Detected by Pingoru
Jul 06, 2026, 04:38 PM UTC
Resolved
Jul 06, 2026, 05:12 PM UTC
Duration
34m
Affected: Omni US
Timeline · 4 updates
  1. investigating Jul 06, 2026, 04:38 PM UTC

    Latency was detected in the SaaS US environment. Metrics showed significant degradation

  2. investigating Jul 06, 2026, 04:44 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Jul 06, 2026, 05:00 PM UTC

    The issue has been fully resolved. All system metrics, including latency and error rates, have returned to normal levels. Our team continues to monitor the environment closely to confirm sustained stability.

  4. resolved Jul 06, 2026, 05:12 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 4, 2026

New sessions not showing on the dashboard

Detected by Pingoru
Jul 04, 2026, 09:33 AM UTC
Resolved
Jul 04, 2026, 11:14 AM UTC
Duration
1h 41m
Affected: Omni US
Timeline · 5 updates
  1. investigating Jul 04, 2026, 09:33 AM UTC

    We are currently investigating this issue.

  2. investigating Jul 04, 2026, 10:09 AM UTC

    We are continuing to investigate this issue.

  3. identified Jul 04, 2026, 10:36 AM UTC

    The issue has been identified and a fix is being implemented.

  4. monitoring Jul 04, 2026, 10:41 AM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Jul 04, 2026, 11:14 AM UTC

    This incident has been resolved. All sessions are now visible on the SAAS US dashboard.

Read the full incident report →

Major June 27, 2026

E2EE Non-Functional for SaaS US Customers

Detected by Pingoru
Jun 27, 2026, 03:03 AM UTC
Resolved
Jun 27, 2026, 03:38 AM UTC
Duration
35m
Affected: Omni US
Timeline · 4 updates
  1. investigating Jun 27, 2026, 03:03 AM UTC

    We are currently investigating this situation

  2. identified Jun 27, 2026, 03:22 AM UTC

    A fix has been successfully applied, and End-to-End Encryption services have been restored. We continue to monitor the situation to ensure full stability.

  3. monitoring Jun 27, 2026, 03:23 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Jun 27, 2026, 03:38 AM UTC

    This incident has been resolved. End-to-End Encryption services are fully operational

Read the full incident report →

Minor June 19, 2026

SaaS US - Services intermittence

Detected by Pingoru
Jun 19, 2026, 09:31 AM UTC
Resolved
Jun 19, 2026, 10:38 AM UTC
Duration
1h 6m
Affected: Omni US
Timeline · 4 updates
  1. investigating Jun 19, 2026, 09:31 AM UTC

    We are currently investigating this issue.

  2. investigating Jun 19, 2026, 09:54 AM UTC

    We are continuing to investigate this issue. Services still having intermittences, but customers are not affected.

  3. monitoring Jun 19, 2026, 09:58 AM UTC

    Customers are not affected. We are keep monitoring.

  4. resolved Jun 19, 2026, 10:38 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 10, 2026

New Sessions Missing on SaaS US

Detected by Pingoru
Jun 10, 2026, 10:33 AM UTC
Resolved
Jun 10, 2026, 01:04 PM UTC
Duration
2h 31m
Affected: Omni US
Timeline · 6 updates
  1. investigating Jun 10, 2026, 10:33 AM UTC

    We are currently investigating this issue.

  2. monitoring Jun 10, 2026, 10:37 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. monitoring Jun 10, 2026, 10:37 AM UTC

    We are continuing to monitor for any further issues.

  4. monitoring Jun 10, 2026, 11:19 AM UTC

    The maintenance is still in progress. We will update when it is completed.

  5. monitoring Jun 10, 2026, 12:22 PM UTC

    Maintenance at 95% completion.

  6. resolved Jun 10, 2026, 01:04 PM UTC

    Maintenance completed, and all the systems are functioning properly.

Read the full incident report →

Major June 5, 2026

SAAS US Disruption - OCR Failures

Detected by Pingoru
Jun 05, 2026, 03:44 PM UTC
Resolved
Jun 05, 2026, 05:05 PM UTC
Duration
1h 20m
Affected: Omni US
Timeline · 7 updates
  1. investigating Jun 05, 2026, 03:44 PM UTC

    We are currently investigating an issue impacting OCR operations across SAAS US environment. The impact is intermittent.

  2. identified Jun 05, 2026, 03:51 PM UTC

    The issue has been identified and a fix is being implemented.

  3. identified Jun 05, 2026, 03:58 PM UTC

    The issue has been identified and a fix is being implemented. Affected endpoints: /0/omni/add/front-id/v2 /0/omni/add/back-id/v2 /omni/add/front-id/v2 /omni/add/back-id/v2 /0/omni/add/front-id /0/omni/add/back-id /omni/add/front-id /omni/add/watchlist/single-record

  4. identified Jun 05, 2026, 04:17 PM UTC

    The issue has been identified and a fix is being implemented. Affected endpoints: /0/omni/add/front-id/v2 /0/omni/add/back-id/v2 /omni/add/front-id/v2 /omni/add/back-id/v2 /0/omni/add/front-id /0/omni/add/back-id /omni/add/front-id /omni/add/watchlist/single-record

  5. identified Jun 05, 2026, 04:30 PM UTC

    The issue has been identified and a fix is being implemented. Affected endpoints: /0/omni/add/front-id/v2 /0/omni/add/back-id/v2 /omni/add/front-id/v2 /omni/add/back-id/v2 /0/omni/add/front-id /0/omni/add/back-id /omni/add/front-id /omni/add/watchlist/single-record

  6. monitoring Jun 05, 2026, 04:41 PM UTC

    A fix has been implemented and we are monitoring the results.

  7. resolved Jun 05, 2026, 05:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 2, 2026

We detected some issues with our platform

Detected by Pingoru
Jun 02, 2026, 08:11 AM UTC
Resolved
Jun 02, 2026, 09:00 AM UTC
Duration
49m
Affected: Omni US
Timeline · 3 updates
  1. investigating Jun 02, 2026, 08:11 AM UTC

    We are currently investigating this issue.

  2. monitoring Jun 02, 2026, 08:25 AM UTC

    Due to some internal system optimization, we have seen an increase in 4xx and 5xx errors. The problem was mitigated quickly, and the impact lasted about 10 minutes.

  3. resolved Jun 02, 2026, 09:00 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 1, 2026

Latest sessions not showing in the dashboard

Detected by Pingoru
Jun 01, 2026, 10:43 AM UTC
Resolved
Jun 01, 2026, 11:12 AM UTC
Duration
29m
Affected: Omni US
Timeline · 2 updates
  1. identified Jun 01, 2026, 10:43 AM UTC

    The issue only affects the sessions appearing in the dashboard. Other services are fine. There is currently release in progress. We will keep you updated.

  2. resolved Jun 01, 2026, 11:12 AM UTC

    Sessions are now visible in the dashboard.

Read the full incident report →

Minor May 11, 2026

Degraded performance on SaaS US

Detected by Pingoru
May 11, 2026, 09:55 PM UTC
Resolved
May 11, 2026, 10:30 PM UTC
Duration
35m
Affected: Omni US
Timeline · 3 updates
  1. investigating May 11, 2026, 09:55 PM UTC

    We have detected a degradation affecting SaaS US environment, our internal team is investigating. We will provide additional information soon.

  2. investigating May 11, 2026, 10:11 PM UTC

    Our team continues investigating, corrective measures were taken and there should be an improvement in the transaction success rate. We will provide additional information soon

  3. resolved May 11, 2026, 10:30 PM UTC

    A fix was implemented and the degradation was resolved.

Read the full incident report →

Minor May 4, 2026

Session display lag in the all sessions view

Detected by Pingoru
May 04, 2026, 12:13 PM UTC
Resolved
May 04, 2026, 12:37 PM UTC
Duration
24m
Affected: Omni US
Timeline · 2 updates
  1. identified May 04, 2026, 12:13 PM UTC

    In the SaaS US environment, sessions may appear after a slight 10-15 lag in the all sessions view. We implemented a fix, and we will keep sharing updates.

  2. resolved May 04, 2026, 12:37 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 30, 2026

New sessions not appearing in SaaS EU dashboard

Detected by Pingoru
Apr 30, 2026, 11:29 AM UTC
Resolved
Apr 30, 2026, 11:52 AM UTC
Duration
23m
Affected: Omni EU
Timeline · 3 updates
  1. investigating Apr 30, 2026, 11:29 AM UTC

    New sessions are not showing up in the dashboard on the SaaS EU environment. We are investigating.

  2. monitoring Apr 30, 2026, 11:39 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Apr 30, 2026, 11:52 AM UTC

    This incident has been resolved.

Read the full incident report →