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.
The issue has been identified and a fix is being implemented.
We are continuing to work with our underlying provider to address the subset of remaining devices that are showing offline. We will keep you informed with timely updates as progress is made. Thank you for your patience.
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.
Inherited Conditions Making Course Links Inaccessible or Visible & Impact to Other Content Items in a Course A fix introduced in the August release (4000.21.0) caused unintended issues with course links for institutions depending on how their course content is designed or structured. We reverted this fix, which means Discussions and similar items linked in areas like the Gradebook or Discussions tab may again appear outside their intended release conditions. Reference the support article for more details: https://support.anthology.com/s/article/Discussion-Forum-or-other-Assessment-Visible-in-Course-with-Inherited-Release-Conditions
LTI/SFTP integrations with Apex Learning and MajorClarity have been reset. Customers that have not already received updated credentials can contact customersupport@edmentum.com to get their integration reconnected.
Students may be experiencing an issue with a recent ChromeOS LTS version 144.0.7559.257 that prevents Core5, PowerUp, and Lexia English from operating properly on affected devices. The recommended resolution is a minor update to ChromeOS version 144.0.7559.258 or a later version. This update includes a fix that has resolved the issue for devices that have been updated.
Monitors
Amazon Web Services 2
Amazon Web Services
Blackboard LMS: Discussion Forum or other Assessment Visible in Course with Inherited Release Conditions
Blackboard
Edmentum
Houghton Mifflin Harcourt