Incode Outage History

Started Apr 27, 2026, 11:56 AM UTC· resolved Apr 27, 2026, 12:38 PM UTC

1. investigating Apr 27, 2026, 11:56 AM UTC

   We are currently investigating this issue.

2. monitoring Apr 27, 2026, 12:09 PM UTC

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

3. resolved Apr 27, 2026, 12:38 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 23, 2026, 01:12 AM UTC· resolved Apr 23, 2026, 04:04 AM UTC

1. investigating Apr 23, 2026, 01:12 AM UTC

   We are observing high failure rate for ID government validation for Argentina. Our team is working on a diagnostic

2. investigating Apr 23, 2026, 01:44 AM UTC

   We are observing high failure rate for ID government validation for Argentina. Our team is working on a diagnostic

3. identified Apr 23, 2026, 01:46 AM UTC

   We have identified the problem, and we are working on a solution.

4. identified Apr 23, 2026, 02:16 AM UTC

   we continue working on the solution

5. identified Apr 23, 2026, 02:46 AM UTC

   We are continuing work on the solution. The fix is ready and is currently being deployed.

6. identified Apr 23, 2026, 03:15 AM UTC

   The fix is ready and is currently being deployed.

7. identified Apr 23, 2026, 03:47 AM UTC

   The fix is currently being released, and we are actively monitoring the deployment to ensure a smooth and stable rollout.

8. resolved Apr 23, 2026, 04:04 AM UTC

   The update was successfully completed, and the RENAPER service is now fully restored and operating normally.

Read the full incident report →

Started Apr 20, 2026, 08:00 PM UTC· resolved Apr 21, 2026, 11:50 AM UTC

1. investigating Apr 20, 2026, 08:00 PM UTC

   We are currently investigating this issue.

2. investigating Apr 20, 2026, 08:28 PM UTC

   We are continuing to investigate this issue.

3. investigating Apr 20, 2026, 09:07 PM UTC

   We are continuing to investigate this issue.

4. investigating Apr 20, 2026, 10:01 PM UTC

   We are continuing to investigate this issue.

5. investigating Apr 20, 2026, 11:02 PM UTC

   We are continuing to investigate this issue.

6. investigating Apr 21, 2026, 12:03 AM UTC

   We are continuing to investigate this issue.

7. investigating Apr 21, 2026, 02:00 AM UTC

   We are continuing to investigate this issue.

8. investigating Apr 21, 2026, 03:01 AM UTC

   We are continuing to investigate this issue.

9. investigating Apr 21, 2026, 04:11 AM UTC

   We are continuing to investigate this issue.

10. investigating Apr 21, 2026, 06:22 AM UTC

    We are continuing to investigate this issue.

11. investigating Apr 21, 2026, 07:37 AM UTC

    We are continuing to investigate this issue.

12. investigating Apr 21, 2026, 08:14 AM UTC

    We are continuing to investigate this issue.

13. investigating Apr 21, 2026, 09:33 AM UTC

    We are continuing to investigate this issue.

14. monitoring Apr 21, 2026, 10:04 AM UTC

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

15. monitoring Apr 21, 2026, 10:04 AM UTC

    We are continuing to monitor for any further issues.

16. resolved Apr 21, 2026, 11:50 AM UTC

    This incident has been resolved.

Read the full incident report →

Started Mar 31, 2026, 10:13 AM UTC· resolved Mar 31, 2026, 11:26 AM UTC

1. investigating Mar 31, 2026, 10:13 AM UTC

   We are currently investigating this issue.

2. identified Mar 31, 2026, 10:18 AM UTC

   The issue has been identified, and the fix has been applied. Please check on your end.

3. monitoring Mar 31, 2026, 10:36 AM UTC

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

4. resolved Mar 31, 2026, 11:26 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 26, 2026, 06:29 PM UTC· resolved Mar 26, 2026, 11:56 PM UTC

1. investigating Mar 26, 2026, 06:29 PM UTC

   We are currently experiencing an issue preventing some users from accessing the dashboard. Our team is actively investigating the root cause and working on a fix. We will provide an update within the next 30 minutes

2. investigating Mar 26, 2026, 07:02 PM UTC

   Our team is still actively investigating the issue affecting access to the dashboard for some users. We will provide another update within the next 30 minutes

3. investigating Mar 26, 2026, 07:44 PM UTC

   Our team is still actively investigating the issue affecting access to the dashboard for some users. We will provide another update within the next 30 minutes

4. investigating Mar 26, 2026, 08:19 PM UTC

   The issue continues to occur intermittently, impacting performance with increased latency and high response times. Our team is actively investigating the root cause and working to resolve it. We will provide another update within the next 30 minutes.

5. investigating Mar 26, 2026, 09:02 PM UTC

   The issue continues to occur intermittently, impacting performance with increased latency and high response times. Our team is actively investigating the root cause and working to resolve it. We will provide another update within the next 30 minutes.

6. investigating Mar 26, 2026, 10:03 PM UTC

   The issue continues to occur intermittently, impacting performance with increased latency and high response times. Our team is actively investigating the root cause and working to resolve it. We will provide another update within the next 30 minutes.

7. investigating Mar 26, 2026, 10:34 PM UTC

   The issue continues to occur intermittently, impacting performance with increased latency and high response times. Our team is actively investigating the root cause and working to resolve it. We will provide another update within the next 30 minutes.

8. investigating Mar 26, 2026, 11:01 PM UTC

   The issue continues to occur intermittently, impacting performance with increased latency and high response times. Our team is actively investigating the root cause and working to resolve it. We will provide another update within the next 30 minutes.

9. investigating Mar 26, 2026, 11:31 PM UTC

   At this time, overall impact has decreased as production load has stabilized, and no significant latency spikes have been observed in the last few hours. Most operations should be functioning normally. However, the underlying issue is still present and could reoccur. Our team continues to investigate and work towards a permanent resolution. We will provide another update within the next 30 minutes.

10. resolved Mar 26, 2026, 11:56 PM UTC

    The 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 system. Thank you for your patience and understanding.

Read the full incident report →

Started Mar 05, 2026, 11:08 AM UTC· resolved Mar 05, 2026, 12:47 PM UTC

1. identified Mar 05, 2026, 11:08 AM UTC

   We have identified an issue on Saas EU where many sessions are failing and a fix is being implemented.

2. identified Mar 05, 2026, 11:38 AM UTC

   We have identified an issue on Saas EU where many sessions are failing and a fix is being implemented.

3. monitoring Mar 05, 2026, 12:07 PM UTC

   Fix has been implemented and issue is resolved. We will keep monitoring the incident.

4. resolved Mar 05, 2026, 12:47 PM UTC

   Fix has been implemented and working as expected. We are marking this incident as resolved.

Read the full incident report →

Started Mar 01, 2026, 06:40 PM UTC· resolved Mar 03, 2026, 07:24 PM UTC

1. investigating Mar 01, 2026, 06:40 PM UTC

   Our cloud infrastructure provider declared a power outage in the me-central-1 UAE region causing a general outage on our platform. We are closely monitoring this incident and evaluating ways of reducing the impact to our platform.

2. investigating Mar 01, 2026, 07:19 PM UTC

   The issue is still ongoing. We are actively monitoring this incident and evaluating mitigation strategies to minimize the impact on our platform.

3. monitoring Mar 01, 2026, 07:57 PM UTC

   The issue is still ongoing. We are actively monitoring this incident and evaluating mitigation strategies to minimize the impact on our platform.

4. monitoring Mar 01, 2026, 08:33 PM UTC

   We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. We will continue to provide information every 30 minutes or as new information becomes available. Thank you for your patience.

5. monitoring Mar 01, 2026, 09:19 PM UTC

   We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. We will continue to provide information every 30 minutes or as new information becomes available. Thank you for your patience.

6. monitoring Mar 01, 2026, 09:46 PM UTC

   We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. We will continue to provide information every 30 minutes or as new information becomes available. Thank you for your patience.

7. monitoring Mar 01, 2026, 10:16 PM UTC

   We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. We will continue to provide information every 30 minutes or as new information becomes available. Thank you for your patience.

8. monitoring Mar 01, 2026, 10:53 PM UTC

   We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. We will continue to provide information every 30 minutes or as new information becomes available. Thank you for your patience.

9. monitoring Mar 01, 2026, 11:19 PM UTC

   We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. We will continue to provide information every 30 minutes or as new information becomes available. Thank you for your patience.

10. monitoring Mar 01, 2026, 11:46 PM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. We will continue to provide information every 30 minutes or as new information becomes available. Thank you for your patience.

11. monitoring Mar 02, 2026, 12:16 AM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. We will continue to provide information every 30 minutes or as new information becomes available. Thank you for your patience.

12. monitoring Mar 02, 2026, 01:02 AM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. We will continue to provide information every 30 minutes or as new information becomes available. Thank you for your patience.

13. monitoring Mar 02, 2026, 01:18 AM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. We will continue to provide information every 30 minutes or as new information becomes available. Thank you for your patience.

14. monitoring Mar 02, 2026, 01:53 AM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. We will continue to provide information every 30 minutes or as new information becomes available. Thank you for your patience.

15. monitoring Mar 02, 2026, 02:27 AM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. We will continue to provide information every 30 minutes or as new information becomes available. Thank you for your patience.

16. monitoring Mar 02, 2026, 02:57 AM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. We will continue to provide information every 30 minutes or as new information becomes available. Thank you for your patience.

17. monitoring Mar 02, 2026, 03:27 AM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. We will continue to provide information every 30 minutes or as new information becomes available. Thank you for your patience.

18. monitoring Mar 02, 2026, 03:57 AM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. We will continue to provide information every 30 minutes or as new information becomes available. Thank you for your patience.

19. monitoring Mar 02, 2026, 04:27 AM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. We will continue to provide information every 30 minutes or as new information becomes available. Thank you for your patience.

20. monitoring Mar 02, 2026, 04:57 AM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. We will continue to provide information every 30 minutes or as new information becomes available. Thank you for your patience.

21. monitoring Mar 02, 2026, 05:34 AM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. We will continue to provide information every 30 minutes or as new information becomes available. Thank you for your patience.

22. monitoring Mar 02, 2026, 05:57 AM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. We will continue to provide information every 30 minutes or as new information becomes available. Thank you for your patience.

23. monitoring Mar 02, 2026, 09:59 AM UTC

    The outage has escalated to a regional disruption in ME-CENTRAL-1 due to a power issue affecting multiple Availability Zones. Customers are experiencing API errors, failed instance launches, and increased error rates and latency. The AWS Console and APIs are partially unavailable, limiting mitigation. We are attempting workarounds and monitoring AWS updates.

24. monitoring Mar 02, 2026, 03:23 PM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. Thank you for your patience.

25. monitoring Mar 02, 2026, 04:34 PM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. Thank you for your patience.

26. monitoring Mar 02, 2026, 05:02 PM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. Thank you for your patience.

27. monitoring Mar 02, 2026, 09:57 PM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. Thank you for your patience.

28. monitoring Mar 02, 2026, 10:28 PM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. Thank you for your patience.

29. monitoring Mar 02, 2026, 11:39 PM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. Thank you for your patience.

30. monitoring Mar 03, 2026, 12:11 AM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. Thank you for your patience.

31. monitoring Mar 03, 2026, 12:41 AM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. Thank you for your patience.

32. monitoring Mar 03, 2026, 01:12 AM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. Thank you for your patience.

33. monitoring Mar 03, 2026, 01:43 AM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. Thank you for your patience.

34. monitoring Mar 03, 2026, 02:28 AM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. Thank you for your patience.

35. monitoring Mar 03, 2026, 02:59 AM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. Thank you for your patience.

36. monitoring Mar 03, 2026, 03:29 AM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. Thank you for your patience.

37. monitoring Mar 03, 2026, 03:59 AM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. Thank you for your patience.

38. monitoring Mar 03, 2026, 04:29 AM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. Thank you for your patience.

39. monitoring Mar 03, 2026, 05:00 AM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. Thank you for your patience.

40. monitoring Mar 03, 2026, 05:30 AM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. Thank you for your patience.

41. monitoring Mar 03, 2026, 06:00 AM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. Thank you for your patience.

42. monitoring Mar 03, 2026, 06:30 AM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. Thank you for your patience.

43. monitoring Mar 03, 2026, 07:05 AM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. Thank you for your patience.

44. monitoring Mar 03, 2026, 07:30 AM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. Thank you for your patience.

45. monitoring Mar 03, 2026, 08:12 AM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. Thank you for your patience.

46. monitoring Mar 03, 2026, 08:32 AM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. Thank you for your patience.

47. monitoring Mar 03, 2026, 09:00 AM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. Thank you for your patience.

48. monitoring Mar 03, 2026, 09:29 AM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. Thank you for your patience.

49. monitoring Mar 03, 2026, 10:00 AM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. Thank you for your patience.

50. monitoring Mar 03, 2026, 10:29 AM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. Thank you for your patience.

51. monitoring Mar 03, 2026, 10:59 AM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. Thank you for your patience.

52. monitoring Mar 03, 2026, 11:30 AM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. Thank you for your patience.

53. monitoring Mar 03, 2026, 12:01 PM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. Thank you for your patience.

54. monitoring Mar 03, 2026, 12:31 PM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. Thank you for your patience.

55. monitoring Mar 03, 2026, 01:00 PM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. Thank you for your patience.

56. monitoring Mar 03, 2026, 01:34 PM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. Thank you for your patience.

57. monitoring Mar 03, 2026, 02:00 PM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. Thank you for your patience.

58. monitoring Mar 03, 2026, 02:39 PM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. Thank you for your patience.

59. monitoring Mar 03, 2026, 04:46 PM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. Thank you for your patience.

60. monitoring Mar 03, 2026, 05:25 PM UTC

    We are closely monitoring recovery efforts and evaluating system performance in real time, unfortunately the stability of the service has not yet been confirmed. Thank you for your patience.

61. resolved Mar 03, 2026, 07:24 PM UTC

    We 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 operations. Thank you for your patience and understanding as we work through this together, unfortunately the stability of the service has not yet been confirmed. Please watch for our status emails for the latest information.

Read the full incident report →

Started Feb 23, 2026, 03:16 PM UTC· resolved Feb 23, 2026, 04:29 PM UTC

1. investigating Feb 23, 2026, 03:16 PM UTC

   We are currently investigating this issue.

2. identified Feb 23, 2026, 03:24 PM UTC

   We are currently experiencing a service disruption affecting SMS delivery across our platform. This issue was identified on February 23, 2026. Our engineering team has identified the root cause and is actively working to restore SMS service. We are treating this as a high-priority incident and have mobilized our emergency response team to resolve the issue as quickly as possible.

3. identified Feb 23, 2026, 03:57 PM UTC

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

4. monitoring Feb 23, 2026, 04:13 PM UTC

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

5. resolved Feb 23, 2026, 04:29 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 04, 2026, 04:03 AM UTC· resolved Feb 04, 2026, 05:04 AM UTC

1. investigating Feb 04, 2026, 04:03 AM UTC

   We have detected dashboard errors related to Session visibility. Our engineering team is working to know the reason of this affectation.

2. monitoring Feb 04, 2026, 04:18 AM UTC

   The engineering team have detected the issue, and corrective actions have been taken. We are monitoring the general behavior

3. resolved Feb 04, 2026, 05:04 AM UTC

   Service meets the expected behavior. This incident is considered as closed.

Read the full incident report →

Started Jan 26, 2026, 08:53 PM UTC· resolved Jan 27, 2026, 03:38 PM UTC

1. investigating Jan 26, 2026, 08:53 PM UTC

   We are currently investigating a potential incident that may be impacting webhooks features. Our team is actively working to assess the situation and determine the scope of the issue. We will provide updates as soon as more information becomes available. Thank you for your patience and understanding.

2. investigating Jan 26, 2026, 10:17 PM UTC

   We are continuing to investigate this issue.

3. investigating Jan 26, 2026, 10:46 PM UTC

   We are continuing to investigate this issue.

4. investigating Jan 26, 2026, 11:24 PM UTC

   We are continuing to investigate this issue.

5. investigating Jan 27, 2026, 12:01 AM UTC

   We are continuing to investigate this issue.

6. investigating Jan 27, 2026, 12:38 AM UTC

   We are continuing to investigate this issue.

7. investigating Jan 27, 2026, 01:50 AM UTC

   We are continuing to investigate this issue.

8. investigating Jan 27, 2026, 02:44 AM UTC

   We are continuing to investigate this issue.

9. investigating Jan 27, 2026, 03:14 AM UTC

   We are continuing to investigate this issue.

10. investigating Jan 27, 2026, 03:48 AM UTC

    We are continuing to investigate this issue.

11. investigating Jan 27, 2026, 04:45 AM UTC

    We are continuing to investigate this issue.

12. identified Jan 27, 2026, 11:29 AM UTC

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

13. monitoring Jan 27, 2026, 03:23 PM UTC

    Fix has been implemented and issue is now resolved.

14. resolved Jan 27, 2026, 03:38 PM UTC

    Marking this incident as resolved.

Read the full incident report →

Started Jan 26, 2026, 08:33 PM UTC· resolved Jan 26, 2026, 09:39 PM UTC

1. identified Jan 26, 2026, 08:33 PM UTC

   We are currently investigating a potential incident that may be impacting some services. Our team is actively working to assess the situation and determine the scope of the issue. We will provide updates as soon as more information becomes available. Thank you for your patience and understanding.

2. identified Jan 26, 2026, 08:42 PM UTC

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

3. identified Jan 26, 2026, 09:08 PM UTC

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

4. monitoring Jan 26, 2026, 09:15 PM UTC

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

5. resolved Jan 26, 2026, 09:39 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 21, 2026, 11:40 AM UTC· resolved Jan 21, 2026, 12:54 PM UTC

1. investigating Jan 21, 2026, 11:40 AM UTC

   We are currently investigating this issue.

2. identified Jan 21, 2026, 11:41 AM UTC

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

3. monitoring Jan 21, 2026, 12:10 PM UTC

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

4. resolved Jan 21, 2026, 12:54 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 16, 2026, 06:51 PM UTC· resolved Jan 16, 2026, 07:04 PM UTC

1. investigating Jan 16, 2026, 06:51 PM UTC

   We are currently investigating this issue.

2. monitoring Jan 16, 2026, 06:57 PM UTC

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

3. monitoring Jan 16, 2026, 06:58 PM UTC

   We are continuing to monitor for any further issues.

4. resolved Jan 16, 2026, 07:04 PM UTC

   We are continuing to monitor for any further issues.

Read the full incident report →

Started Jan 07, 2026, 03:25 PM UTC· resolved Jan 07, 2026, 05:05 PM UTC

1. investigating Jan 07, 2026, 03:25 PM UTC

   We are currently experiencing issues with the display of updated information on the dashboard. At this time, we have only identified problems with the information displayed on the dashboard; calls to the Incode API and SDK are working correctly, however, manual reviews of sessions and authentications are not reflecting recent information.

2. investigating Jan 07, 2026, 03:47 PM UTC

   We are continuing to investigate this issue.

3. investigating Jan 07, 2026, 04:21 PM UTC

   We are continuing to investigate this issue.

4. identified Jan 07, 2026, 04:38 PM UTC

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

5. monitoring Jan 07, 2026, 04:44 PM UTC

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

6. resolved Jan 07, 2026, 05:05 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 18, 2025, 12:24 AM UTC· resolved Dec 18, 2025, 01:55 AM UTC

1. investigating Dec 18, 2025, 12:24 AM UTC

   We are currently investigating a potential incident that may be impacting some services. Our team is actively working to assess the situation and determine the scope of the issue. We will provide updates as soon as more information becomes available. Thank you for your patience and understanding.

2. investigating Dec 18, 2025, 12:56 AM UTC

   We are currently investigating a potential incident that may be impacting some services. Our team is actively working to assess the situation and determine the scope of the issue. We will provide updates as soon as more information becomes available. Thank you for your patience and understanding.

3. investigating Dec 18, 2025, 01:27 AM UTC

   We are currently investigating a potential incident that may be impacting some services in our SaaS EU Region. Our team is actively working to assess the situation and determine the scope of the issue. We will provide updates as soon as more information becomes available. Thank you for your patience and understanding.

4. identified Dec 18, 2025, 01:36 AM UTC

   We have identified the issue and will apply the proper corrections in order to resolve this issue.

5. monitoring Dec 18, 2025, 01:37 AM UTC

   We have implemented a fix and we are monitoring that no more errors appear.

6. resolved Dec 18, 2025, 01:55 AM UTC

   We are pleased to inform you that Incode services have been fully restored and operating as expected.

Read the full incident report →

Started Dec 15, 2025, 04:46 PM UTC· resolved Dec 15, 2025, 08:04 PM UTC

1. investigating Dec 15, 2025, 04:46 PM UTC

   We are currently investigating this issue.

2. investigating Dec 15, 2025, 05:15 PM UTC

   We are continuing to investigate this issue.

3. investigating Dec 15, 2025, 05:40 PM UTC

   We are currently experiencing degradation in the dashboard where new sessions were not displaying correctly. All other services, including session processing via API, continued to operate normally. We are continuing to investigate this issue.

4. investigating Dec 15, 2025, 06:31 PM UTC

   We are continuing to investigate this issue.

5. identified Dec 15, 2025, 06:48 PM UTC

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

6. identified Dec 15, 2025, 06:50 PM UTC

   The issue has been identified and all sessions are now displaying correctly in the dashboard. A fix is being implemented.

7. monitoring Dec 15, 2025, 07:02 PM UTC

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

8. resolved Dec 15, 2025, 08:04 PM UTC

   This incident has been resolved.

Read the full incident report →