Aplos incident

Users are unable to authenticate with PEX

Major Resolved View vendor source →

Aplos experienced a major incident on July 10, 2025 affecting Accounting, lasting 8d 4h. The incident has been resolved; the full update timeline is below.

Started
Jul 10, 2025, 06:35 PM UTC
Resolved
Jul 18, 2025, 10:49 PM UTC
Duration
8d 4h
Detected by Pingoru
Jul 10, 2025, 06:35 PM UTC

Affected components

Accounting

Update timeline

  1. investigating Jul 10, 2025, 06:35 PM UTC

    We have discovered an issue that has been preventing users from authenticating (or re-authenticating) with PEX. The team are beginning their investigations.

  2. investigating Jul 11, 2025, 01:44 AM UTC

    Our investigations will continue into tomorrow, as we are now communicating with the PEX team to help track down the source of this issue. Please note that many users who are already connected to PEX are not seeing any issues, this only affect those attempting to connect for the first time and a small number of connections that are expired and trying to re-authenticate.

  3. identified Jul 14, 2025, 04:23 PM UTC

    The team are preparing to apply a fix, and we'll announce here as soon as it's live and continue to monitor to ensure new and re-authenticating users can connect to PEX properly.

  4. identified Jul 17, 2025, 08:41 PM UTC

    The team have determined that the changes we intend to implement to resolve this PEX issues may impact other Aplos integrated services. To avoid causing greater impact to those services, we are performing extensive testing on the solution before launching it. We hope to have an update soon on when the fix will be live, and will verify that new PEX connections can be created.

  5. resolved Jul 18, 2025, 10:49 PM UTC

    This should now be resolved and all users should be able to log into PEX.