Announcing Required Changes for Customers Who Use the LiveRamp SFTP (5/21/19)
LiveRamp is in the process of making technical improvements to the backend of our platform, which includes a migration of the infrastructure where we process your data from a managed data center to Google Cloud Platform (GCP). See “Announcing LiveRamp’s Infrastructure Improvements (5/21/19)” for complete information.
As a result of the migration, our SFTP server’s IP address and domain name have changed and as of August 16, 2019 we no longer support the previous domain (sftp.liveramp.com). All customers who upload or download files via the LiveRamp SFTP must update this information to prevent any disruption to service.
Caution
Customers who receive files into their own SFTP and customers who use the domain sftp.pippio.com for SFTP uploads or downloads do not need to make any changes.
If you use a firewall that allows you to allowlist trusted IP addresses for file transfers, update the LiveRamp SFTP IP address:
Previous IP address: 139.61.75.249
New IP address: 35.202.130.160
When connecting to the LiveRamp SFTP, use the updated domain name:
Previous domain name: sftp.liveramp.com
New domain name: files.liveramp.com
Once you've made the required updates, fill out this survey so we know you've made the changes.
While you can temporarily continue to upload or download files via the LiveRamp SFTP with the current IP address and domain name, we’re aiming to have all customers make these updates by August 15, 2019 in order to prevent any future disruption to SFTP file uploads or downloads.
See “Upload a File via LiveRamp's SFTP” for updated SFTP upload instructions.
FAQs
What will change in the SFTP upload or download process once I make the update?
If the update is completed successfully, you will not see any other changes in how you upload or download files via the LiveRamp SFTP.
What is the level of effort required to make these updates?
These updates should not require a significant amount of time or resources to complete. If you use a firewall that allows you to allowlist trusted IP addresses for file transfers, your IT or Technical Ops lead will need to update your firewall settings to include the new IP address. Additionally, your SFTP-credentialed user will need to update the domain name in your SFTP client application (or at the command line if you use this for uploads or downloads).
If our company doesn’t upload or download files using the LiveRamp SFTP (i.e., we use an S3 bucket for uploads or we receive files into our SFTP server), do we need to change anything about how we upload or download files?
No.
If our company receives files from LiveRamp into our own SFTP, do we need to make any SFTP changes?
No.
If our company uploads via SFTP to the domain sftp.pipio.com do we need to make any SFTP changes?
No.
Other than the changes for customers who use the LiveRamp SFTP, will there be any other changes that we will need to make in how we interact with LiveRamp after the migration is complete?
No. All of the changes will be on the backend and will not change how you interact with LiveRamp.