Global Microsoft 365 Outage – Impacting iPipeline Business Email Communications
Identified - Due to the ongoing global Microsoft 365 outage, iPipeline's ability to send and receive business emails to and from customers is impacted. As a result, you may experience delays or may not receive emails sent from our teams.

Please note that this issue does not impact emails sent directly from our applications, such as iGO, DocFast, etc. These application-generated emails continue to function as expected.

Our team is closely monitoring Microsoft's updates and will share further information as it becomes available.

- iPipeline Support
Nov 12, 2026 - 15:37 EST
Uptime over the past 90 days. View historical uptime.
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 Operational
WealthServ Investments Operational
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.

No incidents or maintenance related to this downtime.

Nov 12, 2026

Unresolved incident: Global Microsoft 365 Outage – Impacting iPipeline Business Email Communications.

Nov 11, 2026

iGO and DocFast - AlphaTrust e-Signature Issue
Resolved - The signing issue in Alpha Trust has been resolved. Users should now be able to successfully progress through and complete the signing process.

- The iPipeline Support Team
Nov 11, 15:55 EST
Investigating - We are currently receiving reports that users are receiving eSignature failures while using the AlphaTrust solution. We are investigating this issue and further updates will be provided as we have more details.

- The iPipeline Support Team
Nov 11, 15:32 EST

Nov 10, 2026

No incidents reported.

Nov 9, 2026

No incidents reported.

Nov 8, 2026

No incidents reported.

Nov 7, 2026

PING AWS Migration - Production
Completed - The scheduled maintenance has been completed.
Nov 7, 00:00 EST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Nov 6, 21:30 EST
Scheduled - 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:

*Migration Information*
https://customerportal.ipipeline.com/ping-2026-aws-migration/#BlueBanner

*Frequently Asked Questions (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.

Thank you for your continued partnership and support as we complete this important infrastructure modernization initiative.
Oct 6, 11:26 EDT

Nov 6, 2026

Nov 5, 2026

No incidents reported.

Nov 4, 2026

Intermittent Email Delays - Various Applications
Resolved - Our team has implemented changes to address the email delivery delays, and we are no longer observing delays in email processing or delivery.

Service has stabilized, and email traffic is flowing as expected. The team will continue to closely monitor the environment to ensure ongoing stability and will work with our service providers to help prevent similar issues in the future.
Nov 4, 13:02 EST
Update - We are no longer observing delays in email delivery and email processing is currently operating as expected.

While our investigation remains ongoing, we have identified areas of focus and continue to work with our vendor to better understand the conditions that may have contributed to the intermittent delays.
Nov 4, 00:02 EST
Update - We are actively working with our email vendor to confirm the cause and resolve the issue. We have also investigated interim solutions that we hope will help reduce the impact while the root cause is fully determined and addressed. At this time, we are still evaluating whether those measures will be successful.

The delays we are observing are generally measured in minutes rather than hours, though some emails may experience delays of approximately 30 minutes. The issue is intermittent and does not affect all emails, so some users may not experience any impact.

We will continue to closely monitor the situation and expect to provide another update tomorrow morning, November 4.
Nov 3, 17:59 EST
Investigating - We have received reports that some emails generated by some of our applications, including iGO, are delayed in delivery. Our team is actively investigating the issue and working to restore normal email delivery as quickly as possible.

We will provide additional updates as more information becomes available.
Nov 3, 15:55 EST

Nov 3, 2026

Nov 2, 2026

No incidents reported.

Nov 1, 2026

No incidents reported.

Oct 31, 2026

No incidents reported.

Oct 30, 2026

No incidents reported.

Oct 29, 2026

No incidents reported.

Incident History Powered by Atlassian Statuspage