[Scheduled][IBM-Aspera] - [AoC:API] - Change Notification - IP ranges for api.ibmaspera.com
Scheduled Maintenance Report for IBM-Aspera Service Status
The scheduled maintenance has been completed.
Posted Jan 21, 2022 - 17:00 PST
In progress
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted Jan 21, 2022 - 16:00 PST
On January 22, 2022, Aspera on Cloud (AoC) will be changing to use the Akamai Network in front of the AoC API and Frontend. This will require that customers update their firewall rules if they have them in place. If your organization has a Trust List in place for our currently published IP range (https://ibmaspera.com/help/admin/nodes/2_tethered_firewall) for your users to access AoC, you will need to change it to no longer trust just the IP range. We will no longer be able to publish IP ranges for client-to-server communication for the AoC API and Frontend. You will need to configure your firewall to trust the hostname of "api.ibmaspera.com" and ".ibmaspera.com", both on port 443. For those customers who are using the legacy "api.asperafiles.com" endpoint for API clients, you will need to update your firewall rules in the same matter as well.

The published range for allowing communication from AoC to tethered nodes will remain the same.
The published ranges for allowing communication to managed nodes or ATS clusters will also remain the same.

All customers who are using entitlements for their on-premise HSTS installations should also be aware that asperalee needs to communicate to the AoC API for entitlement information, even if you are not an AoC customer. So if a firewall exists in your network configuration to trust the AoC API range, that will need to be changed.
Posted Nov 15, 2021 - 14:26 PST
This scheduled maintenance affected: IBM-Aspera API Services (api.ibmaspera.com).