Incode incident

Outage in Middle East UAE region

Resolved after 2 days, affecting Omni Middle East, on March 1, 2026.

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.

Started
Mar 01, 2026, 06:40 PM UTC
Resolved
Mar 03, 2026, 07:24 PM UTC
Duration
2d
Detected by Pingoru
Mar 01, 2026, 06:40 PM UTC

Affected components

Omni Middle East

Update timeline

  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.

Your product runs on more than Incode

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →