Live Status\Incident History\Asset source, proxy download & upload via Aspera fails

Minor outage

Asset source, proxy download & upload via Aspera fails

  • Resolved

    We received the following root-cause analysis from IBM (who run Aspera on Cloud of which Media Room is a client): > Following a recent application update, newly provisioned hosts were not correctly configured with the required SSH fingerprint due to a failure in the Ansible automation responsible for applying this configuration. As a result, some customers experienced connection issues when attempting to access these new nodes, while existing hosts remained unaffected. > > To quickly mitigate customer impact, we reverted traffic to the previous stable environment while investigating the issue. The root cause was identified as a gap in configuration validation during the provisioning process, which allowed hosts to be deployed without the required SSH fingerprint. The issue has since been corrected, and additional safeguards—such as post-provisioning validation and improved deployment checks—are being implemented to ensure critical configurations are consistently applied and verified before release.

  • Resolved

    No further errors reported from Aspera on cloud. We are in contact with IBM (who own and run the Aspera service) to get a root cause analysis.

  • Monitoring

    We are not receiving any more error reports when doing transfers via Aspera. We continue to monitor the issue with Aspera. Aspera confirm they made a configuration change in their hosted Aspera service which may have resolved the issue.

  • Monitoring

    Aspera have implemented a configuration change which has seen some transfers succeeding. Some Aspera transfers continue to fail intermittently. We are monitoring and continuing to work with Aspera on the issue.

  • Identified

    Aspera confirm the issue - we are working with Aspera to resolve it.

  • Identified

    Transfers via Aspera fail to start with the error "Remote host is not who we expected". We are lodging a case with Aspera support and will report any updates.