Incode Outage History

55 incidents recorded over the last 365 days, 53 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Every Recorded Incode Incident

Incode incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 27, 2026Degraded Performance – End-to-End Encryption (E2EE) Flows in SaaS USThis incident has been resolved. Between 21:13 and 22:00 UTC, E2EE flows in our SaaS US environment had elevated errors. The service has been working normally since then. We apologize for the inconvenience.40 minResolved
Oct 5, 2026Elevated number of error 500s on several endpointsThis incident has been resolved.31 minResolved
Sep 15, 2026Mexican CURP Validation - Scheduled Maintenance.[EN] We would like to inform you that a maintenance window has been scheduled by RENAPO, as detailed below: Maintenance details: • Affected service: CURP Validation Service • Environment: Production • Responsible…27h 59mScheduled
Sep 15, 2026Elevated number of errors faceDBThis incident has been resolved.1h 28mResolved
Sep 1, 2026Elevated error ratesIdentity verification requests are operating normally. The issue has been resolved.1h 20mResolved
Aug 31, 2026Degradation in SaaS US environmentThis incident has been resolved. The SaaS US environment is operating normally. We apologize for any disruption caused.44 minResolved
Aug 28, 2026Elevated errors on ID processingWe 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/v241 minResolved
Aug 25, 2026SaaS US - Increased latencyThis incident is now resolved.1h 15mResolved
Aug 24, 2026Increased LatencyLatency back not to normal levels. We are closing the incident.1h 17mResolved
Aug 18, 2026Selfie submission issuesThis incident has been resolved.35 minResolved
Aug 17, 2026Increased LatencyThis incident has now been resolved.41 minResolved
Aug 15, 2026EU environment elevated number 500 Internal Server ErrorError 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…3h 30mResolved
Jul 29, 2026Elevated Errors – Face Recognition (Canada SaaS)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.1h 19mResolved
Jul 27, 2026SaaS US - Increased latencyThis incident has been resolved.32 minResolved
Jul 9, 2026Degradation in SaaS US environmentThis incident is now resolved. Facial verification and document processing have been fully stable with normal response times for the past several minutes1h 7mResolved
Jul 9, 2026SAAS EU DegradationThis incident has been resolved.1h 10mResolved
Jul 8, 2026SAAS US Dashboard UnavailableThe incident has been resolved. Affected services: Dashboard login Onboarding sessions22 minResolved
Jul 6, 2026SAAS US DegradationThis incident has been resolved.34 minResolved
Jul 4, 2026Degradation in SaaS US environmentThis incident has been resolved. Response times are back to normal54 minResolved
Jul 4, 2026New sessions not showing on the dashboardThis incident has been resolved. All sessions are now visible on the SAAS US dashboard.1h 41mResolved
Jul 2, 2026SAAS US DegradationServices are stable and back to normal levels.1h 3mResolved
Jun 27, 2026E2EE Non-Functional for SaaS US CustomersThis incident has been resolved. End-to-End Encryption services are fully operational35 minResolved
Jun 19, 2026SaaS US - Services intermittenceThis incident has been resolved.1h 6mResolved
Jun 15, 2026New sessions not showing up in the dashboard SaaS US.Sessions are now appearing in the dashboard.23 minResolved
Jun 10, 2026SAAS EU DegradationThis incident has been resolved.1h 57mResolved
Jun 10, 2026New Sessions Missing on SaaS USMaintenance completed, and all the systems are functioning properly.2h 31mResolved
Jun 5, 2026SAAS US Disruption - OCR FailuresThis incident has been resolved.1h 20mResolved
Jun 2, 2026We detected some issues with our platformThis incident has been resolved.49 minResolved
Jun 1, 2026Latest sessions not showing in the dashboardSessions are now visible in the dashboard.29 minResolved
May 27, 2026SAAS US DegradationThis incident has been resolved.1h 4mResolved
May 11, 2026Degraded performance on SaaS USA fix was implemented and the degradation was resolved.35 minResolved
May 8, 2026Degraded performanceAll systems are operating normally. Confirmation received from Vendor that all services have fully recovered22h 8mResolved
May 6, 2026SAAS US OutageThis incident has been resolved; services are working on the normal levels.2h 50mResolved
May 4, 2026Session display lag in the all sessions viewThis incident has been resolved.24 minResolved
Apr 30, 2026New sessions not appearing in SaaS EU dashboardThis incident has been resolved.23 minResolved
Apr 27, 2026DEMO environment unable to loginThis incident has been resolved.42 minResolved
Apr 26, 2026Scheduled MaintenanceThe scheduled maintenance has been successfully completed, and all services are now fully operational. Thank you for your patience and cooperation. If you experience any issues, please reach out to our support team.1h 0mScheduled
Apr 23, 2026Argentina Government is having intermitences.The update was successfully completed, and the RENAPER service is now fully restored and operating normally.2h 52mResolved
Apr 20, 2026Incode Workforce OutageThis incident has been resolved.15h 49mResolved
Mar 31, 2026Elevated errors in productionThis incident has been resolved.1h 13mResolved
Mar 26, 2026Dashboard access issueThe issue has been mitigated and system performance has returned to normal levels. Latency and response times are now stable, and services are operating as expected. Our team will continue to closely monitor the…5h 27mResolved
Mar 5, 2026Failed session issue on Saas EUFix has been implemented and working as expected. We are marking this incident as resolved.1h 39mResolved
Mar 1, 2026Outage in Middle East UAE regionWe are continuing to monitor the situation closely and will keep you informed through regular email updates. Our team is committed to resolving this matter as quickly as possible and ensuring minimal impact to your…48h 44mResolved
Feb 23, 2026SMS Notifications OutageThis incident has been resolved.1h 13mResolved
Feb 4, 2026SAAS AUS Sessions not visible - missing dependenciesService meets the expected behavior. This incident is considered as closed.1h 0mResolved
Jan 26, 2026SAAS US WebhooksMarking this incident as resolved.18h 44mResolved
Jan 26, 2026SAAS US 4XX and 5XX errorsThis incident has been resolved.1h 6mResolved
Jan 21, 2026SaaS EU Degradation - Missing new sessions on DashboardThis incident has been resolved.1h 14mResolved
Jan 16, 2026SAAS US DB connection issuesWe are continuing to monitor for any further issues.13 minResolved
Jan 15, 2026SAAS US OutageThis incident has been resolved.25 minResolved
Jan 7, 2026SAAS US - Delay in updating dashboard informationThis incident has been resolved.1h 39mResolved
Dec 18, 2025Interruption internal componentsWe are pleased to inform you that Incode services have been fully restored and operating as expected.1h 30mResolved
Dec 15, 2025SaaS EU Degradation - Dashboard does not show all sessionsThis incident has been resolved.3h 18mResolved
Dec 8, 2025Issues with 503 on /omni/start endpointThis incident has been resolved.49 minResolved
Nov 18, 2025Issues with Web onboarding (Third party Cloudflare)This incident has been resolved.7h 15mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Incode incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Incode Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Incode acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Incode outage in this window ran 2d, against a mean recovery of 3h 40m. If you depend on Incode in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.