Yesterday, April 15, 2026, we identified a delay in our nightly integration sync processing. Sync jobs are continuing to process, but at a slower rate than expected. We have taken steps to address the issue and are actively monitoring progress. If you do not see expected account creations or updates in your system by the end of today, please contact our support team for assistance. We appreciate your patience and will provide an update once processing has returned to normal.
Last update on
Monitoring AWS ME-Central-1 region incident. Waiting for AWS resolution. Services may be impacted. Updates to follow.
Last update on
We are providing an update on the ongoing service disruptions affecting the AWS Middle East (Bahrain) Region (ME-SOUTH-1). We continue to make progress on recovery efforts across multiple workstreams. With the immediate phase of this event now better understood, we are moving to a more targeted communication model. Going forward, updates will be delivered directly to affected customers through the AWS Personal Health Dashboard. Customers who require assistance with this event are encouraged to contact AWS Support through the AWS Management Console or the AWS Support Center. We continue to strongly recommend that customers with workloads running in the Middle East take action now to migrate those workloads to alternate AWS Regions. Customers should enact their disaster recovery plans, recover from remote backups stored in other Regions, and update their applications to direct traffic away from the affected Regions. For customers requiring guidance on alternate regions, we recommend considering AWS Regions in the United States, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements.
Last update on
Monitors
Magnus Health
Selective Cloud Orchestrators are affected on ME-Central-1 (UAE)
Aruba Networks
Increased Connectivity Issues and API Error Rates
Amazon Web Services
StatusGator