OutSystems Status

Resolved: All customers impacted by this incident have been contacted and supported individually. While the Middle East region continues to be affected by the ongoing geopolitical situation and AWS continues to report the region as impacted, OutSystems has completed its direct response to every affected organization. The affected services remain flagged as a major outage while these conditions persist. Customers who need further assistance can contact OutSystems Support by raising a new ticket or continuing their existing case through Support Services.

Identified: Most affected O11 Cloud customers in the Middle East (Bahrain) region have been mitigated, and overall stability has improved. The AWS outage remains ongoing. We are continuing to actively monitor AWS updates to ensure full service recovery. Further updates will be provided directly to affected users via their individual support tickets. Customers requiring additional assistance are encouraged to contact OutSystems Support by raising a new ticket or following their existing cases through the Support Portal.

Identified: We are investigating reports of service disruption affecting O11 Cloud customer in the Middle East (Bahrain) region. We are currently reaching out to impacted customers directly and will provide further updates as more information becomes available.

Identified: Recovery efforts for the Middle East (UAE) remain ongoing as cloud infrastructure providers work to restore impacted services. ODC organizations remain unavailable while these restoration efforts continue. We are continuing tracking the recovery process of this incident to ensure a complete recovery. Going forward, updates will be delivered directly to affected users through their individual support tickets. Users who require further assistance with this event are encouraged to contact OutSystems Support by raising a new ticket or following their existing cases through the Support Portal.

Identified: Recovery efforts for the Middle East (UAE) remain ongoing as cloud infrastructure providers work to restore impacted services. ODC organizations remain unavailable while these restoration efforts continue. We are closely tracking the progress and will provide further updates as more information becomes available.

Identified: Recovery efforts for the Middle East (UAE) region remain ongoing as cloud infrastructure providers work to restore impacted services. We continue to track the recovery progress and will provide further updates as more information becomes available.

Identified: Recovery efforts are still underway for the Middle East (UAE) as cloud services work to restore one of the affected areas. We are continuing to track the progress and will provide further updates as more information becomes available.

Identified: We are continuing to monitor the recovery of ODC services in the Middle East (UAE) as the underlying infrastructure issues are being addressed. We will provide further updates as soon as more information becomes available.

Identified: Update - We are continuing to monitor the progress of recovery efforts in the affected region. We will provide further information as soon as more details become available.

Monitoring: Update - We are continuing to monitor the progress of recovery efforts in the affected region. We will provide further information as soon as more details become available.

Identified: Recovery efforts are still being prioritized by AWS for this region, focusing on restoration of the impacted AWS Services. We are closely monitoring the situation and will provide further updates once they become available.

Identified: The cause has been identified as a widespread infrastructure failure in the Middle East (UAE) affecting foundational AWS services. While recovery efforts are underway, ODC and other services in this region will remain unavailable until the underlying infrastructure is fully restored.

We are closely monitoring the situation as it recovers and will provide further information once it becomes available.

Investigating: We are still continuing to monitor the investigation with AWS, as the recovery towards the impaired AWS Middle East (UAE) Region is still ongoing. While there have been significant improvements made so far, the estimated recovery time will take at least another day before power and connectivity can be restored.

Investigating: We continue to follow closely the investigation in partnership with AWS, towards the recovery of the Middle East (UAE) Region. At this point, we are expecting recovery to take at least a day given the significant efforts required. Until then, ODC and other services in this region will continue experiencing a total service outage. We continue to monitor the situation closely and will provide updates as more information becomes available.

Investigating: We are investigating an issue affecting Outsystems Products in the Middle East (UAE) region. This disruption is related to the ongoing AWS service incident reported on March 1st.

Users in this region are currently experiencing a total service outage in ODC, and all services are unavailable. We are monitoring the situation closely and will provide updates as more information becomes available.

Investigating: We are currently investigating this issue.

Monitoring: Our services have been fully restored, and the issue affecting our OutSystems customers has been mitigated. While the ongoing disruption reported by AWS continues, it is not expected to impact our customers at this time. We will continue to closely monitor the situation. If you experience any issues, please contact our Support team.

For updates directly from AWS, please visit: https://health.aws.amazon.com/health/status

Identified: We are continuing to monitor the official AWS status page. At this time, AWS has informed customers that some may experience errors when performing certain network-related actions.

AWS is actively implementing mitigation measures, and recovery is expected within the next few hours.

Identified: AWS Team has identified the cause of the disruption affecting one availability zone in the Middle East (UAE) region. Power was temporarily shut down at the facility as a safety precaution.

Restoration of power and connectivity may take several hours. Other availability zones in the region remain operational.

We will provide further updates as more information becomes available.

Investigating: We are currently experiencing service degradation in the Middle East (UAE) region due to connectivity and power issues within a major cloud provider (AWS).

We are actively monitoring the situation and following updates from the official AWS status page. Our team is closely tracking recovery progress. We will provide further updates as more information becomes available.

Postmortem: On June 26, 2026, a code deployment intended to improve our system's infrastructure inadvertently introduced a sorting issue that affected the deployment stage ordering on the ODC platform. This issue prevented several customers from deploying applications through their expected deployment stages. We identified the root cause on June 29 and immediately implemented a fast-track fix. When further investigation revealed the issue persisted for additional customers due to a deeper underlying cause, we deployed a comprehensive fix on June 30 that fully resolved the problem across all affected tenants. All impacted customers have been verified as fully operational, and their applications can now be deployed normally through all stages.

Resolved: The incident has been resolved. The fix has been successfully applied across all affected regions, and we have verified that deployment pipelines are now operating with the correct stage ordering. We received direct confirmation from affected customers and have seen no further reports since the fix was implemented. We apologise for any disruption caused and thank you for your patience.

Monitoring: We have applied a solution to resolve the configuration issue affecting deployment pipelines across multiple regions. We are now monitoring the platform closely to ensure that application promotions are functioning correctly and that all systems have fully recovered.

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

Identified: We are continuing to work on implementing the fix for the configuration issue affecting deployment pipelines across multiple regions. While the mitigation actions are being executed, users may still experience issues promoting applications or see incorrect ordering in their deployment stages. We remain focused on resolving this as quickly as possible and will provide another update once the solution has been fully rolled out.

Identified: The root cause has been found and linked to a misconfigured code that was deployed recently, which was then used to update the environment configuration orders. Mitigation actions will be implemented soon. We appreciate your patience while the fix is being fully rolled out.

Investigating: We are currently investigating an issue where users are experiencing difficulties promoting applications through their deployment pipelines due to an incorrect ordering of deployment stages. This issue is affecting users across several regions. We are working to resolve the problem as quickly as possible and will provide updates as more information becomes available.

Postmortem: On June 26, 2026, a code deployment intended to improve our system's infrastructure inadvertently introduced a sorting issue that affected the deployment stage ordering on the ODC platform. This issue prevented several customers from deploying applications through their expected deployment stages. We identified the root cause on June 29 and immediately implemented a fast-track fix. When further investigation revealed the issue persisted for additional customers due to a deeper underlying cause, we deployed a comprehensive fix on June 30 that fully resolved the problem across all affected tenants. All impacted customers have been verified as fully operational, and their applications can now be deployed normally through all stages.

Resolved: The configuration issue affecting deployment pipeline stage ordering across multiple regions for ODC has been resolved. The fix has fully addressed both the primary issue identified on June 29th and a secondary edge case affecting users with custom environment names. Our team has completed the monitoring period, and all services are now operating as expected. We apologise for any disruption caused and thank you for your patience.

Monitoring: A fix has been implemented to address the configuration issue affecting deployment pipelines across multiple regions. We are now closely monitoring the platform to ensure application promotions are proceeding as expected and to confirm that all systems have fully recovered.

Identified: We are investigating a recurring issue where users are experiencing difficulties promoting applications through their deployment pipelines due to an incorrect ordering of deployment stages. This issue is currently affecting users across several regions.

Our team is actively working to resolve the problem as quickly as possible and will provide updates as more information becomes available.

Postmortem: On June 26, 2026, a code deployment intended to improve our system's infrastructure inadvertently introduced a sorting issue that affected the deployment stage ordering on the ODC platform. This issue prevented several customers from deploying applications through their expected deployment stages. We identified the root cause on June 29 and immediately implemented a fast-track fix. When further investigation revealed the issue persisted for additional customers due to a deeper underlying cause, we deployed a comprehensive fix on June 30 that fully resolved the problem across all affected tenants. All impacted customers have been verified as fully operational, and their applications can now be deployed normally through all stages.

Resolved: The incident has been resolved. The fix has been successfully applied across all affected regions, and we have verified that deployment pipelines are now operating with the correct stage ordering. We received direct confirmation from affected customers and have seen no further reports since the fix was implemented. We apologise for any disruption caused and thank you for your patience.

Monitoring: We have applied a solution to resolve the configuration issue affecting deployment pipelines across multiple regions. We are now monitoring the platform closely to ensure that application promotions are functioning correctly and that all systems have fully recovered.

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

Identified: We are continuing to work on implementing the fix for the configuration issue affecting deployment pipelines across multiple regions. While the mitigation actions are being executed, users may still experience issues promoting applications or see incorrect ordering in their deployment stages. We remain focused on resolving this as quickly as possible and will provide another update once the solution has been fully rolled out.

Identified: The root cause has been found and linked to a misconfigured code that was deployed recently, which was then used to update the environment configuration orders. Mitigation actions will be implemented soon. We appreciate your patience while the fix is being fully rolled out.

Investigating: We are currently investigating an issue where users are experiencing difficulties promoting applications through their deployment pipelines due to an incorrect ordering of deployment stages. This issue is affecting users across several regions. We are working to resolve the problem as quickly as possible and will provide updates as more information becomes available.

Postmortem: On June 26, 2026, a code deployment intended to improve our system's infrastructure inadvertently introduced a sorting issue that affected the deployment stage ordering on the ODC platform. This issue prevented several customers from deploying applications through their expected deployment stages. We identified the root cause on June 29 and immediately implemented a fast-track fix. When further investigation revealed the issue persisted for additional customers due to a deeper underlying cause, we deployed a comprehensive fix on June 30 that fully resolved the problem across all affected tenants. All impacted customers have been verified as fully operational, and their applications can now be deployed normally through all stages.

Resolved: The configuration issue affecting deployment pipeline stage ordering across multiple regions for ODC has been resolved. The fix has fully addressed both the primary issue identified on June 29th and a secondary edge case affecting users with custom environment names. Our team has completed the monitoring period, and all services are now operating as expected. We apologise for any disruption caused and thank you for your patience.

Monitoring: A fix has been implemented to address the configuration issue affecting deployment pipelines across multiple regions. We are now closely monitoring the platform to ensure application promotions are proceeding as expected and to confirm that all systems have fully recovered.

Identified: We are investigating a recurring issue where users are experiencing difficulties promoting applications through their deployment pipelines due to an incorrect ordering of deployment stages. This issue is currently affecting users across several regions.

Our team is actively working to resolve the problem as quickly as possible and will provide updates as more information becomes available.

Resolved: All customers impacted by this incident have been contacted and supported individually. While the Middle East region continues to be affected by the ongoing geopolitical situation and AWS continues to report the region as impacted, OutSystems has completed its direct response to every affected organization. The affected services remain flagged as a major outage while these conditions persist. Customers who need further assistance can contact OutSystems Support by raising a new ticket or continuing their existing case through Support Services.

Identified: Most affected O11 Cloud customers in the Middle East (Bahrain) region have been mitigated, and overall stability has improved. The AWS outage remains ongoing. We are continuing to actively monitor AWS updates to ensure full service recovery. Further updates will be provided directly to affected users via their individual support tickets. Customers requiring additional assistance are encouraged to contact OutSystems Support by raising a new ticket or following their existing cases through the Support Portal.

Identified: We are investigating reports of service disruption affecting O11 Cloud customer in the Middle East (Bahrain) region. We are currently reaching out to impacted customers directly and will provide further updates as more information becomes available.

Identified: Recovery efforts for the Middle East (UAE) remain ongoing as cloud infrastructure providers work to restore impacted services. ODC organizations remain unavailable while these restoration efforts continue. We are continuing tracking the recovery process of this incident to ensure a complete recovery. Going forward, updates will be delivered directly to affected users through their individual support tickets. Users who require further assistance with this event are encouraged to contact OutSystems Support by raising a new ticket or following their existing cases through the Support Portal.

Identified: Recovery efforts for the Middle East (UAE) remain ongoing as cloud infrastructure providers work to restore impacted services. ODC organizations remain unavailable while these restoration efforts continue. We are closely tracking the progress and will provide further updates as more information becomes available.

Identified: Recovery efforts for the Middle East (UAE) region remain ongoing as cloud infrastructure providers work to restore impacted services. We continue to track the recovery progress and will provide further updates as more information becomes available.

Identified: Recovery efforts are still underway for the Middle East (UAE) as cloud services work to restore one of the affected areas. We are continuing to track the progress and will provide further updates as more information becomes available.

Identified: We are continuing to monitor the recovery of ODC services in the Middle East (UAE) as the underlying infrastructure issues are being addressed. We will provide further updates as soon as more information becomes available.

Identified: Update - We are continuing to monitor the progress of recovery efforts in the affected region. We will provide further information as soon as more details become available.

Monitoring: Update - We are continuing to monitor the progress of recovery efforts in the affected region. We will provide further information as soon as more details become available.

Identified: Recovery efforts are still being prioritized by AWS for this region, focusing on restoration of the impacted AWS Services. We are closely monitoring the situation and will provide further updates once they become available.

Identified: The cause has been identified as a widespread infrastructure failure in the Middle East (UAE) affecting foundational AWS services. While recovery efforts are underway, ODC and other services in this region will remain unavailable until the underlying infrastructure is fully restored.

We are closely monitoring the situation as it recovers and will provide further information once it becomes available.

Investigating: We are still continuing to monitor the investigation with AWS, as the recovery towards the impaired AWS Middle East (UAE) Region is still ongoing. While there have been significant improvements made so far, the estimated recovery time will take at least another day before power and connectivity can be restored.

Investigating: We continue to follow closely the investigation in partnership with AWS, towards the recovery of the Middle East (UAE) Region. At this point, we are expecting recovery to take at least a day given the significant efforts required. Until then, ODC and other services in this region will continue experiencing a total service outage. We continue to monitor the situation closely and will provide updates as more information becomes available.

Investigating: We are investigating an issue affecting Outsystems Products in the Middle East (UAE) region. This disruption is related to the ongoing AWS service incident reported on March 1st.

Users in this region are currently experiencing a total service outage in ODC, and all services are unavailable. We are monitoring the situation closely and will provide updates as more information becomes available.

Investigating: We are currently investigating this issue.

Monitoring: Our services have been fully restored, and the issue affecting our OutSystems customers has been mitigated. While the ongoing disruption reported by AWS continues, it is not expected to impact our customers at this time. We will continue to closely monitor the situation. If you experience any issues, please contact our Support team.

For updates directly from AWS, please visit: https://health.aws.amazon.com/health/status

Identified: We are continuing to monitor the official AWS status page. At this time, AWS has informed customers that some may experience errors when performing certain network-related actions.

AWS is actively implementing mitigation measures, and recovery is expected within the next few hours.

Identified: AWS Team has identified the cause of the disruption affecting one availability zone in the Middle East (UAE) region. Power was temporarily shut down at the facility as a safety precaution.

Restoration of power and connectivity may take several hours. Other availability zones in the region remain operational.

We will provide further updates as more information becomes available.

Investigating: We are currently experiencing service degradation in the Middle East (UAE) region due to connectivity and power issues within a major cloud provider (AWS).

We are actively monitoring the situation and following updates from the official AWS status page. Our team is closely tracking recovery progress. We will provide further updates as more information becomes available.

Postmortem: On June 26, 2026, a code deployment intended to improve our system's infrastructure inadvertently introduced a sorting issue that affected the deployment stage ordering on the ODC platform. This issue prevented several customers from deploying applications through their expected deployment stages. We identified the root cause on June 29 and immediately implemented a fast-track fix. When further investigation revealed the issue persisted for additional customers due to a deeper underlying cause, we deployed a comprehensive fix on June 30 that fully resolved the problem across all affected tenants. All impacted customers have been verified as fully operational, and their applications can now be deployed normally through all stages.

Resolved: The incident has been resolved. The fix has been successfully applied across all affected regions, and we have verified that deployment pipelines are now operating with the correct stage ordering. We received direct confirmation from affected customers and have seen no further reports since the fix was implemented. We apologise for any disruption caused and thank you for your patience.

Monitoring: We have applied a solution to resolve the configuration issue affecting deployment pipelines across multiple regions. We are now monitoring the platform closely to ensure that application promotions are functioning correctly and that all systems have fully recovered.

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

Identified: We are continuing to work on implementing the fix for the configuration issue affecting deployment pipelines across multiple regions. While the mitigation actions are being executed, users may still experience issues promoting applications or see incorrect ordering in their deployment stages. We remain focused on resolving this as quickly as possible and will provide another update once the solution has been fully rolled out.

Identified: The root cause has been found and linked to a misconfigured code that was deployed recently, which was then used to update the environment configuration orders. Mitigation actions will be implemented soon. We appreciate your patience while the fix is being fully rolled out.

Investigating: We are currently investigating an issue where users are experiencing difficulties promoting applications through their deployment pipelines due to an incorrect ordering of deployment stages. This issue is affecting users across several regions. We are working to resolve the problem as quickly as possible and will provide updates as more information becomes available.

Postmortem: On June 26, 2026, a code deployment intended to improve our system's infrastructure inadvertently introduced a sorting issue that affected the deployment stage ordering on the ODC platform. This issue prevented several customers from deploying applications through their expected deployment stages. We identified the root cause on June 29 and immediately implemented a fast-track fix. When further investigation revealed the issue persisted for additional customers due to a deeper underlying cause, we deployed a comprehensive fix on June 30 that fully resolved the problem across all affected tenants. All impacted customers have been verified as fully operational, and their applications can now be deployed normally through all stages.

Resolved: The configuration issue affecting deployment pipeline stage ordering across multiple regions for ODC has been resolved. The fix has fully addressed both the primary issue identified on June 29th and a secondary edge case affecting users with custom environment names. Our team has completed the monitoring period, and all services are now operating as expected. We apologise for any disruption caused and thank you for your patience.

Monitoring: A fix has been implemented to address the configuration issue affecting deployment pipelines across multiple regions. We are now closely monitoring the platform to ensure application promotions are proceeding as expected and to confirm that all systems have fully recovered.

Identified: We are investigating a recurring issue where users are experiencing difficulties promoting applications through their deployment pipelines due to an incorrect ordering of deployment stages. This issue is currently affecting users across several regions.

Our team is actively working to resolve the problem as quickly as possible and will provide updates as more information becomes available.

Postmortem: On June 26, 2026, a code deployment intended to improve our system's infrastructure inadvertently introduced a sorting issue that affected the deployment stage ordering on the ODC platform. This issue prevented several customers from deploying applications through their expected deployment stages. We identified the root cause on June 29 and immediately implemented a fast-track fix. When further investigation revealed the issue persisted for additional customers due to a deeper underlying cause, we deployed a comprehensive fix on June 30 that fully resolved the problem across all affected tenants. All impacted customers have been verified as fully operational, and their applications can now be deployed normally through all stages.

Resolved: The incident has been resolved. The fix has been successfully applied across all affected regions, and we have verified that deployment pipelines are now operating with the correct stage ordering. We received direct confirmation from affected customers and have seen no further reports since the fix was implemented. We apologise for any disruption caused and thank you for your patience.

Monitoring: We have applied a solution to resolve the configuration issue affecting deployment pipelines across multiple regions. We are now monitoring the platform closely to ensure that application promotions are functioning correctly and that all systems have fully recovered.

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

Identified: We are continuing to work on implementing the fix for the configuration issue affecting deployment pipelines across multiple regions. While the mitigation actions are being executed, users may still experience issues promoting applications or see incorrect ordering in their deployment stages. We remain focused on resolving this as quickly as possible and will provide another update once the solution has been fully rolled out.

Identified: The root cause has been found and linked to a misconfigured code that was deployed recently, which was then used to update the environment configuration orders. Mitigation actions will be implemented soon. We appreciate your patience while the fix is being fully rolled out.

Investigating: We are currently investigating an issue where users are experiencing difficulties promoting applications through their deployment pipelines due to an incorrect ordering of deployment stages. This issue is affecting users across several regions. We are working to resolve the problem as quickly as possible and will provide updates as more information becomes available.

Resolved: All customers impacted by this incident have been contacted and supported individually. While the Middle East region continues to be affected by the ongoing geopolitical situation and AWS continues to report the region as impacted, OutSystems has completed its direct response to every affected organization. The affected services remain flagged as a major outage while these conditions persist. Customers who need further assistance can contact OutSystems Support by raising a new ticket or continuing their existing case through Support Services.

Identified: Most affected O11 Cloud customers in the Middle East (Bahrain) region have been mitigated, and overall stability has improved. The AWS outage remains ongoing. We are continuing to actively monitor AWS updates to ensure full service recovery. Further updates will be provided directly to affected users via their individual support tickets. Customers requiring additional assistance are encouraged to contact OutSystems Support by raising a new ticket or following their existing cases through the Support Portal.

Identified: We are investigating reports of service disruption affecting O11 Cloud customer in the Middle East (Bahrain) region. We are currently reaching out to impacted customers directly and will provide further updates as more information becomes available.

Identified: Recovery efforts for the Middle East (UAE) remain ongoing as cloud infrastructure providers work to restore impacted services. ODC organizations remain unavailable while these restoration efforts continue. We are continuing tracking the recovery process of this incident to ensure a complete recovery. Going forward, updates will be delivered directly to affected users through their individual support tickets. Users who require further assistance with this event are encouraged to contact OutSystems Support by raising a new ticket or following their existing cases through the Support Portal.

Identified: Recovery efforts for the Middle East (UAE) remain ongoing as cloud infrastructure providers work to restore impacted services. ODC organizations remain unavailable while these restoration efforts continue. We are closely tracking the progress and will provide further updates as more information becomes available.

Identified: Recovery efforts for the Middle East (UAE) region remain ongoing as cloud infrastructure providers work to restore impacted services. We continue to track the recovery progress and will provide further updates as more information becomes available.

Identified: Recovery efforts are still underway for the Middle East (UAE) as cloud services work to restore one of the affected areas. We are continuing to track the progress and will provide further updates as more information becomes available.

Identified: We are continuing to monitor the recovery of ODC services in the Middle East (UAE) as the underlying infrastructure issues are being addressed. We will provide further updates as soon as more information becomes available.

Identified: Update - We are continuing to monitor the progress of recovery efforts in the affected region. We will provide further information as soon as more details become available.

Monitoring: Update - We are continuing to monitor the progress of recovery efforts in the affected region. We will provide further information as soon as more details become available.

Identified: Recovery efforts are still being prioritized by AWS for this region, focusing on restoration of the impacted AWS Services. We are closely monitoring the situation and will provide further updates once they become available.

Identified: The cause has been identified as a widespread infrastructure failure in the Middle East (UAE) affecting foundational AWS services. While recovery efforts are underway, ODC and other services in this region will remain unavailable until the underlying infrastructure is fully restored.

We are closely monitoring the situation as it recovers and will provide further information once it becomes available.

Investigating: We are still continuing to monitor the investigation with AWS, as the recovery towards the impaired AWS Middle East (UAE) Region is still ongoing. While there have been significant improvements made so far, the estimated recovery time will take at least another day before power and connectivity can be restored.

Investigating: We continue to follow closely the investigation in partnership with AWS, towards the recovery of the Middle East (UAE) Region. At this point, we are expecting recovery to take at least a day given the significant efforts required. Until then, ODC and other services in this region will continue experiencing a total service outage. We continue to monitor the situation closely and will provide updates as more information becomes available.

Investigating: We are investigating an issue affecting Outsystems Products in the Middle East (UAE) region. This disruption is related to the ongoing AWS service incident reported on March 1st.

Users in this region are currently experiencing a total service outage in ODC, and all services are unavailable. We are monitoring the situation closely and will provide updates as more information becomes available.

Investigating: We are currently investigating this issue.

Monitoring: Our services have been fully restored, and the issue affecting our OutSystems customers has been mitigated. While the ongoing disruption reported by AWS continues, it is not expected to impact our customers at this time. We will continue to closely monitor the situation. If you experience any issues, please contact our Support team.

For updates directly from AWS, please visit: https://health.aws.amazon.com/health/status

Identified: We are continuing to monitor the official AWS status page. At this time, AWS has informed customers that some may experience errors when performing certain network-related actions.

AWS is actively implementing mitigation measures, and recovery is expected within the next few hours.

Identified: AWS Team has identified the cause of the disruption affecting one availability zone in the Middle East (UAE) region. Power was temporarily shut down at the facility as a safety precaution.

Restoration of power and connectivity may take several hours. Other availability zones in the region remain operational.

We will provide further updates as more information becomes available.

Investigating: We are currently experiencing service degradation in the Middle East (UAE) region due to connectivity and power issues within a major cloud provider (AWS).

We are actively monitoring the situation and following updates from the official AWS status page. Our team is closely tracking recovery progress. We will provide further updates as more information becomes available.