iPipeline incident

iGo - Browser compatibility issue with recent Google Chrome ver update

Notice Resolved View vendor source →

iPipeline experienced a notice incident on July 7, 2026 affecting iGO, lasting 1d 23h. The incident has been resolved; the full update timeline is below.

Started
Jul 07, 2026, 05:47 PM UTC
Resolved
Jul 09, 2026, 05:04 PM UTC
Duration
1d 23h
Detected by Pingoru
Jul 07, 2026, 05:47 PM UTC

Affected components

iGO

Update timeline

  1. investigating Jul 07, 2026, 05:47 PM UTC

    We are currently investigating a compatibility issue introduced by the recent Google Chrome version 150 update (which also impacts Edge browsers). Our team is actively working on this and will provide updates as soon as they become available. In the meantime, if you are experiencing issues, please try a different web browser. We appreciate your patience and understanding. - iPipeline Support

  2. identified Jul 07, 2026, 08:10 PM UTC

    At this time, the issue appears to be limited to a subset of users. We have identified a solution and are currently undertaking all the necessary validation and testing steps. In the meantime, users who encounter this issue may continue working by using an alternative browser, such as Firefox or Safari. Alternatively, users may temporarily revert to a previous version of Chrome or Microsoft Edge until the fix has been fully validated and deployed. We will continue to provide updates as additional information becomes available. - iPipeline Support

  3. identified Jul 08, 2026, 06:24 PM UTC

    Testing has been successfully completed, and the team is preparing to deploy the changes to production tonight. We will continue to provide updates as additional information becomes available. - iPipeline Support

  4. monitoring Jul 09, 2026, 02:17 PM UTC

    The code fix was released this morning and has been successfully validated. At this time, we have not observed any issues following deployment. We will continue to closely monitor the situation and provide further updates if needed. - iPipeline Support

  5. resolved Jul 09, 2026, 05:04 PM UTC

    Since the fix was deployed, we have not observed any new occurrences of the issue. Ongoing monitoring has confirmed stability, and the issue is considered resolved at this time. - iPipeline Support