iPipeline Outage History

Started Dec 16, 2025, 06:21 PM UTC· resolved Dec 16, 2025, 08:53 PM UTC

1. investigating Dec 16, 2025, 06:21 PM UTC

   We are currently investigating an issue affecting InsureSight report scheduling and report exports. At this time, users are still able to generate and view results directly within the InsureSight application; only scheduled and exported reports are impacted. Our team is actively working to identify the cause and restore full functionality. We will provide additional updates as they become available. - iPipeline Support

2. resolved Dec 16, 2025, 08:53 PM UTC

   The issue has been resolved, and users are now able to successfully export reports from InsureSight. - iPipeline Support

Read the full incident report →

Started Dec 09, 2025, 07:52 PM UTC· resolved Dec 09, 2025, 10:36 PM UTC

1. investigating Dec 09, 2025, 07:52 PM UTC

   We are currently investing reports of an issue that is causing customers to experience delays in the Transmission of eApps. Further updates will be provided as we have more details. - The iPipeline Support Team

2. monitoring Dec 09, 2025, 09:03 PM UTC

   We have resolved the issue, and transactions are now successfully processing through our system. The backlog of cases is also progressing through the workflow. While it will take some time for all pending items to complete, we expect the system to fully catch up as processing continues. We have added extra resources to help expedite the backlog processing. We will continue to monitor progress and provide updates as needed. - The iPipeline Support Team

3. resolved Dec 09, 2025, 10:36 PM UTC

   We are observing a strong processing rate , and cases are now flowing through the system without any further issues. Based on the current stability, we will proceed to close the incident. The team will continue to closely monitor server performance and case volume to ensure sustained stability. - iPipeline Support Team

Read the full incident report →

Started Dec 04, 2025, 11:39 PM UTC· resolved Dec 07, 2025, 01:23 AM UTC

1. identified Dec 04, 2025, 11:39 PM UTC

   We have received reports from customers that email signatures are not being delivered when using Gmail as the email provider. We identified that our emails are being blocked by Gmail, and we have opened a ticket with Google to assist with resolving this issue. In the meantime, our support teams have implemented a workaround to assist users who inquire about delayed eSignature emails. Additional updates will be communicated as made available. -iPipeine Support

2. identified Dec 05, 2025, 03:08 PM UTC

   We are continuing to experience issues with emails sent from iGO to GMAIL.com email addresses. iPipeline continues to engage with Google support in order to work to resolve the issue. Additional updates will be communicated at 12 pm EST. - Ipipeline Support

3. identified Dec 05, 2025, 03:26 PM UTC

   We have identified that only a subset of emails is being rejected by Google. The affected messages are those missing a required header. Our team is actively investigating the cause and working to ensure all emails are delivered successfully. Additional updates will be communicated at 12 pm EST.

4. identified Dec 05, 2025, 05:17 PM UTC

   We are continuing to investigate this issue while we await Google’s response regarding the ongoing blocking of our emails and whether adjustments can be made on their end. We have also identified that additional domains may be affected, particularly those using Gmail as a mail relay. Clients who support their customers through the Admin Tool can copy and manually send the signature link to impacted users. We will continue working toward a resolution and will provide further updates around 2 PM . - iPipeline Support

5. identified Dec 05, 2025, 07:08 PM UTC

   We continue to investigate this issue and have identified that approximately 60% of emails are being successfully delivered. Our investigation is now focused on understanding the characteristics of the emails that are being blocked. We will share further updates as more information becomes available. - iPipeline Support

6. identified Dec 05, 2025, 09:32 PM UTC

   We continue working with the relevant vendors on mitigations to this problem, which impacts a subset of emails sent only to gmail addresses. In the mean time, we are also supporting our customers and users with a number of work arounds applicable to their specific configuration and situation to ensure continued processing of business. We will share further updates as more information becomes available. - iPipeline Support

7. identified Dec 06, 2025, 12:00 AM UTC

   We have identified iCloud.com as an additional domain that is being partially blocked as part of the current incident. We continue to work on mitigation. Additional updates will be communicated as new information becomes available. -iPipeine Support

8. identified Dec 06, 2025, 03:25 PM UTC

   We have developed and tested a technical solution which alleviates the issues we have been having with some of the emails going to gmail and iCloud. As we apply this fix, the outbound emails will be paused an queued for 30 minutes. Once the fix is implemented, we will monitor to ensure that all queued emails are successfully processed. We will provide another update in an hour. -iPipeline Support Team

9. identified Dec 06, 2025, 04:32 PM UTC

   We have implemented a change to address the email delivery issue and are now seeing significant improvement in email delivery. Our team continues to investigate and work toward fully resolving the issue. We will post another update within the hour -iPipeine Support

10. monitoring Dec 06, 2025, 05:43 PM UTC

    We continue to see emails being delivered successfully to end users, and the team continues to actively monitor the system. -iPipeine Support

11. resolved Dec 07, 2025, 01:23 AM UTC

    Email delivery has fully returned to normal operations, and messages are being delivered successfully. The issue has been resolved, and we will continue to monitor the system to ensure ongoing stability. - iPipeline Support

Read the full incident report →

Started Nov 24, 2025, 07:07 PM UTC· resolved Dec 11, 2025, 10:22 PM UTC

1. investigating Nov 24, 2025, 07:07 PM UTC

   Dear Valued Partners We are currently receiving reports of customers being unable to complete and receive transmitted orders in the UAT environment following recent updates. Our teams are actively investigating and working to restore full functionality. Further updates will be provided as more information becomes available. -The iPipeline Support Team

2. identified Nov 24, 2025, 09:26 PM UTC

   We have identified the issue preventing customers from receiving transmitted orders in our UAT environment. We are currently working with our industry clearing and transaction-processing partner to determine a resolution and deployment timeline. In the meantime, we have confirmed that all transactions are processing successfully in the production environment.

3. identified Dec 01, 2025, 10:46 PM UTC

   Our team continues to actively work toward resolving the current issue. We can confirm that cases are being successfully transmitted to DTCC for processing. However, we have identified a problem with files that are sent to DTCC in a zipped format. As a temporary workaround, we have adjusted the process so that files are transmitted without being zipped. This measure ensures continuity while we collaborate with DTCC to address the underlying issue. We will provide a further update tomorrow as more information becomes available. - iPipeline Support

4. identified Dec 02, 2025, 03:54 PM UTC

   We have partnered with DTCC on a fix to the existing processing issues and expect it to be implemented tonight. All customers should see transaction flow return to normal in UAT tomorrow. At the same time we are investigating a number of reports of gateway timeouts being experienced in the UAT environment. We will continue to provide updates as additional information becomes available -iPipeline Support Team

5. identified Dec 02, 2025, 10:56 PM UTC

   We have identified the issue causing the gateway timeout errors. We have tested a fix and have a plan to roll it out overnight. We will provide additional updates tomorrow morning. --- iPipeline Support Team

6. identified Dec 03, 2025, 09:52 PM UTC

   We resolved the gateway timeout issue earlier today and have made meaningful progress on the DTCC order processing issues. A few issues are still outstanding, and the team is actively working through them. We will provide a further update tomorrow as more information becomes available. --- iPipeline Support Team

7. identified Dec 04, 2025, 04:27 PM UTC

   Last night we resolved the file processing issues, and we’ve since resumed sending confirmation and rejection files. Several clients have already confirmed receiving their files. We are currently addressing a separate issue affecting BoB file processing, and the team is actively working on it. Additional updates will be shared as information becomes available. - iPipeline Support

8. monitoring Dec 08, 2025, 10:35 PM UTC

   Issues related to BoB have been corrected, and orders should now be processing as expected. If teams encounter any new issues, please proceed through the standard defect triage process. Individual project teams will review and address defects as they are reported. -The iPipeline Support Team

9. resolved Dec 11, 2025, 10:22 PM UTC

   All critical issues have been resolved. If any new issues are encountered, please reach out to the iPipeline contacts for review and defect triage. -The iPipeline Support Team

Read the full incident report →

Started Nov 18, 2025, 01:04 PM UTC· resolved Nov 18, 2025, 03:33 PM UTC

1. identified Nov 18, 2025, 01:04 PM UTC

   We are aware of a widespread outage reported with Cloudflare, an IT security provider. At this time, our applications are not impacted. However, some of our partners or providers that rely on Cloudflare may experience disruptions. Our team is actively monitoring the situation and will provide updates if we detect any impact on our systems. Next Update - 9 am EST. - iPipeline Support

2. identified Nov 18, 2025, 02:08 PM UTC

   We are continuing to monitor the situation as Cloudflare works to restore its services. At this time, our systems remain fully operational, and we have not observed any impact. Our team is actively monitoring the situation. Next Update - 10 am EST - iPipeline Support

3. monitoring Nov 18, 2025, 02:55 PM UTC

   Cloudflare has implemented a fix and confirmed that the issue should now be resolved. Our team will continue to monitor the situation for a period before closing the communication. Next Update - 10:30 am EST - iPipeline Support

4. resolved Nov 18, 2025, 03:33 PM UTC

   This communication will now be closed as the service is now restored. - iPipeline Support

Read the full incident report →

Started Oct 29, 2025, 04:54 PM UTC· resolved Oct 30, 2025, 01:37 PM UTC

1. identified Oct 29, 2025, 04:54 PM UTC

   We are currently experiencing an issue with the AFFIRM 1035 Yellow Pages service. The Yellow Page services may not be accessible at this time. Our vendor is actively working to determine the root cause. Additional updates will be sent accordingly. Should you have any other technical issues, please contact: [email protected] -- The iPipeline Support Team

2. resolved Oct 30, 2025, 01:37 PM UTC

   The issue with the 1035 Yellow Pages has been resolved and full service has been restored. Should you experience and remaining technical issues please contact: [email protected] -- The iPipeline Support Team

Read the full incident report →

Started Oct 28, 2025, 07:18 PM UTC· resolved Nov 04, 2025, 02:10 PM UTC

1. investigating Oct 28, 2025, 07:18 PM UTC

   We are currently investigating sporadic reports of an issue affecting the ability to view completed applications in DocFast, where an error appears when attempting to view forms after the signature process is complete. Our team is actively investigating and will continue to provide updates as more information becomes available. - iPipeline Support

2. identified Oct 28, 2025, 08:55 PM UTC

   The team has identified the cause of the issue and is actively working on a resolution. We will provide further updates as they become available. - iPipeline Support

3. monitoring Oct 29, 2025, 01:17 PM UTC

   Our team has mitigated the issue that was affecting users’ ability to view completed applications. The impacted functionality has been restored, and users should now be able to access completed applications without interruption. We will continue to closely monitor the system to ensure ongoing stability and performance. - iPipeline Support

4. monitoring Oct 29, 2025, 06:25 PM UTC

   The team continues to closely monitor the application and has confirmed that the issue should no longer occur for cases completed today. Cases completed prior to this may still encounter errors; these are being reviewed and corrected promptly. - iPipeline Support

5. monitoring Oct 30, 2025, 06:36 PM UTC

   We have identified that this issue could potentially affect iGO cases. While no reports have been received, our internal review process detected the behavior in limited scenarios. The team continues to actively monitor the environment and will promptly remediate any cases that are reported. - iPipeline Support

6. resolved Nov 04, 2025, 02:10 PM UTC

   We have been monitoring a previously reported sporadic issue and have implemented internal fixes to address related anomalies. At this time, we have not received any new reports of the issue. As a result, we are closing this incident. Our team will continue to monitor the environment to ensure ongoing stability. If you experience any related issues, please reach out to our support team. - iPipeline Support

Read the full incident report →

Started Oct 21, 2025, 03:51 AM UTC· resolved Oct 21, 2025, 10:40 AM UTC

1. investigating Oct 21, 2025, 03:51 AM UTC

   We have identified degraded performance with LifePipe, where users may experience longer-than-normal response times when running quotes. Our team is actively investigating and has determined that the issue is likely related to a third-party vendor impacting our system. We are working on a solution and will provide updates as more information becomes available. - iPipeline Support

2. identified Oct 21, 2025, 03:54 AM UTC

   The issue has been identified and a fix is being implemented.

3. identified Oct 21, 2025, 06:20 AM UTC

   We have started to see improved performance with the LifePipe application as the third-party vendor makes necessary adjustments. Our team continues to work on a solution and will provide updates as more information becomes available. - iPipeline Support Team

4. resolved Oct 21, 2025, 10:40 AM UTC

   The issue has been resolved by our third-party vendor, and the LifePipe application is now functioning normally. We will continue to monitor performance to ensure ongoing stability. - iPipeline Support Team

Read the full incident report →

Started Oct 20, 2025, 02:01 PM UTC· resolved Oct 21, 2025, 11:26 PM UTC

1. monitoring Oct 20, 2025, 02:01 PM UTC

   We are continuing to monitor for residual impacts of the AWS outage widely reported overnight. All our services remain available and accessible and are performing normally. It is possible that some performance impacts may be experienced as our partners continue their recovery efforts and make necessary adjustments. We will post material updates here as they become available. - iPipeline Support Team

2. monitoring Oct 20, 2025, 02:54 PM UTC

   As AWS continues to work on recovering from the issue, intermittent network problems are still being observed, sporadically impacting users accessing iPipeline systems. We have received reports from users experiencing issues running Resonant and iGO systems. Additionally, InsureSight dashboards are delayed in updating. We are continuing to monitor the situation and will keep you updated here. - iPipeline Support

3. monitoring Oct 20, 2025, 03:43 PM UTC

   We continue to observe sporadic issues related to the ongoing AWS outage. We have also received reports of users encountering errors while using LifePipe. We will continue to closely monitor AWS’s recovery process and provide an update within the next 30 minutes. - iPipeline Support

4. monitoring Oct 20, 2025, 04:40 PM UTC

   As AWS reports progress in their mitigation efforts, we observe fewer of the sporadic issues related to the ongoing AWS outage. At the same time, we have received reports of impacts to XRAE which have not been previously communicated. We will continue to closely monitor AWS’s recovery process and provide an update within the next 30 minutes. - iPipeline Support Team

5. monitoring Oct 20, 2025, 04:52 PM UTC

   We are continuing to monitor for any further issues.

6. monitoring Oct 20, 2025, 05:46 PM UTC

   We are continuing to monitor for sporadic impacts of the ongoing AWS outage. As the AWS team continues to make progress with their mitigation efforts, we continue to assess the impact on our services. We will post material updates here as they become available. - iPipeline Support Team

7. monitoring Oct 20, 2025, 06:06 PM UTC

   We are closely monitoring the ongoing AWS outage and continue to receive reports from agents experiencing intermittent access issues with our systems. We will provide additional updates as more information becomes available. -- iPipeline Support Team

8. monitoring Oct 20, 2025, 08:15 PM UTC

   We have observed that our systems have been inaccessible for the past 30 minutes, potentially due to a PING service issue. The team is actively investigating and will provide an update as soon as more information becomes available. - iPipeline Support

9. monitoring Oct 20, 2025, 08:50 PM UTC

   We have started to see improvements in system accessibility following the reboot of the PING server. The issue appears to have been related to underlying AWS network instability. Connectivity across all systems has improved, and we continue to monitor to ensure ongoing stability. Our team is also monitoring AWS’s recovery progress and will provide further updates as they become available. - iPipeline Support Team

10. monitoring Oct 20, 2025, 10:07 PM UTC

    We are continuing to see improvements in system accessibility in line with the recovery efforts being reported by AWS. Connectivity across all systems has improved, the number of reported errors continues to decline. Our team is also monitoring AWS’s recovery progress and will continue to provide further updates as they become available. - iPipeline Support Team

11. monitoring Oct 20, 2025, 10:28 PM UTC

    As AWS has restored the majority of its services, we are seeing corresponding improvements across our platform. Our applications are operating normally with stable performance. We have not observed any further degradation over the past few hours and continue to monitor our systems closely. - iPipeline Support Team

12. monitoring Oct 21, 2025, 10:49 AM UTC

    Our team worked through the night to mitigate the issue that impacted application performance following the outage. The issue has been successfully resolved, and all applications are now healthy and functioning normally. We will continue to monitor the environment throughout the morning and take any necessary action if new concerns arise. - iPipeline Support Team

13. resolved Oct 21, 2025, 11:26 PM UTC

    After monitoring for residual impacts throughout the day and performing all the necessary verifications and reconciliations on impacted applications we are confirming that this incident is resolved. -iPipeline Support Team

Read the full incident report →

Started Oct 13, 2025, 01:40 PM UTC· resolved Oct 13, 2025, 02:08 PM UTC

1. investigating Oct 13, 2025, 01:40 PM UTC

   We are aware that users are currently unable to access Agency Integrator system. Our engineering team is engaged and investigating the issue to identify the cause and restore access as quickly as possible. -iPipeline Support

2. resolved Oct 13, 2025, 02:08 PM UTC

   We have resolved the issue, and our monitoring confirms that the Agency Integrator application is back online and functioning as expected. - iPIpeline Support

Read the full incident report →

Started Sep 26, 2025, 07:04 PM UTC· resolved Sep 29, 2025, 06:15 PM UTC

1. investigating Sep 26, 2025, 07:04 PM UTC

   We have received reports from some users experiencing slow response times when completing signatures. Our engineering team has been engaged and is investigating the issue. - iPipeline Support

2. monitoring Sep 26, 2025, 08:07 PM UTC

   The team has been reviewing and investigating the reported slowness and identified a period of high usage earlier this afternoon. The system has since stabilized, and we are not observing any performance issues at this time. The team will continue to monitor the system. - iPipeline Support

3. resolved Sep 29, 2025, 06:15 PM UTC

   We have been monitoring the server and have not observed any performance issues today. As the system remains stable, we will be closing this incident. - iPipeline Support

Read the full incident report →

Started Sep 22, 2025, 11:51 PM UTC· resolved Sep 23, 2025, 12:09 AM UTC

1. investigating Sep 22, 2025, 11:51 PM UTC

   We have been receiving reports that users are unable to access our term quote solution, LifePipe. We are investigating this issue and further updates will be provided as we have more details. - The iPipeline Support Team

2. resolved Sep 23, 2025, 12:09 AM UTC

   We have resolved the LifePipe access issues. We are monitoring to ensure that systems are operating normally. We appreciate your patience while we worked through the issue. - The iPipeline Support Team

Read the full incident report →

Started Sep 08, 2025, 02:09 PM UTC· resolved Sep 08, 2025, 04:00 PM UTC

1. investigating Sep 08, 2025, 02:09 PM UTC

   We are aware that users are unable to access iPipeline systems. Our team is actively investigating the issue. -- iPipeline Support

2. monitoring Sep 08, 2025, 02:50 PM UTC

   We identified a recent update to the authentication service as the cause of performance degradation and access issues. The update has been rolled back, and the system is now stable and performing normally. We continue to monitor the service closely. - iPipline Support

3. monitoring Sep 08, 2025, 03:03 PM UTC

   We are continuing to work with the team. Further investigation is in progress, and we will provide timely updates. -iPipeline Support

4. monitoring Sep 08, 2025, 03:34 PM UTC

   We are seeing improvements and have confirmed that users are able to access our systems. While some performance degradation may still occur as the system fully recovers, our team is actively monitoring. - iPipeline Support

5. resolved Sep 08, 2025, 04:00 PM UTC

   The authentication service is fully operational, and users can access iPipeline systems without issues. We will continue monitoring to ensure stability. - iPipeline Support

Read the full incident report →

Started Aug 25, 2025, 09:46 PM UTC· resolved Aug 26, 2025, 05:07 PM UTC

1. investigating Aug 25, 2025, 09:46 PM UTC

   We are currently receiving reports that some customers are receiving error messages while using the XRAE solution. We are investigating this issue and further updates will be provided as we have more details. - The iPipeline Support Team

2. monitoring Aug 25, 2025, 11:21 PM UTC

   A change has been made that appears to have made a significant positive impact on the intermittent nature of the issue, and we will continue to monitor until we can confirm that the issue is fully resolved.

3. resolved Aug 26, 2025, 05:07 PM UTC

   The changes made yesterday appear to have fully resolved the issues we were seeing with XRAE, and no additional reports of the issue have surfaced.

Read the full incident report →

Started Aug 25, 2025, 07:28 PM UTC· resolved Sep 02, 2025, 04:49 PM UTC

1. investigating Aug 25, 2025, 07:28 PM UTC

   We are currently receiving reports that customers are experiencing latency while signing with AlphaTrust. We are investigating this issue and further updates will be provided as we have more details. - The iPipeline Support Team

2. investigating Aug 25, 2025, 08:27 PM UTC

   We are continuing to investigate the latency issues impacting customers while signing with AlphaTrust. Further updates will be provided as we have more details. - The iPipeline Support Team

3. identified Aug 26, 2025, 12:00 AM UTC

   We have identified an issue that was causing intermittent latency for customers signing with AlphaTrust earlier in the day and are working on remediation strategies. Further updates will be provided as we have more details. - The iPipeline Support Team

4. monitoring Aug 26, 2025, 11:31 AM UTC

   We have implemented remediation strategies overnight to address the intermittent latency Alphatrust Customers were experiencing with signing. We are continuing to closely monitor performance to ensure the issue has been fully resolved. --The iPipeline Team

5. monitoring Aug 26, 2025, 05:21 PM UTC

   We have been closely monitoring our systems and observed a brief period of degraded performance for 30 mins .Our team is actively engaged and continues to work on remediating the problem. At this time, services are stable, and we will continue to monitor closely. Further updates will be provided as more information becomes available. - The iPipeline Support Team

6. identified Aug 26, 2025, 10:21 PM UTC

   Our team is making steady progress in stabilizing the environment. We have identified potential solutions and are actively working on implementing them. These efforts will continue through tomorrow morning, after which we will evaluate the impact and provide another update. We will continue to share further updates as more information becomes available. - The iPipeline Support Team

7. monitoring Aug 27, 2025, 12:57 PM UTC

   Our team has implemented the remediation solutions overnight for AlphaTrust as planned. At this time, services are stable, and we will continue to monitor closely to ensure the issue is fully resolved. Further updates will be provided as more information becomes available. - The iPipeline Support Team

8. resolved Sep 02, 2025, 04:49 PM UTC

   We have not observed any performance issues over the past few days, and the system remains stable. This incident will now be closed. - The iPipeline Support Team

Read the full incident report →

Started Aug 15, 2025, 04:12 PM UTC· resolved Aug 15, 2025, 06:04 PM UTC

1. investigating Aug 15, 2025, 04:12 PM UTC

   We are currently aware of an issue impacting multiple iPipeline applications, including AFFIRM, where some customers are unable to access the platforms. Our Support teams are actively investigating the root cause. Further updates will be communicated accordingly. -- The iPipeline Support Team

2. identified Aug 15, 2025, 05:00 PM UTC

   Our team is actively investigating the issue. We have not observed any further occurrences in the past 30 minutes and will continue to closely monitor the situation until we confirm full resolution. -- iPipeline Support

3. resolved Aug 15, 2025, 06:04 PM UTC

   We have not observed any errors in our systems for the past hour, and users have been able to access the systems normally. We will continue working to identify the root cause and implement measures to minimize any future disruptions. As the service remains stable, we are closing the incident but will continue to monitor closely. -- iPipeline Support

Read the full incident report →

Started Aug 14, 2025, 08:04 PM UTC· resolved Aug 14, 2025, 08:26 PM UTC

1. identified Aug 14, 2025, 08:04 PM UTC

   On August 12, Guardian reported eapp processing issues affecting certain cases. This was traced to a recent project release on August 9, where a scenario requiring an agency code was missing, causing the application to fail to process in the client’s backend system. The team has identified the fix, which is scheduled for release on Saturday, August 16. In the meantime, the Support team is manually correcting affected cases as they are identified. -- iPipeline Support

2. resolved Aug 14, 2025, 08:26 PM UTC

   The earlier communication was sent in error and should be disregarded. Please ignore the message, and we apologize for any inconvenience caused. -- iPipeline Support

Read the full incident report →

Started Aug 04, 2025, 03:27 PM UTC· resolved Aug 04, 2025, 05:57 PM UTC

1. investigating Aug 04, 2025, 03:27 PM UTC

   We are currently investigating an issue where agents are unable to upload documents due to an error occurring during the virus scan process. Our support team is actively reviewing the problem and will provide further updates as more information becomes available. --iPipeline Support

2. resolved Aug 04, 2025, 05:57 PM UTC

   The team engaged Symantec engineers to assist in troubleshooting the issue and has successfully resolved the problem. The root cause was an unsupported Java version that had been installed on the server during an update on August 2. After reverting to the previously supported Java version, the antivirus services started functioning normally. We have confirmed with the support team that agents are now able to upload documents and proceed without issues. -- iPipeline Support

Read the full incident report →

Started Aug 04, 2025, 03:09 PM UTC· resolved Aug 04, 2025, 05:43 PM UTC

1. investigating Aug 04, 2025, 03:09 PM UTC

   AFFIRM users are currently experiencing an issue when attempting to upload attachments within the AFFIRM application. Users are receiving the following error message when uploading items: ‘Error Upload Failed’. This issue is impacting all AFFIRM customers. Our internal teams have identified the cause and are actively working towards a resolution. Additional updates will be communicated accordingly. -- The iPipeline Support Team

2. identified Aug 04, 2025, 05:34 PM UTC

   iPipeline continues to work towards resolving the issue preventing users from uploading files to the AFFIRM platform. All iPipeline Teams are actively engage. Additional updates will be communicated accordingly. -- The iPipeline Support Team

3. resolved Aug 04, 2025, 05:43 PM UTC

   The issue impacting users ability to upload files to the AFFIRM platform has been resolved. iPipeline Teams were able to work with the vendor to resolve the issue. Functionality has been fully restored, and we’re continuing to monitor system performance. -- The iPipeline Support Team

Read the full incident report →

Started Jun 16, 2025, 05:44 PM UTC· resolved Jun 16, 2025, 07:45 PM UTC

1. investigating Jun 16, 2025, 05:44 PM UTC

   We are investigating reports from multiple users encountering a blank page upon logging into InsureSight. Our data team is actively engaged and working to identify the root cause and implement a resolution. Additional updates will be communicated accordingly. -- iPipeline Support

2. resolved Jun 16, 2025, 07:45 PM UTC

   The issue was caused by a connectivity failure between internal services due to an authentication error. After identifying a configuration issue related to authentication, the team updated the necessary settings, and connectivity has since been restored. Users are now able to log in to InsureSight as expected. -- iPipeline Support

Read the full incident report →

Started Jun 04, 2025, 04:29 PM UTC· resolved Jun 04, 2025, 05:04 PM UTC

1. investigating Jun 04, 2025, 04:29 PM UTC

   iPipeline is aware of users being unable to log into and access Laser App Anywhere and Fusion. Multiple teams are are currently engaged in investigating the issue and working to identify root cause and correct. Additional updates will be communicated accordingly. -- The iPipeline Support Team

2. resolved Jun 04, 2025, 05:04 PM UTC

   iPipeline system engineers have restored access to the Laser App Anywhere and Fusion applications. Teams remain engaged in monitoring the system to ensure access remains fully restored. -- The iPipeline Support Team

Read the full incident report →

Started Apr 15, 2025, 03:03 PM UTC· resolved Apr 15, 2025, 04:49 PM UTC

1. investigating Apr 15, 2025, 03:03 PM UTC

   We are currently investigating an issue with XRAE producing various errors when attempting to navigate through existing cases or adding new cases. We will provide additional updates as more information becomes available.

2. monitoring Apr 15, 2025, 03:50 PM UTC

   We've reviewed the issue and have made some system adjustments and are now seeing reduced errors. We are continuing to monitor.

3. resolved Apr 15, 2025, 04:49 PM UTC

   After a period of monitoring we have confirmed that the issues reported for XRAE have been resolved. Thank you for your patience as we've worked through this issue.

Read the full incident report →

Started Apr 11, 2025, 06:35 PM UTC· resolved Apr 11, 2025, 06:39 PM UTC

1. investigating Apr 11, 2025, 06:35 PM UTC

   We are currently investigating an issue affecting the one-time passcode (OTP) required to log in and continue signing the illustration. This issue appears to be isolated to a single customer, the Catholic Order of Foresters (COF). We will provide additional updates as more information becomes available. --iPipeline Support

2. resolved Apr 11, 2025, 06:39 PM UTC

   This was sent in an error , please ignore it. --iPipeline Support

Read the full incident report →