Neon Fundraise Outage History

Neon Fundraise had 4 outages in the last 2 years totaling 79h 12m of downtime — averaging 0.2 incidents per month.

There were 4 Neon Fundraise outages since October 3, 2025 totaling 79h 12m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.rallybound.com

Critical March 20, 2026

Intermittent charging issues with Neon Pay

Detected by Pingoru: Mar 20, 2026, 10:15 PM UTC
Resolved: Mar 23, 2026, 01:08 PM UTC
Duration: 2d 14h

Affected: Neon Pay

Timeline · 4 updates

investigating Mar 20, 2026, 10:15 PM UTC

We are currently investigating an issue causing charges to intermittently fail on Neon Pay.
investigating Mar 20, 2026, 10:59 PM UTC

We have isolated the issue and mitigated the affect to Payments. All charges are currently processing as expected and we are continuing to monitor as we work towards full resolution.
monitoring Mar 21, 2026, 12:00 AM UTC

All charges have continued to process as expected - we will continue to monitor the situation before marking this as fully resolved.
resolved Mar 23, 2026, 01:08 PM UTC

No further issues have occurred since the fix was implemented and monitoring began, the issue has been marked as fully resolved.

Read the full incident report →

Major January 7, 2026

High CPU usage caused intermittent issues

Detected by Pingoru: Jan 07, 2026, 04:32 PM UTC
Resolved: Jan 07, 2026, 08:03 PM UTC
Duration: 3h 30m

Timeline · 2 updates

monitoring Jan 07, 2026, 04:32 PM UTC

We have identified an issue with high cpu usage. A fix has been implemented and we are monitoring to confirm that the issue does not recur.
resolved Jan 07, 2026, 08:03 PM UTC

This incident has been marked as resolved. The fix implemented earlier has addressed the CPU usage, and monitoring has confirmed that levels have remained normal since the issue was addressed.

Read the full incident report →

Notice October 20, 2025

Hosting provider (AWS) experiencing degradation of services

Detected by Pingoru: Oct 20, 2025, 01:58 PM UTC
Resolved: Oct 20, 2025, 09:17 PM UTC
Duration: 7h 19m

Timeline · 3 updates

monitoring Oct 20, 2025, 01:58 PM UTC

AWS (our hosting provider) experienced a degradation of services last night and continues to experience issues in rectifying services. Overall Fundraise systems are operational as of now, but we are continuing to investigate to determine any impact. Information on the outage from AWS can be found here: https://health.aws.amazon.com/health/status
monitoring Oct 20, 2025, 04:56 PM UTC

AWS (our hosting provider) experienced a degradation of services last night and continues to experience issues in rectifying services. Overall Fundraise systems are operational as of now. At this point we have not discovered any affected services, but we are continuing to investigate to determine any impact. Information on the outage from AWS can be found here: https://health.aws.amazon.com/health/status
resolved Oct 20, 2025, 09:17 PM UTC

AWS has confirmed that their fix is working as expected. At this point, we have concluded our investigation and have not found any additional services affected within Neon Fundraise. Please reach out to support with any additional questions or concerns. AWS Statuspage: https://health.aws.amazon.com/health/status

Read the full incident report →

Critical October 3, 2025

Admin Login Disruption

Detected by Pingoru: Oct 03, 2025, 01:28 PM UTC
Resolved: Oct 03, 2025, 06:57 PM UTC
Duration: 5h 29m

Affected: Management interfaces

Timeline · 4 updates

identified Oct 03, 2025, 01:28 PM UTC

We are currently investigating an issue preventing users from logging into Neon Fundraise Admin. This issue is not affecting front-end forms, events, or payments.
identified Oct 03, 2025, 01:57 PM UTC

We have identified the root cause of the issue and are working to release a fix.
monitoring Oct 03, 2025, 04:17 PM UTC

A fix has been implemented for this issue and we are monitoring the situation.
resolved Oct 03, 2025, 06:57 PM UTC

This incident has been resolved.

Read the full incident report →