In many cases, customers and carriers have implemented IP filters on traffic going out or coming in. Here are the IP addresses to open in firewalls for our traffic.
1. Customers restricting outbound traffic
Use case: Customer restricts traffic to known external partners only.
Below are the 2 IP addresses that you will need to allow.
| Environment | IP addresses |
|---|---|
| accept | 52.223.58.16 and 35.71.186.39 |
| prod | 13.248.222.228 and 76.223.87.97 |
2. Customers restricting inbound traffic
Use case: Customers using streamed statuses and customers who want their Jasper report to be pushed to their FTP server.
| Environment | IP address |
|---|---|
| accept | 54.246.58.232 |
| prod | 54.217.101.135 |
3. Carriers restricting inbound traffic
Use case: Some carriers restrict access to resources on their end, typically an FTP server, based on IP address. For example, this can apply when we put manifest files on their server or pull status files.
The IP addresses that need to be whitelisted by the carrier are the same as for customer-streamed statuses:
| Environment | IP address |
|---|---|
| test | 54.170.28.127 |
| accept | 54.246.58.232 |
| prod | 54.217.101.135 |
4. Carriers restricting outbound traffic
Use case: There are two ways for carriers to connect to our servers to send shipment status updates:
- Data file upload to our SFTP server
- Status push over HTTPS
In both cases, the carrier might be using IP whitelisting.
| Environment | IP addresses |
|---|---|
| accept | No server available |
| prod | 99.81.35.6 for FTP and 76.223.87.97 for HTTPS |