Update - While monitoring the issue, the Team has identified some emails being processed multiple times which is delaying email processing for some Customers.
The duplicate processing has been addressed and the Team continues to closely monitor the system to ensure processing remains stable and delayed emails are successfully processed.
Any duplication will be addressed once delayed emails are processed.
--The iPipeline Team
Sep 03, 2026 - 10:21 EDT
The duplicate processing has been addressed and the Team continues to closely monitor the system to ensure processing remains stable and delayed emails are successfully processed.
Any duplication will be addressed once delayed emails are processed.
--The iPipeline Team
Sep 03, 2026 - 10:21 EDT
Monitoring - A fix was deployed to production to day afternoon, and we have observed that email processing has resumed successfully and messages are currently being processed normally.
Our team continues to closely monitor the system to ensure processing remains stable and completes as expected.
--The iPipeline Team
Sep 02, 2026 - 18:55 EDT
Our team continues to closely monitor the system to ensure processing remains stable and completes as expected.
--The iPipeline Team
Sep 02, 2026 - 18:55 EDT
Identified - We have identified the issue that is delaying processing of emails in WealthServ and are working on a resolution.
A further update will be provided as soon as one is available.
--The iPipeline Team
Sep 01, 2026 - 13:18 EDT
A further update will be provided as soon as one is available.
--The iPipeline Team
Sep 01, 2026 - 13:18 EDT
Investigating - We are currently investigating an issue with email processing services in WealthServ. At this time Customer emails within the system are delayed in processing.
A further update will be provided as soon as one is available.
--The iPipeline Team
Sep 01, 2026 - 11:14 EDT
A further update will be provided as soon as one is available.
--The iPipeline Team
Sep 01, 2026 - 11:14 EDT
AFFIRM for Annuities
Operational
AFFIRM for Life
Operational
Agency Integrator
Operational
AlphaTrust - Embedded
Operational
AlphaTrust - SaaS
Operational
Data Feeds
Operational
DocFast
Operational
FormsPipe
Operational
IFS
Operational
iGO
Operational
iGO Client Collaboration
Operational
Illustrations
Operational
InsureSight
Operational
Laser App
Operational
Quote
Operational
Portals and Tools
Operational
Resonant
Operational
WealthServ Insurance
Degraded Performance
WealthServ Investments
Degraded Performance
XRAE
Operational
XRAE Lite
Operational
iGO Evolve
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Scheduled Maintenance
Ping AWS Migration – UAT Sep 18, 2026 21:30 - Sep 19, 2026 00:00 EDT
As part of iPipeline's ongoing investment in improving the performance, scalability, reliability, and security of its authentication services, the Ping Identity infrastructure is being migrated to AWS. This migration introduces new network endpoints that may require updates to customer firewall, allowlist, proxy, WAF, and other network security configurations.
Customer Action Required:
Customers who restrict access using IP allowlists or other network security controls should review and update their configurations before the deadline below.
Important:
New AWS IP addresses must be added and must not replace existing Ping Identity IP addresses.
Existing approved Ping Identity IP addresses must remain in place until iPipeline provides formal notice that they can be removed.
Key Dates:
- September 1, 2026 – Deadline for customers to complete required network and allowlist updates. This is a customer readiness date and not the production migration date.
- September 18, 2026 - 10:30PM to 12:00AM EST – UAT environment migration to AWS.
- Production Cutover Date – To be confirmed. iPipeline will communicate the confirmed production migration date at least 30 days in advance to allow customers sufficient time for planning and preparation.
Urgent Reminder:
If you have not yet completed the required network and allowlist updates, please do so as soon as possible. Customers who have not implemented the required changes before the UAT and Production cutover may experience service interruptions when the migration to AWS is completed. Completing these updates now will help ensure uninterrupted access to Ping authentication services throughout 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
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.
Information: https://customerportal.ipipeline.com/ping-2026-aws-migration/#BlueBanner
FAQ: https://customerportal.ipipeline.com/faq/ping-2026-aws-migration-faqs/#BlueBanner
Need Assistance?
If you have any questions or require assistance, please contact your iPipeline Customer Success Manager.
Posted on Sep 02, 2026 - 10:55 EDT
Customer Action Required:
Customers who restrict access using IP allowlists or other network security controls should review and update their configurations before the deadline below.
Important:
New AWS IP addresses must be added and must not replace existing Ping Identity IP addresses.
Existing approved Ping Identity IP addresses must remain in place until iPipeline provides formal notice that they can be removed.
Key Dates:
- September 1, 2026 – Deadline for customers to complete required network and allowlist updates. This is a customer readiness date and not the production migration date.
- September 18, 2026 - 10:30PM to 12:00AM EST – UAT environment migration to AWS.
- Production Cutover Date – To be confirmed. iPipeline will communicate the confirmed production migration date at least 30 days in advance to allow customers sufficient time for planning and preparation.
Urgent Reminder:
If you have not yet completed the required network and allowlist updates, please do so as soon as possible. Customers who have not implemented the required changes before the UAT and Production cutover may experience service interruptions when the migration to AWS is completed. Completing these updates now will help ensure uninterrupted access to Ping authentication services throughout 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
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.
Information: https://customerportal.ipipeline.com/ping-2026-aws-migration/#BlueBanner
FAQ: https://customerportal.ipipeline.com/faq/ping-2026-aws-migration-faqs/#BlueBanner
Need Assistance?
If you have any questions or require assistance, please contact your iPipeline Customer Success Manager.
Posted on Sep 02, 2026 - 10:55 EDT