Incode Status

Resolved - This incident has been resolved; we see normal traffic within SaaS environment.
Data Synchronization: We are currently performing data synchronization from the secondary environment back to the primary environment. This process requires a minimum of 72 hours to complete. During this time, all services remain fully operational.
Oct 21, 02:58 UTC

Update - AWS services have stabilized, and we have successfully switched traffic back to our primary US SaaS environment. All services are now operating normally from the primary region.

Data Synchronization: We are currently performing data synchronization from the secondary environment back to the primary environment. This process requires a minimum of 72 hours to complete. During this time, all services remain fully operational.

We will continue to monitor service performance closely and provide updates on the completion of data synchronization.
Oct 21, 02:54 UTC

Update - AWS services have stabilized, and we have successfully switched traffic back to our primary US SaaS environment. All services are now operating normally from the primary region.

Data Synchronization: We are currently performing data synchronization from the secondary environment back to the primary environment. This process requires a minimum of 72 hours to complete. During this time, all services remain fully operational.

We will continue to monitor service performance closely and provide updates on the completion of data synchronization.
Oct 21, 02:10 UTC

Update - AWS services have stabilized, and we have successfully switched traffic back to our primary US SaaS environment. All services are now operating normally from the primary region.

Data Synchronization: We are currently performing data synchronization from the secondary environment back to the primary environment. This process requires a minimum of 72 hours to complete. During this time, all services remain fully operational.

We will continue to monitor service performance closely and provide updates on the completion of data synchronization.
Oct 21, 01:38 UTC

Update - AWS services have stabilized, and we have successfully switched traffic back to our primary US SaaS environment. All services are now operating normally from the primary region.

Data Synchronization: We are currently performing data synchronization from the secondary environment back to the primary environment. This process requires a minimum of 72 hours to complete. During this time, all services remain fully operational.

We will continue to monitor service performance closely and provide updates on the completion of data synchronization.
Oct 21, 01:07 UTC

Update - AWS services have stabilized, and we have successfully switched traffic back to our primary US SaaS environment. All services are now operating normally from the primary region.

Data Synchronization: We are currently performing data synchronization from the secondary environment back to the primary environment. This process requires a minimum of 72 hours to complete. During this time, all services remain fully operational.

We will continue to monitor service performance closely and provide updates on the completion of data synchronization.
Oct 21, 00:33 UTC

Update - AWS services have stabilized, and we have successfully switched traffic back to our primary US SaaS environment. All services are now operating normally from the primary region.

Data Synchronization: We are currently performing data synchronization from the secondary environment back to the primary environment. This process requires a minimum of 72 hours to complete. During this time, all services remain fully operational.

We will continue to monitor service performance closely and provide updates on the completion of data synchronization.
Oct 21, 00:02 UTC

Update - AWS services have stabilized, and we have successfully switched traffic back to our primary US SaaS environment. All services are now operating normally from the primary region.

Data Synchronization: We are currently performing data synchronization from the secondary environment back to the primary environment. This process requires a minimum of 72 hours to complete. During this time, all services remain fully operational.

We will continue to monitor service performance closely and provide updates on the completion of data synchronization.
Oct 20, 23:33 UTC

Update - AWS services have stabilized, and we have successfully switched traffic back to our primary US SaaS environment. All services are now operating normally from the primary region.

Data Synchronization: We are currently performing data synchronization from the secondary environment back to the primary environment. This process requires a minimum of 72 hours to complete. During this time, all services remain fully operational.

We will continue to monitor service performance closely and provide updates on the completion of data synchronization.
Oct 20, 23:03 UTC

Update - AWS services have stabilized and we have successfully switched traffic back to our primary US SaaS environment. All services are now operating normally from the primary region.

Data Synchronization: We are currently performing data synchronization from the secondary environment back to the primary environment. This process requires a minimum of 72 hours to complete. During this time, all services remain fully operational.

We will continue to monitor service performance closely and provide updates on the completion of data synchronization.
Oct 20, 22:34 UTC

Update - AWS services have stabilized and we have successfully switched traffic back to our primary US SaaS environment. All services are now operating normally from the primary region.

Data Synchronization: We are currently performing data synchronization from the secondary environment back to the primary environment. This process requires a minimum of 24 hours to complete. During this time, all services remain fully operational.

We will continue to monitor service performance closely and provide updates on the completion of data synchronization.
Oct 20, 22:33 UTC

Update - We continue to operate in our secondary environment (Disaster Recovery Plan active) with the following known limitations: Face Authentication and SSO Authentication in Incode Dashboard.
Oct 20, 21:54 UTC

Update - We continue to operate in our secondary environment (Disaster Recovery Plan active) with the following known limitations: Face Authentication and SSO Authentication in Incode Dashboard.
Oct 20, 21:20 UTC

Update - We continue to operate in our secondary environment (Disaster Recovery Plan active) with the following known limitations: Face Authentication and SSO Authentication in Incode Dashboard.
Oct 20, 20:51 UTC

Update - We continue to operate in our secondary environment (Disaster Recovery Plan active) with the following known limitations: Face Authentication and SSO Authentication in Incode Dashboard.
Oct 20, 20:21 UTC

Update - Following the recent fix, we are observing considerable improvement in latency across our Secondary SaaS US environment. Response times have returned to expected levels.

We continue to operate in our secondary environment (Disaster Recovery Plan active) with the following known limitations: Face Authentication and SSO Authentication in Incode Dashboard.
Oct 20, 19:36 UTC

Monitoring - A fix has been implemented and we are monitoring the results.
Oct 20, 18:52 UTC

Investigating - We are currently experiencing a Major Outage affecting our US SaaS environment. Our team is actively investigating the issue and working to restore service as quickly as possible.

We will provide updates as more information becomes available.
Oct 20, 18:22 UTC

Update - Update - We are still currently experiencing degraded performance with multiple services including id-processing and SSO. Our team is actively troubleshooting the issue.
Oct 20, 18:02 UTC

Update - We are still currently experiencing degraded performance with multiple services including id-processing. Our team is actively troubleshooting the issue.
Oct 20, 17:40 UTC

Monitoring - Traffic switched to secondary environment due to AWS degradation. Service restored to normal performance. Face Authentication with temporarily limitations.
Oct 20, 16:50 UTC

Update - To maintain service availability and improve response times while AWS resolves the infrastructure issues, we are activating our Disaster Recovery Plan (DRP) and switching traffic to our secondary environment. This is a standard procedure designed to minimize impact to your operations during infrastructure incidents.
Oct 20, 16:30 UTC

Update - We continue experiencing elevated response times may affect time-sensitive operations in our SaaS US environment due to AWS service degradation. Our team is actively implementing mitigations to minimize impact while AWS works toward resolution.
Oct 20, 15:23 UTC

Identified - Incode internal team has determined that the degradation and increased response latency is related to ongoing AWS services degradation. We are closely monitoring the situation and AWS's progress toward full stability.
Oct 20, 14:51 UTC

Investigating - We have identified and are actively investigating a service degradation affecting our US SaaS environment. This issue is characterized by increased response latency that may impact your operations.
Oct 20, 14:31 UTC

All Systems Operational

Past Incidents