Overview
When iPaaS.com syncs data, it calls your connected systems' APIs from a fixed set of outbound IP addresses. If a system sits behind a firewall, or its API only accepts requests from approved IP addresses, those calls are blocked until the iPaaS.com addresses are allowed.
Common signs that iPaaS.com traffic is being blocked:
The subscription connection test fails or times out.
Transfers fail with timeout,
401 Unauthorized, or403 Forbiddenerrors even though the credentials are correct.Polling returns no data from a system that has new records.
iPaaS.com Outbound IP Addresses
Allow inbound traffic from both of the following addresses to the API or service your integration connects to:
IP Address | Description |
| iPaaS.com production outbound address ( |
| iPaaS.com datacenter address |
NOTE: 69.61.66.130 is part of the iPaaS.com datacenter range 69.61.66.128/27. Some integration-specific articles list the full range. Allowing the single address is sufficient for most environments, and allowing the full range is also acceptable.
Retired address: 52.184.255.108 was the iPaaS.com outbound address before an infrastructure update and is no longer in use. If your firewall or allowlist still includes it, replace it with 20.98.221.25.
Who Should Do This
Whitelisting is configured in the external system, not in iPaaS.com. The subscriber's system administrator or IT provider is responsible for adding these addresses to the firewall, network security group, or API allowlist that protects the system.
When You Need to Whitelist
On-premises systems: ERP, POS, or database servers hosted on your own network (for example, Microsoft Dynamics NAV, NCR Counterpoint, or Syspro).
Cloud APIs with IP restrictions: SaaS platforms that let you limit API access to approved IP addresses.
Corporate firewalls and proxies: Networks that block inbound traffic from unknown sources by default.
How to Whitelist iPaaS.com
Exact steps vary by firewall and platform. The general process is:
Locate the firewall rule, security group, or API allowlist setting that controls access to the system.
Add an inbound allow rule for each iPaaS.com IP address listed above.
Scope the rule to the port and service the integration uses (typically HTTPS on port 443, or the custom port in your subscription's API URL).
Save and apply the rule.
In iPaaS.com, re-test the subscription connection, then resync a single record to confirm data flows.
For a Windows Firewall example, see the whitelisting section of Microsoft Dynamics NAV Installation Instructions.
Troubleshooting
Still blocked after whitelisting: Confirm the rule applies to the correct port and network profile, and that no upstream firewall or proxy is also filtering traffic.
Connections stopped working after an iPaaS.com infrastructure update: Check whether your allowlist still uses the retired address
52.184.255.108and replace it with20.98.221.25.