As part of iPipeline's ongoing investment in improving the performance, scalability, reliability, and security of its authentication services, the Ping infrastructure is being migrated to Amazon Web Services (AWS).
This migration introduces new network endpoints that may require updates to customer firewall rules, IP allowlists, proxy servers, Web Application Firewalls (WAFs), and other network security controls.
*Customer Action Required* Customers who restrict access using IP allowlists or other network security controls should review and update their configurations as soon as possible to ensure uninterrupted access to iPipeline services following the Production migration.
*Important* - New AWS IP addresses must be added and must not replace existing Ping IP addresses. - Existing approved Ping IP addresses must remain in place until iPipeline provides formal notice that they can be removed. - Customers who have not yet completed the required network updates should prioritize these changes before the Production cutover date.
*Key Dates* - September 1, 2026 – Customer readiness deadline for completing required network and IP allowlist updates. - September 18, 2026 – UAT environment successfully migrated to the AWS-hosted Ping infrastructure. - November 6, 2026 – Production environment migration to the AWS-hosted Ping infrastructure.
*Urgent Reminder* If you have not yet completed the required network and allowlist updates, please do so as soon as possible.
Customers that have not implemented the required changes prior to the November 6, 2026 Production cutover may experience authentication failures, connectivity issues, application access disruptions, or impacts to Single Sign-On (SSO) integrations once traffic begins routing through the AWS-hosted Ping infrastructure.
Completing these updates in advance will help ensure uninterrupted access to Ping authentication services both during and after the migration.
*Potentially Impacted Services* This change may impact applications and integrations that rely on Ping authentication, including but not limited to:
iGO® Illustrations (Sammons) Resonant® DocFast® Quote (LifePipe and iSolve®) FormsPipe AdminPipe iService Content Suite Single Sign-On (SSO) integrations PingFederate and PingAccess-protected services Carrier and vendor integrations using Ping authentication services Other applications and services that authenticate through iPipeline's Ping infrastructure
*Technical Details* The complete list of current and new IP addresses, implementation guidance, FAQs, and supporting documentation can be found on the iPipeline Customer Portal: