Jama IT Dashboard

We are providing an update on the disruption affecting the Middle East (UAE) (me-central-1) Region. After a thorough assessment, we have determined that we are unable to restore access to the resources and data hosted exclusively in the mec1-az2 Availability Zone. We continue to work on recovering regional resources, as well as zonal resources hosted in the other affected Availability Zones (mec1-az1 and mec1-az3). Since the disruption began in March, most customers have been able to re-establish their operations in other Regions by restoring backups or copying data that remained accessible. AWS Support remains available to help customers who need assistance moving their applications to alternate Regions. We remain committed to supporting our customers in the UAE. We are working on replacing the affected infrastructure and will provide an update on the restoration of our services in the coming months. We have notified the relevant authorities and continue to work with them toward that goal.

We have identified a potential cause of this issue and are deploying a fix.

We're investigating an issue causing Gong Enrich to be unavailable. Our teams are aware and working on it. We'll provide another update as soon as we have more information

**Investigating** We are currently investigating an issue affecting OCR Processing Some customers may experience service unavailability, or slower OCR processing times. Our engineering team is actively investigating the issue and working to restore normal service as quickly as possible. We will provide the next update within 60 minutes, or sooner if additional information becomes available. Thank you for your patience and understanding. Mitigated The issue affecting access to Nexonia has been mitigated, and service has been restored. Between 13:35 UTC and 14:17 UTC, customers were unable to access their Nexonia accounts due to the Nexonia Sign-in page failing to load and returning 504 Gateway Timeout errors. During this period, both the nexonia-na1 and nexonia-na2 services experienced degraded performance, preventing users from successfully authenticating. The incident affected all customers attempting to sign in through the Nexonia Sign-in page and resulted in approximately 42 minutes of service unavailability for authentication-related access. Our team implemented mitigation measures and restored normal service at 14:17 UTC. We are continuing to monitor the environment to ensure stability and are conducting post-incident review activities to determine the underlying cause and identify any additional preventative actions. We apologize for the disruption and appreciate your patience while we worked to resolve the issue. Service has returned to normal operating levels, and we are continuing to monitor the system to ensure stability. We appreciate your patience and understanding while we worked to resolve this matter.

The service continues to perform as expected and remains under close monitoring. Should customers experience any issues, they are advised to contact Customer Services.

We identified the potential cause of the issue and are working on implementing a fix to resolve the impact to customers. We will provide an update every 2 days or sooner if we have more information

The monitor is down in the following regions: us-east and us-west

We identified the potential cause of the issue and are working on implementing a fix to resolve the impact to customers. We will provide an update every 2 days or sooner if we have more information