Our team continues to actively work with X to address all known issues. We will continue to provide updates as soon as new information becomes available. Next update will be on Wednesday, June 24th.
Last update on
We are still investigating the issue for the listed services.
Last update on
We are providing an update on the ongoing service disruption. The Middle East (UAE) Region (ME-CENTRAL-1) has suffered damage as a result of the conflict in the Middle East and is currently unable to reliably support customer applications. While some workloads continue to function normally, we strongly recommend customers migrate all accessible resources to other Regions and restore inaccessible resources from remote backups as soon as possible. Relevant billing operations are currently suspended while we restore normal operations in this AWS Region. This process is expected to take several months.
Last update on
The fix is still in progress and being deployed. We will provide an update upon resolution.
Last update on
Jira and JSM customers using Microsoft OAuth for automatic creation of Jira tickets from email were unable to read email. This is now fixed and functional for all new incoming email processing. The impacted customers during the incident period need to re-authorise the Microsoft mail server to restore and below are the instructions. To re-authorise an incoming Microsoft mail server: Login in Jira as Admin Select > System Select Mail > Incoming Mail. Select Edit incoming mail server. Select re-authorise . Enter your Microsoft credentials to continue using your Microsoft mail server.
Last update on
Jira and JSM customers using Microsoft OAuth for automatic creation of Jira tickets from email were unable to read email. This is now fixed and functional for all new incoming email processing. The impacted customers during the incident period need to re-authorise the Microsoft mail server to restore and below are the instructions. To re-authorise an incoming Microsoft mail server: Login in Jira as Admin Select > System Select Mail > Incoming Mail. Select Edit incoming mail server. Select re-authorise . Enter your Microsoft credentials to continue using your Microsoft mail server.
Last update on
**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.
Last update on
We are actively working on a fix. Thank you for your understanding as we work to resolve this issue.
Last update on
We continue to make progress toward restoring services and remain in close coordination with our third-party infrastructure provider as recovery efforts continue. The impact remains limited to customers with sandbox environments on a subset of instances, and there is no impact to production environments. We'll provide further updates upon significant developments or sooner as new information becomes available.
Last update on
The monitor is down in the following regions: us-east and us-west
Last update on
We continue to make progress toward restoring services and remain in close coordination with our third-party infrastructure provider as recovery efforts continue. The impact remains limited to customers with sandbox environments on a subset of instances, and there is no impact to production environments. We'll provide further updates upon significant developments or sooner as new information becomes available.
Last update on
Monitors
Amazon Web Services
Jira : Incoming emails partial outage
Jira Service Desk
Scheduled Maintenance; OCR slowness; Nexonia Sign-in page not loading and throwing a "504 Gateway Time Out" Error
Nexonia
Could not connect to https://static.jamasoftware.com: Couldn't resolve host name
static.jamasoftware.com
Tableau Cloud
Microsoft 365 suite
Adobe Creative Cloud
dev.jamasoftware.com
rest.jamasoftware.com
velocity.jamasoftware.com
StatusGator