Aplos Outage History

Aplos is up right now

Aplos had 44 outages in the last 2 years totaling 746h 57m of downtime — averaging 1.8 incidents per month.

There were 44 Aplos outages since December 11, 2024 totaling 746h 57m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.aplos.com

Major July 10, 2025

Users are unable to authenticate with PEX

Detected by Pingoru
Jul 10, 2025, 06:35 PM UTC
Resolved
Jul 18, 2025, 10:49 PM UTC
Duration
8d 4h
Affected: Accounting
Timeline · 5 updates
  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.

Read the full incident report →

Major July 3, 2025

Transactions which previously had Tags are no longer displaying their Tags

Detected by Pingoru
Jul 03, 2025, 06:26 PM UTC
Resolved
Jul 04, 2025, 02:48 AM UTC
Duration
8h 21m
Affected: Reports
Timeline · 4 updates
  1. investigating Jul 03, 2025, 06:26 PM UTC

    The team are aware of this issue and actively investigating.

  2. investigating Jul 03, 2025, 08:47 PM UTC

    We have learned that even Transactions created today are losing their assigned Tags. The team is still investigating for the source of the issue.

  3. monitoring Jul 03, 2025, 11:54 PM UTC

    The team has discovered the cause of the Transaction-line Tags being removed, and applied a fix to prevent it from happening again. Any transaction with lines containing tags applied before ~8:20am PT on 07/03/2025 will be restored. Tags applied after that time today may have lost their lines' associations with those tags and will need re-applied.

  4. resolved Jul 04, 2025, 02:48 AM UTC

    As of ~6:30pm PT, all Transaction-line Tags that were created before this incident began have been restored.

Read the full incident report →

Major June 20, 2025

Bank Reconciliation

Detected by Pingoru
Jun 20, 2025, 03:36 PM UTC
Resolved
Jun 20, 2025, 11:55 PM UTC
Duration
8h 18m
Affected: Accounting
Timeline · 6 updates
  1. investigating Jun 20, 2025, 03:36 PM UTC

    We have identified an issue that is causing the bank reconciliation page to be unavailable to customers

  2. investigating Jun 20, 2025, 03:38 PM UTC

    We are continuing to investigate this issue.

  3. identified Jun 20, 2025, 05:35 PM UTC

    We have identified the issue and have deployed a fix. Refreshing the browser should get the bank reconciliation page to load again.

  4. identified Jun 20, 2025, 05:36 PM UTC

    We will continue to monitor the bank reconciliation page for any more issues.

  5. monitoring Jun 20, 2025, 05:36 PM UTC

    A fix has been implemented and we are monitoring the results.

  6. resolved Jun 20, 2025, 11:55 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical June 12, 2025

A global Google outage may be creating issues with Donation Forms and WebBuilder pages

Detected by Pingoru
Jun 12, 2025, 06:35 PM UTC
Resolved
Jun 13, 2025, 03:27 PM UTC
Duration
20h 51m
Affected: Payment Processing
Timeline · 3 updates
  1. investigating Jun 12, 2025, 06:35 PM UTC

    Aplos relies on certain Google services for Donation Forms, payment processing, and our WebBuilder pages, and they may present failures until the outage is resolved.

  2. monitoring Jun 12, 2025, 07:09 PM UTC

    We have implemented a temporary workaround and payments submitted through Donation Forms should be working again. The team will continue monitoring the Google outage and let you know when all affected services have returned to normal.

  3. resolved Jun 13, 2025, 03:27 PM UTC

    Google services are now back to working as normal.

Read the full incident report →

Major June 10, 2025

Report Data Visualizer is unavailable

Detected by Pingoru
Jun 10, 2025, 06:45 PM UTC
Resolved
Jun 11, 2025, 02:45 PM UTC
Duration
20h
Affected: Reports
Timeline · 2 updates
  1. identified Jun 10, 2025, 06:45 PM UTC

    We have identified an issue that is preventing the use of the Report Data Visualizer, and will provide updates as they become available.

  2. resolved Jun 11, 2025, 02:45 PM UTC

    The Report Data Visualizer is once again operational.

Read the full incident report →

Major June 10, 2025

Certain system emails (such as Donation Notifications to Merchants) have not been sending

Detected by Pingoru
Jun 10, 2025, 05:10 PM UTC
Resolved
Jun 10, 2025, 05:17 PM UTC
Duration
6m
Affected: Payment Processing
Timeline · 2 updates
  1. investigating Jun 10, 2025, 05:10 PM UTC

    Since ~8:40pm PT on 06/09/2025, certain system emails have not been sending to Organizations who have them enabled. Some examples include notifications sent to Merchants concerning events with their Donations.

  2. resolved Jun 10, 2025, 05:17 PM UTC

    This incident has been resolved. Emails which did not send since the issue began will slowly be re-processed, and should be delivered shortly.

Read the full incident report →

Major June 5, 2025

Certain Contributions cannot be edited and Contributions created via the Aplos API may fail

Detected by Pingoru
Jun 05, 2025, 09:10 PM UTC
Resolved
Jun 06, 2025, 01:56 AM UTC
Duration
4h 45m
Affected: APIAccounting
Timeline · 3 updates
  1. investigating Jun 05, 2025, 09:10 PM UTC

    Related to yesterday's outage, outstanding issues are making it so certain Contribution records cannot be edited, and Contributions created via the Aplos API will time out and fail. The team is actively investigating these issues.

  2. identified Jun 05, 2025, 10:06 PM UTC

    The issue has identified and a fix is being prepared.

  3. resolved Jun 06, 2025, 01:56 AM UTC

    These issues have been resolved.

Read the full incident report →

Critical June 4, 2025

Aplos pages are down

Detected by Pingoru
Jun 04, 2025, 05:46 PM UTC
Resolved
Jun 04, 2025, 05:56 PM UTC
Duration
9m
Timeline · 5 updates
  1. investigating Jun 04, 2025, 05:16 PM UTC

    Please be aware that currently Aplos is unavailable. We are working on a solution.

  2. investigating Jun 04, 2025, 05:19 PM UTC

    We are continuing to investigate this issue.

  3. identified Jun 04, 2025, 05:28 PM UTC

    We have identified the issue and are working on deploying the fix.

  4. identified Jun 04, 2025, 05:46 PM UTC

    Login should be working again but the contribution page is still unavailable.

  5. resolved Jun 04, 2025, 05:56 PM UTC

    The issue has been resolved. All pages in Aplos should be available.

Read the full incident report →

Notice May 16, 2025

One-Time Donation Receipts were failing to send for some users since April 25th

Detected by Pingoru
May 16, 2025, 07:48 PM UTC
Resolved
May 16, 2025, 07:48 PM UTC
Duration
—
Timeline · 1 update
  1. resolved May 16, 2025, 07:48 PM UTC

    We were recently alerted to an error concerning Online Donation Receipts (for One-Time donations only, not Recurring) and have discovered that they were not being sent to certain donors. Many donors did still receive this email, the issue was only intermittent. We have now resolved that issue and all Donation Receipts are sending again without error. Please note that Donation Receipts which failed to send during this time cannot be re-sent. We encourage donors to access their MyAplos portal and print a Contribution Statement report if they need proof of payment.

Read the full incident report →

Major April 21, 2025

Online donations aren't creating deposits in their designated account registers

Detected by Pingoru
Apr 21, 2025, 10:20 PM UTC
Resolved
Apr 22, 2025, 04:01 PM UTC
Duration
17h 40m
Affected: Accounting
Timeline · 3 updates
  1. investigating Apr 21, 2025, 10:20 PM UTC

    The team is aware of the issue and actively investigating.

  2. monitoring Apr 22, 2025, 12:32 AM UTC

    A fix has been implemented for this issue. It might take a while for the deposits to show in Aplos. We will continue to monitor.

  3. resolved Apr 22, 2025, 04:01 PM UTC

    The fix was applied and all fully-processed Donations should now be posted to their appropriate registers.

Read the full incident report →

Major March 31, 2025

Unable to Pay Bills

Detected by Pingoru
Mar 31, 2025, 05:57 PM UTC
Resolved
Apr 01, 2025, 03:23 PM UTC
Duration
21h 25m
Affected: Bill PayAccounting
Timeline · 4 updates
  1. identified Mar 31, 2025, 05:57 PM UTC

    The team has identified an issue affecting the ability to pay Accounts Payable (Bill) items. We are working on implementing a fix.

  2. identified Mar 31, 2025, 08:15 PM UTC

    We have identified a work around of using the tab key three times. We expect to have a fix in the next 30 mins.

  3. monitoring Mar 31, 2025, 08:52 PM UTC

    A fix has been deployed for the buttons and we will continue to investigate general styling issues.

  4. resolved Apr 01, 2025, 03:23 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical March 25, 2025

Degraded Performance

Detected by Pingoru
Mar 25, 2025, 06:51 PM UTC
Resolved
Mar 26, 2025, 04:43 AM UTC
Duration
9h 51m
Affected: Full System
Timeline · 6 updates
  1. investigating Mar 25, 2025, 06:51 PM UTC

    We are currently investigating this issue.

  2. investigating Mar 25, 2025, 06:56 PM UTC

    We're currently investigating an issue that is preventing use of Login Page. Users may encounter issues trying to accessing aplos when trying to log in.

  3. monitoring Mar 25, 2025, 07:05 PM UTC

    The issues have subsided and the team will continue monitoring for stability.

  4. investigating Mar 25, 2025, 07:56 PM UTC

    Issues accessing the login page and slowness across the platform have persisted. We are continuing our investigations.

  5. monitoring Mar 25, 2025, 09:27 PM UTC

    To improve system performance and reliability, we're upgrading this week. We have identified that this performance degradation is related to the upgrade. You may experience brief outages during this time. We appreciate your patience while we prepare for the upgrade. Our team is continuing to monitor.

  6. resolved Mar 26, 2025, 04:43 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical March 16, 2025

Login page unavailable

Detected by Pingoru
Mar 16, 2025, 10:51 PM UTC
Resolved
Mar 17, 2025, 12:54 AM UTC
Duration
2h 2m
Affected: Full System
Timeline · 2 updates
  1. investigating Mar 16, 2025, 10:51 PM UTC

    We are investigating reports of the login page being intermittently unavailable.

  2. resolved Mar 17, 2025, 12:54 AM UTC

    The issues have subsided and the team will continue monitoring for stability.

Read the full incident report →

Notice February 19, 2025

Income Statement report is not loading

Detected by Pingoru
Feb 19, 2025, 10:23 PM UTC
Resolved
Mar 07, 2025, 04:27 PM UTC
Duration
15d 18h
Affected: Reports
Timeline · 4 updates
  1. investigating Feb 19, 2025, 10:23 PM UTC

    We have received reports of extensive loading times and performance issues in the Income Statement report. The team is aware of and actively investigating these issues.

  2. investigating Feb 19, 2025, 10:49 PM UTC

    We have implemented a fix to relieve performance and loading issues with the Income Statement. The team will continue monitoring to ensure stability.

  3. monitoring Feb 19, 2025, 11:04 PM UTC

    The fix is in place and the Income Statement should be accessible again. The team will continue to monitor for issues.

  4. resolved Mar 07, 2025, 04:27 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 10, 2025

Login page down and performance issues

Detected by Pingoru
Feb 10, 2025, 05:15 PM UTC
Resolved
Feb 10, 2025, 06:22 PM UTC
Duration
1h 6m
Affected: Full System
Timeline · 2 updates
  1. investigating Feb 10, 2025, 05:15 PM UTC

    We have received reports of the login page being unavailable and intermittently slow loading across Aplos. The team is actively investigating.

  2. resolved Feb 10, 2025, 06:22 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 10, 2025

Users are unable to access Bank Integration

Detected by Pingoru
Jan 10, 2025, 07:25 PM UTC
Resolved
Jan 10, 2025, 10:42 PM UTC
Duration
3h 16m
Affected: PlaidFinicity
Timeline · 3 updates
  1. investigating Jan 10, 2025, 06:56 PM UTC

    We are currently investigating an issue where customers are unable to log into bank integration.

  2. monitoring Jan 10, 2025, 07:25 PM UTC

    We have deployed a fix for this issue . We are continuing to monitor the situation.

  3. resolved Jan 10, 2025, 10:42 PM UTC

    This incident has been resolved.

Read the full incident report →

Major December 11, 2024

Some users are experiencing issues logging into Aplos

Detected by Pingoru
Dec 11, 2024, 05:54 PM UTC
Resolved
Dec 14, 2024, 12:37 AM UTC
Duration
2d 6h
Affected: Full System
Timeline · 3 updates
  1. investigating Dec 11, 2024, 05:54 PM UTC

    We are investigating a spike in error rates relating to issues concerning the log-in page.

  2. monitoring Dec 12, 2024, 02:16 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Dec 14, 2024, 12:37 AM UTC

    This incident has been resolved.

Read the full incident report →